jordanal

Ah, good to know John, I was not aware there is a little delay. Glad I could help and thanks again for all you do. Regards,

Hi John, please find the requested log files (sanitized), along with my .ini file, attached. FSUIPC7 PMDG 777 MSFS2020.log FSUIPC7 PMDG 777 MSFS2024.log FSUIPC7.ini

Thank you for this... The above "Pause" control (c1152) idea was a perfect solution to operate multiple switches in the PMDG 737's and 777's in both MSFS2020 & 2024. I was experiencing the same symptom where only the last sequential switch in a group would operate. Adding the pause control allows all sequential switches to work as expected. Regards,

Yes, I still use both MSFS2020 & 2024. The 2020 777-200er name still begins with "PMDG 777".

I think I've got this sorted now. The log shows all aircraft as "777-200er GE"/PW/RR. So, for MSFS2020 I have the PMDG B777 profile detecting "PMDG 777" and for MSFS2024, I have the profile looking for "777-200er". Seems to work... [Profile. PMDG 777] 1=PMDG 777 2=777-200er

I "think" this may have become a problem with the brand new PMDG B772er native aircraft released this week for MSFS2024. My standard "Profile.PMDG 777" profile in the FSUIPC.ini file is no longer working. My FSUIPC PMDG profiles have always worked in MSFS2020/P3D/FSX without issue and continue to do so. According to PMDG, the standard aircraft.cfg native to their livery folders is no longer documented in the latest MSFS2024 SDK and they chose to negate the file and thus the aircraft title. How will the FSUIPC profile feature work now with fully compliant MSFS2024 aircraft? There is a new ongoing discussion regarding this in the PMDG forums, here: TITLE is the same for all RR, PW, and GE liveries - PMDG Simulations Thank you,

Hi John et al, I've been using FSUIPC7 to map PMDG B737 buttons to my Honeycomb hardware for the past few years and it continues to work great. Now that the PMDG B773 for MSFS has been released, I'm wondering if I'll be able to map its buttons using FSUIPC7 as well in the future? Thanks for any info you can share, - Al

Has anyone got this working with FSUIPC5 betas and P3Dv4 (x64)?

Of course Prepar3D v3 came out - Pete went on vacation; this is the third time in a row! LM even commented on Pete assisting the v3 development process; wonder why he didn't post a compatible version before his Holiday?

Thank you so much, Pete. I wish I could confirm the fix for you immediately, but unfortunately I've already packed all my flighsim gear. It's going to be a long month without my rig for the first time in 17 years.

As always, you're a scholar and a gentleman! :razz:

Good morning, Pete. You were correct, using v4.939g when I uncheck the 'exclude ThrottleN set' checkbox in the Throttle axis calibration page, the throttles become unresponsive, just like v4.939j and later. without restarting the FSX session, I can immediately re-check the same option and the throttles work again. In case in matters, you should be aware that I only use FSUIPC for button/key/axis assignments (send to FS as normal axis) and I do not use any of the FSUIPC calibration facilities, which seems to work best with my PMDG aircraft. FYI, I will only have access to my Flightsim-rig for a few more days (probably Wednesday) before tearing everything down to begin the process of moving my home to Florida - I don't anticipate having it running again until late May. I only mention this because there's no hurry for a permanent solution on my part, and I won't be able to assist in further troubleshooting during this time.

Hi Pete, My, you're up awfully late today... My 'exclude ThrottleN set' checkboxes for throttle, were already checked. Continued testing with v4.939j, unchecking it does not appear to have any affect. I have sent a personal e-mail to 'PilotJohn' asking if he can contribute to this discussion. His e-mail address was found at the top of the ThrottleManager script.

Pete, I've discovered that if I roll-back FSUIPC to version 4.939g without modifying my FSUIPC.ini file, this Lua ThrottleManager (v1.1.3) works as it always had. When I re-install FSUIPC version 4.939j_updated, all throttle axis become inoperable as long as this ThrottleManager script is listed in the ini AUTO section. What could have changed between these two versions of FSUIPC that broke this Lua script starting with version 4.939j_updated? ThrottleManager version 1.1.3 can be found on page two of this thread here: http://forum.simflight.com/topic/69388-throttle-manager-to-allow-axis-forwardreverse-toggle/page-2#entry436660 Thanks,

Is there any chance the latest FSUIPC 4.939k update broke something in this LUA Throttle Manager utility, or how it interacts with the throttle axis assignments? This ThrottleManager.lua has been working fine for years, until very recently. Now, all my axis work normally except any throttle axis assigments on any FSX aircraft, including the default. The throttle axis raw values are still changing in the FSUIPC Axis Assigments GUI. Now, I just discovered that if I disable (comment-out) the "1=Lua ThrottleManger" entry in the Auto section of the my FSUIPC.ini file, all throttle axis work normally again. I wonder if the following 'change note' from the FSUIPC update PDF, might have had something to do with this new issue. "-- Fixed a long-standing problem with some older FS98 style control assignments." Thanks for any help.