Jump to content
The simFlight Network Forums

airforce2

Members
  • Content count

    181
  • Joined

  • Last visited

Community Reputation

0 Neutral

About airforce2

  • Rank
    Advanced Member
  • Birthday 01/01/1970

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Colorado, USA
  1. Pete; Ah...OK. In the axis assignment options, "Steering Set" is only available in the "Send to FS as normal axis" drop-down, and "Steering Tiller" is only available in the "Send direct to FSUIPC Calibration" drop-down. I had the misconception that I had to use the direct-to-calibration method if I wanted to apply calibration to the axis, but a careful re-reading of the docs makes it clear that I don't--calibration is, in fact, also available to axes (including Steering Set) assigned via "send to FS as normal axis". Great...that makes it a lot simpler than the gyrations I was going through to make this work. Cheers Bob
  2. OK, Pete...no hurries, no worries. I have things functioning well with my programmatic solution, but suspect other FSUIPC users may find themselves wanting something like this as a better way to work NWS in the 'bus. I suspect FSX/P3D v2-3 users of the FSL A320 might also find it useful, though I have never used this add-on in those platforms because of the heavy VAS footprint on a 32-bit sim. Have fun in Spain! Cheers Bob Scott
  3. Pete; I ran into an issue with the FSL A320 and FSUIPC steering tiller control. The steering control in the FSL panel sets the nosewheel steering angle as an exponential function of the tiller input, which makes fine control of the nosewheel at steering angles above ~10 deg nearly impossible using the short-throw (~15 deg) twist-grip axis on my T.16000M stick. I tried using the slope function by assigning the rudder and steering tiller axes as direct to calibration and then setting a negative slope (-4) in the tiller axis calibration to counteract the excessive nonlinearity, but the rub is that apparently the combined tiller/rudder input is being made to the rudder axis and not to the steering axis in P3D. I was able to make it work programmatically in my flight control driver by reading the post-calibration tiller value at offset 0C08 and then rewriting that direct to the FS steering set control (66818 via write to offset 3110). But...it would probably be helpful for others that don't have custom-programmed flight control drivers to be able to send a calibrated steering input to the steering axis rather than the rudder axis. The FSL Scarebus does its own mixing of the tiller and rudder inputs, and expects the tiller input to come in via the P3D steering control. Perhaps a special case where MaxSteerSpeed=0 could be used to force no mixing, but still allow a calibrated value to be sent via the direct-to-calibration path to the native steering axis rather than mixed and sent as a rudder input? Cheers Bob Scott
  4. Pete; In my case, I have a "smart" sync coded that, when active, syncs the axes when the axis inputs are set close to the master axis for a second or so, and unsyncs them automatically if a throttle is moved out of the capture range (e.g. engine failure, use of inboards or asymmetric thrust during taxi etc). So if I move a slave throttle axis slowly into the sync capture range, as soon as my code activates the sync, the slave axis freezes short of reaching the value of the master axis and becomes unresponsive to further axis movements. Once I figured out what it was doing, I just coded the master axis to "wiggle" (briefly make a small temporary change and return it to its original value) after the sync is activated, forcing all the axes to line up with the master. But it was something of a surprise to have sync active but the throttles remaining out of alignment until the master axis was moved. It's not worth a lot of work...just thought initializing the axes to a synced state at activation would be simple. It's easy enough to code around if you understand how it works. Cheers Bob
  5. Pete; One other thing I've noticed when tinkering with axis sync, is that if it is engaged with the synchronized axes out of sync, they remain that way until the "master" axis value is changed, at which time all the axes are written out the same as the master axis. Not critical for me, but I'd recommend that the slave axes be actively set one time as part of the sync activation so that the axes are properly initialized into a synchronized state prior to master axis movement. Cheers Bob Scott
  6. FSUIPC 4.963f P3D Problem back

    Pete; 4.963f crashes on startup in P3D 3.4.22 on Win 10. Logs and ini file attached. Cheers Bob FSUIPC 4.963f crash logs.zip
  7. Yep, Win 10, version 1607 (Anniversary Ed). The Official Operating System of Purgatory. If you still want error log info, I know I had some detail there, but that machine is shut down and I'm headed up to inspect my pillow now. Cheers Bob
  8. Pete--I don't see a link to 4.963d anywhere in that thread. Bob
  9. Hi Pete--no go with 4.963c--P3D (3.4.22.19868) crashes on startup consistently with the test version. Never gets to the Scenario Setup page. Reverted to 4.963 and it starts up again normally. Last line in the FSUIPC log when it crashes is FS UNC Path = "\\HUD\P3Dv3" in a normal run the joystick scan would come next. Regards Bob
  10. 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
  11. 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
  12. Pete...the link says "q" but the file it points to is "p"--is that a problem? Regards Bob
  13. 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
  14. 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
×