Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by airforce2

  1. Thanks Pete. Never saw this before, because I had never tried using the FSUIPC sync. I have a custom hardware input handler that was managing that, but small differences in axis values, presumably due to DirectX calibration issues were bugging me. The handler takes an input value from the hardware, applies a mathematical transform to convert the input to a linear transducer position, and then injects it into the sim with a virtual device driver. When my sync code is active, the value injected on each throttle axis via the virtual joystick is the same for all axes, but apparently some sort of MS device calibration is being applied, and the values for the axes aren't equal by the time FSUIPC gets them. Close, yes, but not equal. So I decided to try the sync in FSUIPC and discovered this. BTW, (I hate to ask) is the same issue present for reversed prop and mixture axes when "Throttle sync to sync Thr/Prop/Mix" is set? Cheers Bob
  2. Hi Pete; I'm using P3D 3.4.22 and FSUIPC 4.963 (same behavior also in 4.962a) I have my throttle axes reversed in the joystick calibration page. If I engage the throttle sync (with hotkey, or toggled using the control in the button programming page), my reversed throttle axes are flipped back to their unreversed state while sync is active, making full fwd on the power levers idle and full back max power. When I hit the toggle again to disengage throttle sync, the axes go back to their (desired) reversed state. Cheers Bob Scott
  3. Pete...the link says "q" but the file it points to is "p"--is that a problem? Regards Bob
  4. Hi Pete; Just sorted through a vexing issue with FSUIPC 4.959n on FSX, where assigned alpha joyname assignments are not respected when multiple devices with identical names (but unique serial numbers and GUIDs) are present. It appears that the joyname FSUIPC is detecting for a device is related somehow to the ordering of the GUIDs (inversely?), and does not respect the joyname assignment in the ini. I have attached an excerpt from the .ini file where the joynames are defined, and a log file. If I define two joynames as below (the short numbers represent GUIDs relative to their lexicographic order): Q=BU0836X Interface Q.GUID={1} Y=BU0836X Interface Y.GUID={2} or with GUIDs swapped Q=BU0836X Interface Q.GUID={2} Y=BU0836X Interface Y.GUID={1} either way the yoke controller was always detected as joystick Q, which is my throttle quadrant, and the quadrant was recognized as joystick Y, my yoke. Without the alpha assignment, the yoke's joystick controller properly associated with GUID 2 and worked. If I change the assigned letters as below, then the yoke controller is detected as joystick P and the quadrant as Q, again even when the GUIDs are reversed: Q=BU0836X Interface Q.GUID={1} P=BU0836X Interface P.GUID={2} or with GUIDs swapped Q=BU0836X Interface Q.GUID={2} P=BU0836X Interface P.GUID={1} So this second case works to make the associations I wanted, but the effect is not apparently because of the joynames assignment, but rather the order of the assigned letters and perhaps something else in the background (device serial number maybe?) Regards Bob Scott log etc.zip
  5. Bueno...thanks. Take your time...I cannibalized a bunch of unused keyboard commands in P3D and temporarily redefined the commands using some of the non-shifted keypresses I freed up. Cheers Bob Scott
  6. Hi Pete; Using FSUIPC 4.955g (same problem with 4.955d it appears) in P3D 3.3.5 I have a profile that sends keystrokes as an axis is moved through its range. I set it up in the sim, and it works as defined until I shut down and restart the sim, and then it takes the SHIFT-F1 through SHIFT-F5 mappings that I had set and redefines them as (unshifted) F1-F5. I define, for example, the first one as keycode 112+1, then 113+1 etc to 116+1. After reload, they always revert to 112+0...116+0 From FSUIPC.ini in the axes.PMDG 777 section after shutting down: 11=QR,8 12=QR,D,-15859,-13184,1070,368 -{ Entering=key press & release: shft+F1 }- 13=QR,U,-12398,-8164,1070,369 -{ Entering=key press & release: shft+F2 }- 14=QR,B,-7999,-552,1070,370 -{ Entering=key press & release: shft+F3 }- 15=QR,B,2013,4261,1070,371 -{ Entering=key press & release: shft+F4 }- 16=QR,U,10191,15873,1070,372 -{ Entering=key press & release: shft+F5 }- And here's the same segment of the .ini after sim is restarted: 11=QR,8 12=QR,D,-15859,-13184,1070,112 -{ Entering=key press & release: F1 }- 13=QR,U,-12398,-8164,1070,113 -{ Entering=key press & release: F2 }- 14=QR,B,-7999,-552,1070,114 -{ Entering=key press & release: F3 }- 15=QR,B,2013,4261,1070,115 -{ Entering=key press & release: F4 }- 16=QR,U,10191,15873,1070,116 -{ Entering=key press & release: F5 }- Any ideas? Cheers Bob Scott
  7. Thanks Ian. I finally got to it on my Verizon cellular data connection, but both Comcast and OpenDNS are not finding it still. I guess it'll update eventually... Cheers Bob Scott
  8. I can't get the main download links from schiratti.com nor the beta downloads on the updated modules page here to work. I get a "could not find host" error (i.e. DNS server is not able to find/resolve fsuipc.simflight.com). Same thing for the main http://simflight.compage...but oddly, the forums still seem to work. Regards Bob Scott
  9. Hi Pete; I am getting a Win 7 "A fatal error has occured" message in P3D V2 that appears related to FSUIPC 4.923. I have a bare install of P3D with only FSUIPC added--if I disable FSUIPC in the dll.xml, exit from P3D occurs normally. If I enable FSUIPC, it always crashes on exit. It appears to be a relatively benign error, in that I can't see any obvious adverse effect. As I recall, there were some menu-system related problems with P3D V1.4 a while back...wonder if it might be related. Cheers
  10. Pete--I just tested your suggested fix from post #12 above with UseAxisControlsForNRZ=Yes in the 777's joystick calibrations section. Worked as advertised--now the throttle axes do not interfere with the PMDG autothrottles. Thanks for that! Cheers Bob
  11. Hi Pete; Was tearing what little is left of my hair out last night trying to discern why the autobrakes in the PMDG NGX had suddenly stopped working. I had apparently made a global change when I assigned the pedal axes direct to calibration while trying to get the Aerosoft Scarebus to behave in-between catastrophic CTDs. I deleted the FSUIPC assignment for the pedal axes and set the NGX' aircraft-specific calibration page to "not processed", but could not get the autobrakes on the NGX to return to working. It turned out that FSUIPC had left a dangling assignment in the calibration section of the .ini file (LeftBrake=0) which somehow had FSUIPC still intervening with the brake axis or axes. The PMDG NGX autobrake does not play well with others--pretty much any intervention by FSUIPC causes the autobrakes on the NGX to malfunction. I found that I had to manually remove the LeftBrake= line from the Calibration section to get things to work again. Oddly, the RightBrake= line had been deleted, so I pass this along in case there might be a minor bug that's preventing the removal of the appropriate lines in the .ini when the assignment/calibration is deselected in the menu. I'm using 4.859m Happy New Year to you and yours.
  12. Pete; I've been using 2/3/4 separate throttles and a single-lever all-throttle reverse lever config with my PFC gear forever. I recently replaced the pots in my PFC yoke/quadrant/rudders with Hall Effect sensors and the quadrant electronics with Bodnar USB joystick interface boards, so I can't use the PFC driver any more to do that. The commercial add-on in question appears to intercept throttle inputs at 3330/3332 and then uses those as inputs to a FADEC simulation...effectively fly-by-wire control for the engines. If the throttle axis inputs are negative by virtue of a throttle lever calibrated to go into reverse range, the FADEC code sees those negative values on offsets 3330/3332 and puts the engines into reverse. If the reverse range is selected with a separate throttle lever, 3330/3332 remain at zero and it has no effect. I guess what might be baffling me is that there is no reverser "axis" listed in either the FS control axes menu or the FSUIPC for Programmers document...my belief was that the reverser input was somehow combined with the throttle inputs and applied to the simulation via a negative value on the throttle axis, as throttle is the only "axis" listed in either document for engine RPM control. Anyway, I ended up solving the problem by programming the reverse lever to send a string of FS throttle-decrease controls...but I remain curious as to where the reverse input from a separate axis is applied to the simulation. Cheers Bob
  13. Hi Pete; I'm trying to get a joystick controller that uses two throttle axes and a separate reverse axis to work with an FSX add-on that uses FSUIPC4. When reverser is applied (the output as shown on the reverser calibration page appears OK, ranging from 0 to -4096), the throttle input offsets at 3330 and 3332 do not reflect the reverse input, so the add-on does not respond to the reverser application. If I set up the throttle axes to have a reverse range, then the reverse values are reflected and the reverser works. Is the absence of the reverser input from a separate reverse axis at the post-calibration throttle offsets a bug or a feature? Cheers
  14. Hi Pete...yes, I did try that, but how does one get a calibrated value sent direct to an FS axis? All I could seem to manage to get to the axis was the raw PFC axis value rescaled to the FS axis range. On a related note, is there a way of setting the reversers via an axis input? The regular throttle offsets, for example at 088C/089A, don't work with the Wilco bus, as his code watches for input events. When I send values from -16383 to 16383 to the axis, that corresponds to the 0-100% throttle range. Cheers Bob
  15. Hi Pete; I just did something like what you recommended here to get my PFC throttle quadrant to work with the Wilco Scarebus. In doing so I got to thinking that it might be a good feature to add to either the PFC driver or FSUIPC to allow a FSUIPC-calibrated value to be applied directly to the axis input. Anyone using a standard HID control device has the option of calibrating that in Windows or possibly in FS itself...with a PFC setup, the best I could do with FSUIPC was to send uncalibrated values direct to the axis, which makes it impossible to scale the inputs, establish dead zones or use the control curves elsewhere available. It wasn't hard to write a mini-driver to do that, but custom programmatic solutions are only available to a relatively small number of us with that skillset. PFC users in particular might appreciate being able to use their gear with the growing number of fly-by-wire implementations. Cheers Bob
  16. A quick post-script on this--it appears the problem with ATC.DLL crashes was related to either flashing a new BIOS that put my overclock right on the ragged edge of stability, or some issues with nVidia's 196.21 drivers, or some combo of the two. Not sure why I saw the same ATC.DLL fault each time, but getting the overclock stable again with a Vcore change and reverting to 182.50 drivers seems to have slain the dragon. Or maybe it was the dried lizard's feet positioned facing towards Salem on top of the CPU case... Also, FWIW, I had unchecked the voice checkbox in the FSX sound control dialog, but left the slider up--turns out that does not turn off the voices. That checkbox only allows the voice sounds to be redirected to a different sound device than the other acft and environment sounds (i.e. to a headset). Turning the voice slider down is what's needed to kill the ATC sounds. Cheers Bob Scott Colonel, USAF (ret) ATP IMEL Gulfstream II-III-IV-V Colorado Springs, CO
  17. Hi Pete; I am seeing the same thing... a lot of crashes due to atc.dll in FSX when using Radar Contact v4.3, and also I am hearing FSX's ATC voices at low level in FSX even with the "voice" checkbox unchecked in the sound dialogue. I run RC on a remote PC via WideFS. Regards Bob Scott Colonel, USAF (ret) ATP IMEL Gulfstream II-III-IV-V Colorado Springs, CO
  18. Hi Ed; My suggestion is, in addition for testing for presence of a DirectInput throttle axis, to also test the single byte FSUIPC offset 0x3373 for a nonzero value, which indicates that a PFC control system is present and active. My understanding of your control methodology leads me to believe it will work unmodified with the PFC systems, as the PFC throttle control inputs will be present at offsets 3330 and 3332 no differently than a joystick axis, and right where you watch for them in your code now. There is a fairly sizeable group of us that use these (pricey) high-end flight controls, so the small effort to include us in your coding considerations will result in enough sales to make it worth doing. Regards Bob Scott Colonel, USAF (ret) ATP IMEL Gulfstream II-III-IV-V Colorado Springs, CO
  19. Pete; I don't see anything specific on the topic. The aircraft-specific assignments are made when you press the "assign to aircraft" button in the driver dialogue window. It places an entry in the Aircraft Quadrants section of the ini file: aircraft_title=Uxx where Uxx is one of the 15 quadrant definitions, yes? The question is, can I use a substring, e.g. Feelthere A3=u15 to catch every aircraft that starts with "Feelthere A3", for example: Feelthere A318IAE Feelthere A320CFM Feelthere A319CJ etc etc Cheers
  20. Hi Pete; Are Short names (aircraft title substring matches) enabled in the PFC driver Aircraft Quadrants section like they are in FSUIPC? My Aircraft Quadrants section in pfc.ini is immense...shortnames could cut that down to size considerably. Cheers
  21. OK, thanks Pete. I did previously check the .dll digital sig per the docs. However, before I run FS I use always Ken Salter's FSAutoStart utility, as many others do. In FS AutoStart I discovered that I had the Cryptographic Service selected to be stopped per the program's recommendation. FYI for the future...may be a good idea to test that the service is running and throw an error code if not, given the wide usage of FSAutoStart and the fact that it explicitly recommends people stop the crypto service. Your call, of course. But...the problem was indeed intermittent...however that error was coming from FSLook, not from FSUIPC directly. Cheers
  22. Pete; When using FSUIPC 3.72 and FSLook from the v27 SDK, I am getting intermittent errors from FSLook complaining about the version number of FSUIPC. It's a sporadic thing, but almost always comes up, especially with more complex aircraft. I recently saw a post on AVSIM with another guy using 3.72 seeing a version error reported by the PMDG 737 panel. Reverting to V3.70 stops the behavior. Cheers
  23. Pete; The electrons are streaking your way now. Cheers
  24. Pete; Having trouble trying to program my PFC yoke buttons in FSUIPC in a new FSX installation. Programming buttons within the PFC driver works OK, but if I go to FSUIPC Buttons+Switches tab, and press the PFC button, nothing happens. Have repaired SimConnect, and tried 4-5 versions back from 4.03/4.065...same thing each time. Regards
  • 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.