Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Content Count

    35,207
  • Joined

  • Last visited

  • Days Won

    113

Pete Dowson last won the day on December 12 2018

Pete Dowson had the most liked content!

Community Reputation

210 Excellent

About Pete Dowson

  • Rank
    Advanced Member
  • Birthday 08/27/1943

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Near Stoke-on-Trent, UK
  • Interests
    Flight Simming, Steam Railways, Travelling, Real / Craft Ale,, worldwide

Recent Profile Visitors

29,619 profile views
  1. I don't kow about that, but it seems a bit odd. Maybe it goes dormant? Is it connected to a proper power supply? Ah, that would explian it! Pete
  2. So, the problem is in the assignment of the buttons to an FSUIPC Offset control? You need to show me what you've done there -- perhaps describe it and show me the FSUIPC INI file? Log button/key presses too in FSUIPC and show me the log after you press buttons. Pete
  3. Pete Dowson

    FSUIPC offset lenght

    No, you cannot change a defined offset length. The value documented is the value supplied by the simulator. How will changing the length affect that? The TAT value is degrees Celsius x 256, and, in the two bytes provided, that gives a range of -128.0000 C to +127.9961 C. Why do you need a larger range? Surely that range is easily sufficient? I've no idea what you are talking about regarding "4 needle movements". Sorry. By the way, you posted your question in a reference subforum. Please ALAYS post support questions here, the Support Forum. Else it will not get attention. I've moved it for you. Pete
  4. That's the same for all axis controls, not just trim. I expect the controls you are using to adjust the trims are INC/DEC controls, so the axis input doesn't change -- both FSUIPC and P3D only note changes in axis values. Yes, tha's the usual way around it, whether by two assignments to the press, a macro, or one on the "press" and the other on the "release". Pete
  5. Well, we don't have the logging we requested yet anyway! Whether it is FSX or another add-on causing problems (e.g. with close down) or not I can't tell from here. You could show me your EXE.XML and DLL.XML (from from your AppData folder where your FSX.CFG is also kept). I can see whether there are any add-ons you should idable as a test. Failing that, yes, an uninstall and re-install of FSX might be appropriate. Of course, you may be grabbing the FSUIPC4.LOG file too soon after the FSX window disappears. The underlying FSX base is still running for many seconds after that.
  6. There's something seriously wrong, then, as that is effectively exactly the same as assigning in FS. No, you haven't. You added "Debug=Please" cotrrectly, but not the "LogExtras=x1008" ! The log is therefore no different to before, no new information, and still too long. Over 10 minutes is a lot longer than you need just to operate each flight control axis once. Also, if that is where your Log actually finishes, then it seems FS is hanging on close -- FSUIPC should complete the log properly with many more lines and a final obvious close. I think you have something wrong in FS. Pete
  7. There may well be L:Vars for what you want. I don't know. Did you check? You can list all the L:Vars using an assignable FSUIPC control or monitor them with one of the Lua examples provided. Pete
  8. In what way? Ouch! You are still using one of the first versions of FSUIPC5 and P3D 4.0. Why have you never updated? Sorry. The currently supported version of FSUIPC is 5.15 or later, and you need to be on P3D4.1 or later -- current is 4.4. LVars are totally unrelated. Why confusing? Pete
  9. Pete Dowson

    Magvar and MakeRwys

    Okay. Thanks for the quick test. Pete
  10. Pete Dowson

    Magvar and MakeRwys

    Could you check the values iwith this one, please. I think I covered all angles. MakeRwys4871.zip Then I'll release it. Pete
  11. Pete Dowson

    Magvar and MakeRwys

    Checked. Yes, you are correct. I merely fixed the MagVar entries. The follow through isn't so easy -- I should have had those in True as per spurce dayta. I'll see what I can do. Pete
  12. Pete Dowson

    Magvar and MakeRwys

    Ah, are those in Magnetic? They are in True in the sources of course. I'll check ... Does that affect all files, do you know? Pete
  13. Are any of the offsets fulfilled? Did you enable them in the PMDG SDK as described at the beginning of the offsets document( the "PLEASE READ THIS FIRST" section)? BTW there are also parameters in the FSUIPC INI file to switch the action on and off, but they default to "Auto". Check for "PMDG737offsets". you can set it to "Yes", "Auto" or "No". The Auto mode depends on detecting the PMDG aircraft by its original name. I cannot really support PMDG aircraft. I don't even have any installed. The offsets are mapped directly from the data supplied by the code in the PMDG software, so if they don't work even when enabled you may want to ask in their forums. Pete
  14. Pete Dowson

    Throttle axis calibration

    So what are the "small corrections" for. surely for takeoff you apply max power, or pretty much so. What are you "correcting" for? I don't have access there, and the title talks about "landing". Surely the corrections are to rudder or tiller, not to throttle, which would be at idle on touchdown, or close to. Or do you mean asymmetric thrust? It is quite normal on real aircraft for the same thrust on each engine to requre slightly different positions of the throttle levers -- they are rarely in perfect alignment. But if you wish you can either make one throttle control both, using an FSUIPC hotkey, or sync positions in the calibration tab using the sync option. Pete
  15. Offsets are hexadecimal numbers (hence the 'B' in 64B2). You needs to express it as 0x64B2, or convert it to decimal (= 25778). Pete
×

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.