hvw

Good morning John, Unfortunately this, too, didn't work. It was worth giving it a shot, thanks a lot for all your help. Hans

Thanks a lot, John. I will give that a go tomorrow and report back to you, OK?

Thanks @Cuantreau but unfortunately this didn't work for me, either. I will wave the white flag and use buttons instead 🙂 Thanks a lot anyhow for trying to help out.

Yes, they both work (F1 and F2) and yes I could set them to the buttons of my joystick, but I just wanted to use my joystick's throttle to handle the 737's thrust (throttle in the middle=idle, throttle all the way forward=full thrust, throttle all the way back=full reverse). I guess I have to make do with thrust controlled by buttons 🙂 Thanks, John Later: Holding F2 depressed gives full reverse, F1 cuts the engine, so I can fly around with the PMDG 737s.

The "weird" thing is that "my" way of assignment/calibration does work great for MSFS' stock 747 and A320, but it really is a royal PITA in PMDG's 737-700. So I decided to live with the fact that when I use the PMDG 737 I will have to use the F2 key to get the reversers to work. Can you let me know what your throttle setup is in MSFS' control options for the joystick? I perhaps may have overlooked something. Thanks.

Let's just wait and see what happens then. I kept on trying to assign the throttle in the same way as I did under P3D/FSX as it worked perfectly there with the help of FSUIPC of course, till I found out this to be impossible in MSFS' 737. I now will use my joystick's throttle in such a way that I only can use thrust idle and up to max thrust forward. The reversers I will activate through the F2 key. When I will be using the 737 that is, I still do prefer the FBW A320Neo 🙂 . Thanks, John

I logged the events and axis. Only Throttle_Inc, Throttle_cut and Throttle_decr are being used via the cockpitUI. Reading the PMDG forum, there are a lot of folks having problems with their joysticks (different brands) to get reverse thrust (and forward thrust) to work correctly.

No, it is not strange 🙂 It was Pete who told me to do so lots of years ago. Yes, the issue is that I with this MSFS2020 version of PMDG 737 cannot use the throttle on my joystick at all. No problem, I will stick to the FBW A320Neo then. Thanks John PS: You may want to have a look at pages 31 and following of the FSUIPC User Manual. It is described there what I did to try and get my throttles to work

Hi John, I assigned the throttle in both MSFS and FSUIPC. I assigned (in FSUIPC) Throttle 1 set and Throttle 2 set and then I calibrated the throttles in option 3 of the calibration tab. (I did it the same way in P3D to avoid having to use buttons for reverse thrust). Calibrating in this option 3 of the calibration tab I selected the max input for full forward thrust, 0 for idle thrust and minimum input for reverse thrust. (See attached files). This worked perfectly in P3D.

Later: Got it working, I thought. I accidentally (??) did assign each engine to a throttle axis in MSFS2020, where I should have select Throttle Axis (with reverser) only in the control options of FS2020.Thought it worked, the throttles moved into the correct positions, but alas, this didn't activate the reversers in the plane itself.

Hi all, Hopefully someone can help me with my reverse thrust problem I have got in PMDG's 737-700. I have got a Thrustmaster T-flight Hotas X joystick and I am attempting to assign the throttle via FSUIPC. Just as I did a couple of years ago with PMDG's 737 for P3D. I did assign the joysticks throttle to Throttle 1 Set and Throttle 2 Set and calibrated this in option 3 of 11: Separate throttles per engine. I unchecked the "Exclude THROTTLEn_SET" checkbox just as I did way back in P3D for this aircraft. Now, however, in MSFS2020 this doesn't work for me. No reverse thrust at all and throttles are running full at the stick's idle position. I hope that I can find some help here. What did I overlook? Or what else should I do to get my joystick to work as desired? Thanks very much for any help, Hans van Wijhe

Hi John, The issue has been resolved. It appears that the experimental version of the A320Neo mod (CFBW) needs a throttle configuration .ini of its own. It can be generated as is stated in this here document: https://github.com/flybywiresim/a32nx/tree/fbw/docs Thanks, Hans

I reported it to them. Will keep you updated on their reply, OK?

In MSFS2020 I solely use FBW's A320Neo. With their stable and latest dev mods my Thrustmaster T-Flight Hotas X works perfectly when I select and calibrate thrust reversers with FSUIPC7. (Assigned as Throttle 1 Set and Throttle 2 Set and calibrated in "3 of 11: Separate throttles per engine"). However, when I use FBW's CFBW (the experimental version of their A320Neo) I cannot get thrust reversers to work with my T-Flight Hotas X assigned and calibrated as stated above. Hopefully there is a workaround for this, unfortunately I didn't find it. Any hints/solution will be greatly appreciated. Thanks, Hans

Thanks a lot for your assistance, John. Have a nice weekend, take care and stay safe, Hans

