Jump to content
The simFlight Network Forums

generexe

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by generexe

  1. Hi Pete, The joystick is connected to FS2004 via windows (like any game; no software of mine is in between). The problem I meant to state was that even though I used offset 310A to disconnect the joystick from the elevator, I can still make the deflection value change just a tiny little bit by moving the joystick. I tested this in a situation where the elevator deflection was 0 (flying straight ahead). I viewed the elevator deflection offset (2E98) in the FS title bar (via logging in FSUIPC). I was just wondering if you had any idea what the reason could be. Regards, Steven. PS. I will update to the latest version of FSUIPC asap.
  2. Hi Pete, I've just checked them on FS2004 -- the 0BB8 and 0BB4 values simply stick at their last manual value (they don't go to 0), but the deflection values at 2EA8 and 2E98 are working fine, and change correctly exactly as they do in FSX when on A/P control. Please check again. Use the Monitoring facilities (right-hand side of the Logging tab) or FSInterrogate. You must be doing something wrong if you only see zeroes. Don't forget those deflections are in Float64 format. Pete Thank you for the tip. I tried the logging and I think I found the problem. When I fly with a joystick, the joystick will always take priority over the autopilot, when controlling the deflection. So a joystick in neutral position will push the deflection to 0. (However the simulation internally makes the plane climb, if the autopilot altitude requires a climb). When I fly with the keyboard (joystick unplugged) then the autopilot seems to be in total control of the deflection. When I use offset 310A to turn off the joystick axis, then it works better. (I tried this before unsuccesfully, due to a bug in the code I made). What is really strange though, is that even with the joystick disconnected from the elevator-axis, I can still control the deflection (2E98) in a very small range (up to 0.025 deflection value). When I turn off the autopilot (at which time the joystick axis is attached again via offset 310A), the joystick gets total deflection control again. I am using FS9.1 and FSUIPC 3.7 on Windows-XP SP2. I am flying a 737-400. Do you have any suggestions? Are there any other tests I could do to tackle the problem? Thanks a lot for any help you can provide! Regards, Steven.
  3. The aileron and elevator position indicators (0BB8, 0BB4) should help. Or you'd need to use the actual deflection angles, 2EA8 for Aileron, 2E98 for elevator. All these work fine with the autopilot in FSX, and should be okay in FS9, though you'd need to check that. I tried these offsets before. (I am using FS2004). If you fly yourself with the joystick the offsets change/work fine. However after the autopiliot takes over they are no longer updated. (E.g. elevator position indicator and elevator deflection become 0, even though there is a clear pitch while the autopilot makes the plane climb). Do you have any other suggestions? Thanx! Steven.
  4. I am working on building a realistic yoke-setup, which we are interfacing with FS via FSUIPC. When the autopilot is switched on, we want to be able to move our yoke according to the actions of the autopilot. E.g. turn the steering wheel when the autopilot is going to a new heading. I was hoping that "Elevator/Aileron/Rudder position indicators" (offsets, 0BB4, 0BB8 and 0BBC) would reflect the autopilot actions as well, but they don't (The "Elevator/Aileron/Rudder control inputs" in offset 0BB2, 0BB6 and 0BBA, work fine in normal flight-mode, which we use to inject our own yoke-sensor readings into FS). The FSUIPC documentation mentions several autopilot features that have been added into FSUIPC, but I am not sure if there are any control-surface related offsets, which reflect the autopilot actions we need. Do you know of any offsets, that are more suitable to derive yoke-positions from, when running the auto-pilot? Is there perhaps a feature in FSUIPC that takes care of this (which I don't understand yet). We appreciate any help/tips/suggestions you can offer! Kind regards, Steven.
×
×
  • 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.