Jump to content
The simFlight Network Forums

Daniel Boulay

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by Daniel Boulay

  1. Good day Peter, hope you're doing well. I have read in your documentation that some PHs are scanned more often than others and I understand why and it makes sens. But if (for a special projetc) I don't use any Sets and only use PH via the FSUIPC_Read feature, will it affect the scanning rate which PHs i choose to use ? My epicinfo.cfg file looks like this: [fanda] Log=0 FSUIPC_WRITE_1=Y15,2,50C0 FSUIPC_READ_1=129,2,50C2 FSUIPC_READ_2=130,4,50C4 FSUIPC_READ_3=131,2,50C8 FSUIPC_READ_4=132,2,50CA FSUIPC_READ_5=133,2,50CC FSUIPC_READ_6=134,2,50CE FSUIPC_READ_7=135,2,50D0 FSUIPC_READ_8=136,2,50D2 FSUIPC_READ_9=137,2,50D4 FSUIPC_READ_10=138,2,50D6 FSUIPC_READ_11=139,2,50D8 FSUIPC_READ_12=149,2,50DA FSUIPC_READ_13=141,2,50DC FSUIPC_READ_14=142,2,50DE So, basically, my question is that if I use PH 118 instead of PH 129, will it make a difference in the updating rate ? Thanks and best regards, Daniel
  2. Ouch!... Stupid mistake... when i saw your post with Sets=CP , it clicked...i had forgotten the line Sets=All in my CFG file. Sorry Peter... Thanks Daniel
  3. Sorry...i should have included more details. I have FS2004 and EPICINFO 4.22 I have used the log in and can confirm that no change is recorded by it for qproc 96 and 97. I have tested another qproc just to make sure and qproc 18 and 19 were beeing recorded in the log file when i pressed the autopilot button.. but when I switched from parking brake on and off, no values recorded. Regards, Daniel
  4. Peter, did you ever got any reports that qproc 96 and 97 for parking brakes are not working ? I've been trying for a long time but no joy... I use qproc 98 and 99 for my prop sync LED with no problem. The doc says it is derived from PARKING_BRAKE_POS... is there a PH for this ?...can't seem to find one. Best regards and wish you a very happy new year ! Daniel
  5. Yes, that would work... it would have been easier if the SetMap command would have worked but that's ok. Thanks Daniel
  6. Good day Pete, I would like to be able to send a real axis value via the FSUIPC_write command to a specific offset. The command does not allow to do this per the documentation so I have mapped the real axis to a soft axis (SetMap) but again, it does not work. If i set the soft axis to a specific value using SetR15=something, it does work. I have the ISA EPIC card. Can this be fixed or is there any other way to do this ? Regards, Daniel Boulay
  7. Pete, have you received any reports on Pigeon Holes greater than 128 not working with epic ISA card... I have WIN98, Epic card ISA, epicinfo 4.20, FSUIPC 3.10 (not registered yet) and I tried these lines: DefinePH(133,Test,0,0,0,0) :Test { } As you can tell, I did not try to do anything with the value... I also tried the above lines with PH 129... Results: My joystick axis would freeze...some not all...and different result if i used 129 and 133... And, after loading it the first time, I would then get an error when compiling my EPL file...wrong version...using eplstrip.exe program. I would remove these 2 lines and it's fine after. Since those PH values are for lever positions, could it be that they only work with the USB version ? Regards, Daniel
  8. Yes, i still have the ISA...hate to spend another 500$ CAN for something i already have but i know that day is coming and i will have to get the USB one...and yes, WIN98 because of my ISA card. Daniel
  9. Pete, happy to report that esound 2.572 with epicinfo 4.20 and fsuipc 3.08 with FS2004 is working fine. I did find the fs9.cfg file and was able to just copy and paste from my fs2002.cfg file for joystick assignments. I can tell you that fs2004 does NOT pick up axis very well from EPIC when trying to use the MSFS assignment page. so, had to do the good old fashion way.. edit the cfg file manually. thanks for your help in this matter...it all started with esound and it is now working nicely...2.572 seem to be a good version for 2002 and 2004. Regards, Daniel
  10. Let me read more on it... as you may remember, i have the epic card which gives me 16 virtual joysticks and fs2004 did not pick up some of them... With fs2002, i programmed the axis manually in the cfg file... i`ll just do the same with fs2004. I was looking fs2004.cfg on the main menu like it was with fs2002. Like I said, i just got fs2004 so i do have some reading to do. Thanks again, and i`ll be registering fsuipc soon also since i do like it and need all the functions (especially the joystick calibration part). Daniel
  11. Pete, got my system working again (thank god !) After a quick test, Esound 2572, with FSUICP 2.975 and FS2002 is now working fine. Great stuff Pete ! I have just installed FS9 but have not installed FSUIPC 3.xx yet so i can't report on that...having some video problems which i'll have to deal with. BUT, I can't find the usual fs2004.cfg file .... is it replaced by something else cause i can't program my EPIC joystick axis with fs2004 menu. Thanks, Daniel
  12. Pete, thanks....i'll try it... my system is down now but should be back soon... i'll let you know. Daniel
  13. OH, by the way... i tested it with FSUIPC 2.975 and 3.08. Dan
  14. After a quick test, no joy Pete. Like I said, i'm OK with it since 2.54 works good so no rush for me. And i can't test it with FS2004 yet. I'm just surprised that it seems that not a lot of folks are using it. It is a great module.... my cabin announcements are automatic...i can even select the sound cards and direct that sound into my headset with lower volume... it's so nice...it's like the real thing...i'm listenning to cabin annoucements and making sure my cabin crew are doing their jobs...lol It adds realisme and what is so nice about it, it is triggered automaticaly so i don't even have to press a button.... for example, when i'm airborn, ALTITUDE_ABOVE_GROUND>=3000, there is that wav file that starts automaticaly saying: now that we are airborn, etc..etc... Man, i sure hope you keep this DLL going... i think most folks don't understand how to use it and what it does. thanks for your fast response Pete, Daniel
  15. Peter, for your consideration, here are my findings... First, button triggers always work...we're talking about token varialbles triggers. I have found an older version of Esound and did some tests: Esound 2.57 with FSUIPC 3.08, no joy Esound 2.57 with FSUIPC 2.975, no joy Esound 2.54 with FSUIPC 3.08, works Esound 2.54 with FSUIPC 2.975, works As a reminder, i still have FS2002. so for now, until I updated to FS2004 (which should not be too long), I will use FSUIPC 2.975 and Esound 2.54. Thank you for your time and effort, Daniel
  16. Good evening all, i realize Peter is not supporting Esound but maybe someone can help. I use Esound 2.57 with FSUIPC 2.975 with FS2002. Works great except i can't get any token variables to work. Here's my esound.cfg file: [Devices] 1=Primary Sound Driver 2=C-Media Audio Direct Sound Driver 3=DirectSound (SB Live! Wave Out [E400]) [settings] 1 = 2,50,C 2 = 3,60,C 3 = 3,30,C [sounds] 1 = SAC1.wav 2 = SAC2.wav 3 = SAC3.wav 4 = SAC4.wav 5 = SAC5.wav 6 = SAC6.wav 7 = SAC7.wav 8 = music.wav 9 = cbding.wav 10 = revbetahorn.wav [Triggers] 1 = B496:0,9,2 ;Fasten seat belt ON or OFF 2 = B497:0,1,2 ;Fasten seat belt ON 3 = B498:0,3,2 4 = B499:0,4,2 5 = B500:0,5,2 6 = B501:0,6,2 7 = B502:0,7,2 8 = B507:0,2,2 9 = B505:0,8,3,LOOP 10 = B505:1,STOP9 11 = B506:0,10,1,LOOP 12 = B506:1,STOP11 13 = AIRSPEED>=20,10,2 Everything woks fine except trigger 13... Sound 10 works with B506 but not with airspeed greater or equ to 20... and I have tried other token variables but no joy... any ideas anyone.... Peter, knowing that you don't support it, did you get report that this actually works because I fail to see what my mistake is if any and i know there has been problems with it in the past. thank you, Daniel
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.