Hi Pete and John, Since I first started to use the RUNIF options, a long, long time ago, I always have been using these options without quotes. Strangely enough this always worked for me until fsuipc v7.0.4 🙂 . (They still work quotes less in Prepar3d, weird uh?) So what I now did (again) was, just to give it another go, ran the fsuipc7.0.4 installer, which of course uninstalled the previous installed version, and after completion of this new installation made sure that these quotes were in the right places in the RUNIFx lines in the .ini file, added the READY parameter as well and then ran the msfs.bat file. (After of course inserting the correct path in this .bat file to the fsuipc directory). Much to my surprise everything worked perfectly now. If you want to I can send you the uninstallFSUIPC7.log, perhaps you can derive from that file what might have gone wrong previously. Do you also want the FSUIPC7.LOG file? Thanks for your help Hans

Bad luck, John, even with quotes in the right places it doesn't work. Hans

Thanks John. Will put quotes where necessary, but isn't it strange that with previous versions of fsuipc these "runif" lines worked perfectly? The fsuipc.ini wasn't changed in any way when I installed v7.0.4. Have a nice weekend, Hans

Hi John, The issue persists unfortunately. Attached please fined both the .ini and .log files. By the way, I uninstalled the previous version when so required by v7.0.4's installer, sorry for causing some confusion, I should have made that clear. FSUIPC7.ini FSUIPC7.log

Hi John, Today I installed, after uninstalling 7.0.3, fsuipc 7.0,4 and so far this new version seems to overlook the 3 RunIf statements that I have got in my fsuipc.ini file. Do you have any idea what I might have done wrong? (Or does fsuipc no longer support RunIf) Thanks, Hans van Wijhe

Hi John, Your suggestion for Rudder=-25000,-512,512,25000 seems to have done it. Of course I can try and finetune it a bit more, but to be honest, I have had it for today :). I am glad that at least I can do a full throttle take-off from a runway with some crosswind and keep the plane under control while rolling. Thanks a lot for your help, Hans

Thanks, John, I will give it a go. As I didn't run into this anomaly before updating to the mentioned mini-update, of which they (Asobo) said that it was only a navaid update, I will be surprised if indeed it will be this setting in fsuipc. Nevertheless, one never knows and I will try it. Will keep you updated, OK? Thanks, Hans

Hi, I posted the below message in Avsim's MSFS forum and it seems that some other do suffer of this phenomenon as well. I wonder if any of my fellow-FSUIPC users also are being victim to this issue. For your information, I disabled all 3rd-party addons and tried all available aircraft types with the same result, ground steering was not possible. All controls were assigned in FSUIPC. I am just curious to know whether or not this can be a FSUIPC related problem. What I doubt, though). ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Ever since I installed the MSFS December 3, 2020's mini-update ground steering became impossible. The plane is swaying left and right on the slightest joystick rudder movement. This happens on FBW's latest dev mod A320 as well as their stable version. Also plain vanilla MSFS A320Neo has been affected by this. I (re-)calibrated my joystick in FSUIPC 7.0.2 without success, also lowering the sensitivity in MSFS didn't result in a better behavior on the ground nor did adjusting dead zones bring me any luck. To make sure that it was not a hardware problem bothering me, I went back to P3D and did a flawless flight (including ground steering) with PMDG's 737-900. Do any of you have an idea what might have gone wrong and how to get MSFS to do correct ground steering again? It's a pity that we can't uninstall this mini-update 😞 Thanks, Hans

None of the given numbers were in the two sections of the registry. Last night I did find the IDs as described in Pete's message (fpr a Sitek and deleted them), followed the further procedures in that message, but still to no avail. Indeed it is a problem with all aircraft in both sims, I guess I have to dive deep in my treasure chest and buy a new joystick. Hopefully, in this case, it indeed is a hardware issue and that I don't run into the same issue with the new stick. As a last attempt I will uninstall the Thrustmaster driver(s) and see if that helps any.

See attached screenshot of the in/out boxes. I also found that in P3D the throttle is not working as expected either. (It did early this morning hence I said it was working correctly). You are right, it seems that the full range is not being sent to the simulator. Moving the throttle on the joystick only a tad forward results in a full throttle in the simulators (P3D and FS2020). I followed the instructions given in the "fixes problems with 50% etc" article, but no cigar. I ran HidScanner to find the PID number for my Thrustmaster, but can't figure out what the correct number is. Can you help me out again, please? This is the header given by HidScanner for the joystick Device at "\\?\hid#vid_044f&pid_b108#6&35a65181&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" Vendor=044F, Product=B108 (Version 1.0) Manufacturer= Thrustmaster Product= T.Flight Hotas X Serial Number= T.Flight Hotas X Looks as if I am being seriously grounded 🙂 Hans Just wondering. Isn't it strange that in both P3D and FS2020 all axis but the throttle ones are working perfectly? In Windows' Game Controller the throttle is indicating that it works 100% correctly