lwha6500 Posted August 27, 2007 Report Share Posted August 27, 2007 I am creating an Automatic Flight Control sytem for a Helo and need access to Elevator, Ailerons, Rudder, and Throttle. I am using the latest registered version of FSUIPC and FSX and writing to offsets 0x0BB2 for Elevator, 0x0BB6 for Ailerons, 0xBBA for Rudder, and 0x089A for Throttle, but there is no apparent effect on the helo. Are these offsets still available in FSX? I have used the above offsets for FS2004 without any problem. Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 27, 2007 Report Share Posted August 27, 2007 I am creating an Automatic Flight Control sytem for a Helo and need access to Elevator, Ailerons, Rudder, and Throttle. I am using the latest registered version of FSUIPC and FSX and writing to offsets 0x0BB2 for Elevator, 0x0BB6 for Ailerons, 0xBBA for Rudder, and 0x089A for Throttle, but there is no apparent effect on the helo.Are these offsets still available in FSX? I have used the above offsets for FS2004 without any problem. Yes, they are all the same in FSX with FSUIPC4. I have several applications using them all the time (one being the Aerosoft GA28R cockpit driver) -- except for 089A which should be working as it did in FS9, but admittedly has not been tested yet (088C is the direct throttle and this is certainly working as it is used by Project Magenta in my 737 cockpit). Please enable IPC write logging, and also Monitor those offsets as type S16, with "normal log" checked, run your program then show me the resulting FSUIPC4.LOG file, so I can see what is happening. Regards Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 27, 2007 Report Share Posted August 27, 2007 I am creating an Automatic Flight Control sytem for a Helo It occurs to me that I've only ever used them for fixed wing aircraft. Maybe the controls in SimConnect for helos are changed in FSX? Can you see if your programming works okay in a fixed wing aircraft? If so, but not in a helo I'll need to dig deeper... Regards Pete Link to comment Share on other sites More sharing options...
lwha6500 Posted August 27, 2007 Author Report Share Posted August 27, 2007 What about FSUIPC offset: Joystick Control 0x310A Joystick Elevator 0x3328 Joystick Aileron 0x332A Joystick Rudder 0x332C Joystick Throttle 0x332E Are these offsets still active in FSX? I am also writing to these offsets for FSX with no apparent effect, but these same offests work correctly for FS2004? Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 27, 2007 Report Share Posted August 27, 2007 What about FSUIPC offset: Joystick Control 0x310A Joystick Elevator 0x3328 Joystick Aileron 0x332A Joystick Rudder 0x332C Joystick Throttle 0x332E Are these offsets still active in FSX? I am also writing to these offsets for FSX with no apparent effect, but these same offsets work correctly for FS2004? 310A (joystick disconnection) may only operate if the axes are intercepted -- which in recent versions of FSUIPC4 only happens if they are calibrated in FSUIPC4. I will have to work out ways of doing it for unregistered users or those not using FSUIPC4 assignments or calibrations. If I'm not intercepting the axes I cannot disconnect them. The others aren't for writing to -- that doesn't have any effect in either FSUIPC3 or 4. They are for reading the values which would have gone to FS if the settings in 310A had allowed. What did you think writing to them would do? Do you have any answers to my previous questions? Regards Pete Link to comment Share on other sites More sharing options...
lwha6500 Posted August 27, 2007 Author Report Share Posted August 27, 2007 Hello Pete: We are using Microsoft Flight Simulator 2004 on several projects for the U.S. Navy. We developed an Automatic Flight Control System for FS2004 using the FSUIPC offsets mentioned so far in this discussion. For FS2004, the AFCS works with fixed wing and rotor craft. For FSX we have just updated to your latest revision of FSUIPC and performed some experiments. There are some inconsistencies. At times the AFCS works and all offsets mentioned in this discussion are functional. We are able to capture the joystick data, drive our algorithim with it, and control the aircraft. Other times, everthing works except the throttle. We have tried using both throttle offsets (0x088c and 0x089a). 0x089a never worked. 0x088c does works on occasion. Also, we have had instances where all the offsets except the throttle (0x088c) work. At times the throttle offset (0x088c) and joystick offsets (0x310A, 0x3328, 0x332A, 0x332c, 0x332e) do not work at all. Whether these offsets will work or not, is known at startup time. Once they come up in working order, they appear to stay in working order. But it is a wild card at startup. This applies to rotor wing and fixed wing in FSX. I also wanted to ask you a question about you comment, "310A (joystick disconnection) may only operate if the axes are intercepted -- which in recent versions of FSUIPC4 only happens if they are calibrated in FSUIPC4. I will have to work out ways of doing it for unregistered users or those not using FSUIPC4 assignments or calibrations. If I'm not intercepting the axes I cannot disconnect them" .... Is there something that we are suppose to be do in terms of calibration to allow you to consistently intercept the joystick axis ??? Are you using simConnect through FSUIPC ? Any help would be greatly appretiated Thank You from NAVAIR Orlando Training Sytems Division Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 27, 2007 Report Share Posted August 27, 2007 Other times, everthing works except the throttle. We have tried using both throttle offsets (0x088c and 0x089a). 0x089a never worked. 0x088c does works on occasion. I will try to test 089A here, but I fear it may be too late for the next version, this week, and then I am away till mid-September. Really, when you ask for help, I need more information. I know 088A works fine, 100%, as it is used for many things. 089A is coded but I don't think has been explicitly re-tested in FSX, so i would need to do that. Also, we have had instances where all the offsets except the throttle (0x088c) work. At times the throttle offset (0x088c) and joystick offsets (0x310A, 0x3328, 0x332A, 0x332c, 0x332e) do not work at all. Whether these offsets will work or not, is known at startup time. Once they come up in working order, they appear to stay in working order. But it is a wild card at startup. This applies to rotor wing and fixed wing in FSX. I need information, please. There are plenty of diagnostic tools in FSUIPC4 as it stands -- IPC read and write logging. You can also log Axis data and specific offsets can be Monitored. If you Monitor the offsets and specify "normal log", you will also get the SimConnect reads and writes for those values logged. Please try to assemble some information for me to look at. I cannot operate in a vacuum. And ALWAYS ALWAYS state FSUIPC (4.???) and FSX (SP1?) version numbers! If these problems are with recent versions (4.12 or later) then it may well be due to the way registered versions are only performing axis interception on an as-needed basis. First, the axes are only intercepted when they are assigned via FS or to FS controls (not direct to fSUIPC4 calibration from FSUIPC4 axis assignment), and even then they are only intercepted after their first actual use. This is all designed to remove problems of axis interception when this action is not specifically needed. If your use of 310A occurs before any real axis input has been seen (since the last aircraft load) then there won't be any interception, so the facility won't work. This would not, however, explain why you are finding that writing to 0BB2 etc has no effect. Writes to these are entirely independent of all this axis and control interception. The writes should always result in an onward write to the appropriate SimConnect "simvar". It certainly does here. Possibly you are misinterpreting what is happening, through not having done any separate tests or looked at any logs? Is there something that we are suppose to be do in terms of calibration to allow you to consistently intercept the joystick axis ??? Not really. In very earlier versions of FSUIPC4 the joystick axes were ALWAYS intercepted. However, because of SimConnect issues, causing TCP/IP queuing and subsequent extended latency in control surface operation (gradually extending to many seconds over a period), in later versions (still last year) I made FSUIPC4 by default NOT intercept axes on unregistered installs of FSUIPC4 -- this was done on the basis that the interception was only really needed for folks doing calibration or mapping in FSUIPC, and they had to be registered to use these facilities. To be honest, with the desire to avoid so many problems, I clean forgot about the 310A facility and its need for axis interception. This is something I will certainly work on fixing now that it has been brought up -- the intercept needs to be activated when 310A interception is activated, and possibly released again afterwards. Are you using simConnect through FSUIPC ? FSUIPC4 is almost 100% using SimConnect. The exceptions are minor indeed, and will be eliminated when possible. Any help would be greatly appretiated Please also help me to help you. More information, please! It is a shame you didn't raise this a week or so ago. I have precisely two days before I am away for nearly two weeks. I am due to release version 4.16 tomorrow or Wednesday. I will do my best to fit something in, but it looks likely now that this won't get resolved for a while. Regards Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 28, 2007 Report Share Posted August 28, 2007 Any help would be greatly appretiated Okay, I've been doing some testing and this is what I've found: WORKING: 1. Writing to offsets 088C (Throttle1), 0BB6 (Aileron control) and 0BBA (rudder control) works fine. I can't make that go wrong at all. 2. Offsets 3328 - 3330, which are read-only (something you appear to have misunderstood?) correctly give the input values for the relevant control axes. 3. The inhibition of axis inputs via 310A works correctly ONLY IF the axes are calibrated in FSUIPC4, and assigned to FS controls (not the "direct to FSUIPC" method in FSUIPC's axis assignment option). NOT WORKING: 4. For some reason, writing to 0BB2 (elevator control) isn't working 100%. I am looking at this now. It may be my joystick control jittering and overriding my inputs, as there really is no internal differences in the treatment of the three main surface controls. 5. Writing to 089A to control the throttle works just like writing to 088C -- until you have inhibited it via 310A. After that, even if it is allowed again via 310A, it doesn't do anything. I'm checking this too. 6. The 310A inhibits don't work when the axes are not being intercepted. To be sure they are intercepted, the axes have to be assigned to FS controls, either normally via FSX, or specifically in FSUIPC4, then calibrated in FSUIPC4. This is an oversight on my part, a result of recent changes in this area. Hopefully all three of these problems should be easy enough to fix, and I am working on that today. If I succeed these fixes will be in FSUIPC 4.16 today or tomorrow, but otherwise they won't be fixed till mid-September (i.e. in about two weeks or so). Please confirm that the problems you are observing coincide with the ones I have identified. I am still starved of any useful information from you, so if I as missing the point I'm afraid your problems will not be fixed for some time. Regards Pete Link to comment Share on other sites More sharing options...
lwha6500 Posted August 28, 2007 Author Report Share Posted August 28, 2007 Hello Pete: Thanks for the quick response.... We are using FSUIPC ver 4.151 and FSX SP1 I have captured a log file using Throttle offset 0x089a. We uderstand that there is a problem with this offset but I have provided the log file anyway. We do understand that Offsets 3328 - 3330 are read only and that is how we use them. We went ahead and calibrated the joystick through FSUIPC and switched back to throttle offset 0x088c and at the moment everything seems to be working fine. But we have done this test in the past (without the calibration through FSUIPC) and have had problems with the elevator control. We have tested this morning and cannot recreate. We have provided you with a log file using offset 0x088c. I am trying to attach the log file and I keep getting the error message that the extension is not allowed...so I am not sure if it attached....... 54406 System time = 09:23:19, FSX time = 09:22:28 (13:22Z) 54593 Aircraft="Sikorsky SH-60B SeaHawk-NavAir" 55765 Advanced Weather Interface Enabled 453906 READ0 0264, 2 bytes: 00 00 .. 453906 READ0 05DC, 2 bytes: 00 00 .. 453906 READ0 0020, 4 bytes: 00 00 00 00 .... 453906 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 453906 READ0 0574, 4 bytes: 23 00 00 00 #... 453906 READ0 3324, 4 bytes: 74 00 00 00 t... 453906 READ0 02BC, 4 bytes: 00 00 00 00 .... 453906 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 453906 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 453906 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 453906 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 453906 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 453906 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 453906 READ0 0578, 4 bytes: F3 BB F7 FF .... 453906 READ0 057C, 4 bytes: 00 00 00 00 .... 453906 READ0 0580, 4 bytes: 69 04 C8 08 i... 453907 READ0 2910, 4 bytes: 80 01 02 00 .... 453907 READ0 2914, 4 bytes: 80 02 02 00 .... 453907 READ0 2918, 4 bytes: 80 03 02 00 .... 453907 READ0 291C, 4 bytes: 80 05 02 00 .... 453907 READ0 2920, 4 bytes: 80 06 02 00 .... 453907 READ0 2924, 4 bytes: 80 20 02 00 . .. 453907 READ0 2928, 4 bytes: 80 22 02 00 .".. 453907 READ0 292C, 4 bytes: 80 24 02 00 .$.. 453907 READ0 2930, 4 bytes: 80 26 02 00 .&.. 453907 READ0 3328, 2 bytes: 00 00 .. 453907 READ0 332A, 2 bytes: 00 00 .. 453907 READ0 332C, 2 bytes: 00 00 .. 453907 READ0 332E, 2 bytes: F2 33 .3 454000 READ0 0264, 2 bytes: 00 00 .. 454000 READ0 05DC, 2 bytes: 00 00 .. 454000 READ0 0020, 4 bytes: 00 00 00 00 .... 454000 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454000 READ0 0574, 4 bytes: 23 00 00 00 #... 454000 READ0 3324, 4 bytes: 74 00 00 00 t... 454000 READ0 02BC, 4 bytes: 00 00 00 00 .... 454000 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454000 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454000 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454000 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454000 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454000 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454000 READ0 0578, 4 bytes: F3 BB F7 FF .... 454000 READ0 057C, 4 bytes: 00 00 00 00 .... 454000 READ0 0580, 4 bytes: 69 04 C8 08 i... 454000 READ0 2910, 4 bytes: 80 01 02 00 .... 454000 READ0 2914, 4 bytes: 80 02 02 00 .... 454000 READ0 2918, 4 bytes: 80 03 02 00 .... 454000 READ0 291C, 4 bytes: 80 05 02 00 .... 454000 READ0 2920, 4 bytes: 80 06 02 00 .... 454000 READ0 2924, 4 bytes: 80 20 02 00 . .. 454000 READ0 2928, 4 bytes: 80 22 02 00 .".. 454000 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454000 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454000 READ0 3328, 2 bytes: 00 00 .. 454000 READ0 332A, 2 bytes: 00 00 .. 454000 READ0 332C, 2 bytes: 00 00 .. 454000 READ0 332E, 2 bytes: F2 33 .3 454094 READ0 0264, 2 bytes: 00 00 .. 454094 READ0 05DC, 2 bytes: 00 00 .. 454094 READ0 0020, 4 bytes: 00 00 00 00 .... 454094 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454094 READ0 0574, 4 bytes: 23 00 00 00 #... 454094 READ0 3324, 4 bytes: 74 00 00 00 t... 454094 READ0 02BC, 4 bytes: 00 00 00 00 .... 454094 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454094 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454094 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454094 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454094 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454094 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454094 READ0 0578, 4 bytes: F3 BB F7 FF .... 454094 READ0 057C, 4 bytes: 00 00 00 00 .... 454094 READ0 0580, 4 bytes: 69 04 C8 08 i... 454094 READ0 2910, 4 bytes: 80 01 02 00 .... 454094 READ0 2914, 4 bytes: 80 02 02 00 .... 454094 READ0 2918, 4 bytes: 80 03 02 00 .... 454094 READ0 291C, 4 bytes: 80 05 02 00 .... 454094 READ0 2920, 4 bytes: 80 06 02 00 .... 454094 READ0 2924, 4 bytes: 80 20 02 00 . .. 454094 READ0 2928, 4 bytes: 80 22 02 00 .".. 454094 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454094 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454094 READ0 3328, 2 bytes: 00 00 .. 454094 READ0 332A, 2 bytes: 00 00 .. 454094 READ0 332C, 2 bytes: 00 00 .. 454094 READ0 332E, 2 bytes: F2 33 .3 454187 READ0 0264, 2 bytes: 00 00 .. 454188 READ0 05DC, 2 bytes: 00 00 .. 454188 READ0 0020, 4 bytes: 00 00 00 00 .... 454188 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454188 READ0 0574, 4 bytes: 23 00 00 00 #... 454188 READ0 3324, 4 bytes: 74 00 00 00 t... 454188 READ0 02BC, 4 bytes: 00 00 00 00 .... 454188 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454188 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454188 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454188 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454188 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454188 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454188 READ0 0578, 4 bytes: F3 BB F7 FF .... 454188 READ0 057C, 4 bytes: 00 00 00 00 .... 454188 READ0 0580, 4 bytes: 69 04 C8 08 i... 454188 READ0 2910, 4 bytes: 80 01 02 00 .... 454188 READ0 2914, 4 bytes: 80 02 02 00 .... 454188 READ0 2918, 4 bytes: 80 03 02 00 .... 454188 READ0 291C, 4 bytes: 80 05 02 00 .... 454188 READ0 2920, 4 bytes: 80 06 02 00 .... 454188 READ0 2924, 4 bytes: 80 20 02 00 . .. 454188 READ0 2928, 4 bytes: 80 22 02 00 .".. 454188 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454188 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454188 READ0 3328, 2 bytes: 00 00 .. 454188 READ0 332A, 2 bytes: 00 00 .. 454188 READ0 332C, 2 bytes: 00 00 .. 454188 READ0 332E, 2 bytes: F2 33 .3 454281 READ0 0264, 2 bytes: 00 00 .. 454281 READ0 05DC, 2 bytes: 00 00 .. 454281 READ0 0020, 4 bytes: 00 00 00 00 .... 454281 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454281 READ0 0574, 4 bytes: 23 00 00 00 #... 454281 READ0 3324, 4 bytes: 74 00 00 00 t... 454281 READ0 02BC, 4 bytes: 00 00 00 00 .... 454281 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454281 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454281 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454281 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454281 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454281 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454281 READ0 0578, 4 bytes: F3 BB F7 FF .... 454281 READ0 057C, 4 bytes: 00 00 00 00 .... 454281 READ0 0580, 4 bytes: 69 04 C8 08 i... 454281 READ0 2910, 4 bytes: 80 01 02 00 .... 454282 READ0 2914, 4 bytes: 80 02 02 00 .... 454282 READ0 2918, 4 bytes: 80 03 02 00 .... 454282 READ0 291C, 4 bytes: 80 05 02 00 .... 454282 READ0 2920, 4 bytes: 80 06 02 00 .... 454282 READ0 2924, 4 bytes: 80 20 02 00 . .. 454282 READ0 2928, 4 bytes: 80 22 02 00 .".. 454282 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454282 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454282 READ0 3328, 2 bytes: 00 00 .. 454282 READ0 332A, 2 bytes: 00 00 .. 454282 READ0 332C, 2 bytes: 00 00 .. 454282 READ0 332E, 2 bytes: F2 33 .3 454375 READ0 0264, 2 bytes: 00 00 .. 454375 READ0 05DC, 2 bytes: 00 00 .. 454375 READ0 0020, 4 bytes: 00 00 00 00 .... 454375 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454375 READ0 0574, 4 bytes: 23 00 00 00 #... 454375 READ0 3324, 4 bytes: 74 00 00 00 t... 454375 READ0 02BC, 4 bytes: 00 00 00 00 .... 454375 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454375 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454375 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454375 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454375 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454375 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454375 READ0 0578, 4 bytes: F3 BB F7 FF .... 454375 READ0 057C, 4 bytes: 00 00 00 00 .... 454375 READ0 0580, 4 bytes: 69 04 C8 08 i... 454375 READ0 2910, 4 bytes: 80 01 02 00 .... 454375 READ0 2914, 4 bytes: 80 02 02 00 .... 454375 READ0 2918, 4 bytes: 80 03 02 00 .... 454375 READ0 291C, 4 bytes: 80 05 02 00 .... 454375 READ0 2920, 4 bytes: 80 06 02 00 .... 454375 READ0 2924, 4 bytes: 80 20 02 00 . .. 454375 READ0 2928, 4 bytes: 80 22 02 00 .".. 454375 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454375 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454375 READ0 3328, 2 bytes: 00 00 .. 454375 READ0 332A, 2 bytes: 00 00 .. 454375 READ0 332C, 2 bytes: 00 00 .. 454375 READ0 332E, 2 bytes: F2 33 .3 454469 READ0 0264, 2 bytes: 00 00 .. 454469 READ0 05DC, 2 bytes: 00 00 .. 454469 READ0 0020, 4 bytes: 00 00 00 00 .... 454469 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454469 READ0 0574, 4 bytes: 23 00 00 00 #... 454469 READ0 3324, 4 bytes: 74 00 00 00 t... 454469 READ0 02BC, 4 bytes: 00 00 00 00 .... 454469 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454469 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454469 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454469 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454469 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454469 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454469 READ0 0578, 4 bytes: F3 BB F7 FF .... 454469 READ0 057C, 4 bytes: 00 00 00 00 .... 454469 READ0 0580, 4 bytes: 69 04 C8 08 i... 454469 READ0 2910, 4 bytes: 80 01 02 00 .... 454469 READ0 2914, 4 bytes: 80 02 02 00 .... 454469 READ0 2918, 4 bytes: 80 03 02 00 .... 454469 READ0 291C, 4 bytes: 80 05 02 00 .... 454469 READ0 2920, 4 bytes: 80 06 02 00 .... 454469 READ0 2924, 4 bytes: 80 20 02 00 . .. 454469 READ0 2928, 4 bytes: 80 22 02 00 .".. 454469 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454469 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454469 READ0 3328, 2 bytes: 00 00 .. 454469 READ0 332A, 2 bytes: 00 00 .. 454469 READ0 332C, 2 bytes: 00 00 .. 454469 READ0 332E, 2 bytes: F2 33 .3 454563 READ0 0264, 2 bytes: 00 00 .. 454563 READ0 05DC, 2 bytes: 00 00 .. 454563 READ0 0020, 4 bytes: 00 00 00 00 .... 454563 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454563 READ0 0574, 4 bytes: 23 00 00 00 #... 454563 READ0 3324, 4 bytes: 74 00 00 00 t... 454563 READ0 02BC, 4 bytes: 00 00 00 00 .... 454563 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454563 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454563 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454563 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454563 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454563 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454563 READ0 0578, 4 bytes: F3 BB F7 FF .... 454563 READ0 057C, 4 bytes: 00 00 00 00 .... 454563 READ0 0580, 4 bytes: 69 04 C8 08 i... 454563 READ0 2910, 4 bytes: 80 01 02 00 .... 454563 READ0 2914, 4 bytes: 80 02 02 00 .... 454563 READ0 2918, 4 bytes: 80 03 02 00 .... 454563 READ0 291C, 4 bytes: 80 05 02 00 .... 454563 READ0 2920, 4 bytes: 80 06 02 00 .... 454563 READ0 2924, 4 bytes: 80 20 02 00 . .. 454563 READ0 2928, 4 bytes: 80 22 02 00 .".. 454563 READ0 292C, 4 bytes: 80 24 02 00 .$.. 454563 READ0 2930, 4 bytes: 80 26 02 00 .&.. 454563 READ0 3328, 2 bytes: 00 00 .. 454563 READ0 332A, 2 bytes: 00 00 .. 454563 READ0 332C, 2 bytes: 00 00 .. 454563 READ0 332E, 2 bytes: F2 33 .3 454656 READ0 0264, 2 bytes: 00 00 .. 454656 READ0 05DC, 2 bytes: 00 00 .. 454656 READ0 0020, 4 bytes: 00 00 00 00 .... 454656 READ0 0570, 4 bytes: C7 47 26 5A .G&Z 454656 READ0 0574, 4 bytes: 23 00 00 00 #... 454656 READ0 3324, 4 bytes: 74 00 00 00 t... 454656 READ0 02BC, 4 bytes: 00 00 00 00 .... 454656 READ0 3090, 8 bytes: 81 BD EA E8 5C 5E E6 BF ....\^.. 454656 READ0 3098, 8 bytes: F7 D8 19 08 74 82 A6 BF ....t... 454656 READ0 30A0, 8 bytes: FD B4 E2 D9 D3 A7 64 3F ......d? 454656 READ0 30A8, 8 bytes: 4E 2A 84 80 16 FA E8 3E N*.....> 454656 READ0 30B0, 8 bytes: 5B 14 BA 15 8C 76 D7 BE [....v.. 454656 READ0 30B8, 8 bytes: 86 5F E7 95 DE 7E 87 BE ._...~.. 454656 READ0 0578, 4 bytes: F3 BB F7 FF .... 454656 READ0 057C, 4 bytes: 00 00 00 00 .... 454656 READ0 0580, 4 bytes: 69 04 C8 08 i... 454656 READ0 2910, 4 bytes: 80 01 02 00 .... 454656 READ0 2914, 4 bytes: 80 02 02 00 Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 28, 2007 Report Share Posted August 28, 2007 We are using FSUIPC ver 4.151 and FSX SP1 4.151? That's pretty old. the current formal release is 4.152, since a month ago, and there's a much-improved 4.156 available above which was available since two weeks ago. I have captured a log file using Throttle offset 0x089a. We uderstand that there is a problem with this offset but I have provided the log file anyway. Actually I've just finished testing this (in 4.156) and I cannot find any problem with it at all. Of the problems I mentioned in my previous message, the true status, having gone into them in some detail, is as follows: 4. For some reason, writing to 0BB2 (elevator control) isn't working 100%. I am looking at this now. It may be my joystick control jittering and overriding my inputs, as there really is no internal differences in the treatment of the three main surface controls. This was a result of a bug in the "ApplyHeloTrim" facility, which I've fixed now. If you haven't enabled this then the elevator control via 0BB2 works fine. 5. Writing to 089A to control the throttle works just like writing to 088C -- until you have inhibited it via 310A. After that, even if it is allowed again via 310A, it doesn't do anything. I'm checking this too. This turned out to be a bug only in the automatic clearing of the 310A inhibits after 10 seconds or so, unless replenished. Writing 0 to 310A did restore the throttle link from 089A to 088C. There is and was no other problem with 089A -- it basically simply operates 088C unless inhibited. I've fixed the 10 second (approx) clearing of the inhibits now. 6. The 310A inhibits don't work when the axes are not being intercepted. To be sure they are intercepted, the axes have to be assigned to FS controls, either normally via FSX, or specifically in FSUIPC4, then calibrated in FSUIPC4. This is an oversight on my part, a result of recent changes in this area. This wasn't quite correct the way I stated it. In fact, if the axes are assigned directly in FSUIPC to FSUIPC calibration, the inhibits worked fine. The only problem was for unregistered users or those who were neither assigning axes direct in FSUIPC or calibrating axes in FSUIPC. I've dealt with this by automatically intercepting the relevant axes once the inhibits are set in 310A. These three fixes are tested and working here in version 4.16 which will be released before the end of the day. Please keep an eye on the FSX downloads announcements above. I'm afraid I won't be able to do much more, if anything is needed, till I return in mid-September. I am here tomorrow and will answer questions, but there will be no more changes till then. We have provided you with a log file using offset 0x088c. I am trying to attach the log file and I keep getting the error message that the extension is not allowed. Always ZIP attachments. In any case, judging by the fragment you included with your message you are not logging IPC writes, so I cannot tell what you are trying to do. You have evidently only set the IPC read logging option. Please refer back to the details of the logging I suggested, which also included Monitoring so that the SimConnect exchanges would be seen. Finally, please do not report problems without first using the very latest version of FSUIPC available. I have no idea why you are still using 4.151 which was an interim Beta replaced very quickly by the formal release of 4.152 over a month ago. Version 4.156 has been available in the Downloads above for two weeks. Now you may as well wait for 4.16. Regards Pete Link to comment Share on other sites More sharing options...
lwha6500 Posted August 28, 2007 Author Report Share Posted August 28, 2007 Thank You for the help.. Will version 4.16 be posted on your main web page ? Currently it shows 4.152 and you mentioned that 4.156 is available. Is there another place where we should be downloading from ? Thanks again for the help. Link to comment Share on other sites More sharing options...
Pete Dowson Posted August 28, 2007 Report Share Posted August 28, 2007 Will version 4.16 be posted on your main web page ? Currently it shows 4.152 and you mentioned that 4.156 is available. I don't have any web pages. If you mean the Schiratti one, that's a page where Enrico Schiratti, of Project Magenta fame, assembles my various FS efforts. I actually distribute the programs to many website managers but they don't all post them. Version 4.156 has been available above (i.e. in the FSX downloads announcement) for over two weeks-- I've just replaced it by 4.16. Haven't you ever noticed the Announcements? They should always be your first port of call, especially if you are a developer. There's more up-to-date developer SDK bits for FSX there too. How do you gert to posting these thread messages without ever seeing the Announcements which occur right at the top? Regards Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now