jordanal

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.

Pete, I'm not sure I understand the above, but with ASN on my Wideclient PC and 4.925 on my FSX PC and running the NGX, I was for the very first time experiencing very, very severe pauses (up to 3 minutes each) with or without ASN actually running on the Wideclient (killing ASN on the client did not stop the pauses). I then re-installed the full version 4.924a and everything is running as expected. Do I understand that we're waiting for an updated version of ASN to work with 4.925 on my particular setup?

Nope - that's what I thought too after re-reading the advanced user guide. I tried to associate the LUA plugin with only other specific profiles, including the NGX. But it was still causing problems with my 777 throttles, even though it wasn't in my 777 profile. It wasn't until I removed ALL references to the LAU file in my ini, then I had no further problems with my T7 throttles. It was as if the LUA file was still being referenced at FS session startup, even though it was not used in the active (T7) profile.

For anyone following/using this ThrottleManger object thread and the new PMDG 777, I found that if this Lua object was ANYWHERE in my fsuipc.ini file, it was causing a conflict with my PMDG 777 throttles (always snapping-back to idle after slightest movement of the physical levers). I had used this Lua module with all my FSX aircraft profiles, including the PMDG NGX. You can read my revelation posted over on the AVSIM PMDG 777 support forum here: http://forum.avsim.net/topic/420572-my-t7-fsuipc-throttle-fix-not-what-i-expected/#entry2793365

I had been using the Lua 'ThrottleManager' object with all my aircraft, including the NGX, to reverse my throttle levers after pulling them down to the switch at the bottom of the axis travel. Once the lever-switch activated the Lua module, these same physical throttle levers become thrust reverser levers. As I pushed them up (away from me), they proportionately increased the amount of reverse thrust until I pull the physical levers back down to the idle-detent, which then deactivates the Lua Throttle Manger object, and returns the lever logic to forward (normal) thrust. It was a really neat module and it felt much more like activating and controlling reverse thrust. Unfortunately I discovered yesterday, this exact same Lua ThrottleManager object, when declared ANYWHERE in my fsuipc.ini file, was causing a major conflict with the new PMDG 777 throttles (always snapping-back to idle). You can see my research I posted over the PMDG 777 forum where I discuss this further. So for now, I'm back to the older button-method of repeating "Throttle_DECR" commands as long as the button at the bottom of the levers is activated. Here is an example from one of my 'Buttons' sections. 20=; ******** THRTL LEVERS ********** 21=RY,20,C65966,0 ; THROTTLE1_DECR 22=UY,20,C65967,0 ; THROTTLE1_CUT 23=RY,21,C65971,0 ; THROTTLE2_DECR 24=UY,21,C65972,0 ; THROTTLE2_CUT I will surely miss my Lua ThrottleManager functionality. :(

Hi Pete, I'm having much trouble with my FSUIPC axis and calibrations along with the PMDG T7 and my Saitek Cessna yoke/throttle setup as well. I have many advanced planes and profiles in my FSUIPC.ini files over the years, including the PMDG NGX. All these have axis, buttons, and calibrations assigned in FSUIPC and the 'enable controllers' box unchecked in the FSX controller menu. I am very comfortable manually editing the fsuipc.ini file over the years but I've never had more difficulty with an axis in FSUIPC, as I have with the PMDG T7 and throttles. I firmly believe the high-level calibration conflicts between PMDG and FSUIPC are occurring as you surmise, and 'sending direct to fsx' with no fsuipc calibration should be an easy solution. [update a bit later] - I have discovered the 'Lua AutoThrottle Manager' module used to reverse the throttle axis travel with a reversers button, which activated at the bottom of the physical throttle axis lever travel, is causing the conflict with PMDG T7 throttles (snapping back to idle). When I disabled this Lua module (my only Lua module) in the 'LuaFiles' and 'Auto' sections of the ini file, all Saitek Cessna Yoke/TX axis work with the T7 when setup as 'Send to FS as Normal Axis' and no calibration section in my T7 ini profile. Oh, and thanks for the 'reversing an axis without calibration' ( ,*-1) - I never knew that one. :)

Thanks for the advice - I'll give it shot.

Hi Pete, If I can be so bold, can I request I slight variation of the current Traffic Density Set/Toggle feature/assignements? If I recall correctly, the current incarnation toggles the amount of traffic between zero percent and a predifiend level, or 100% if undefined. I'd like to request an additional varition to toggle the amount of traffic between my current AI traffic level before toggled, and the amount (percentage) specified in the value box. So in my scenario; I routinely fly with 100% AI commercial and GA traffic in FSX(sp2). As I begin my descent into a very graphic-intensive airport like FSDT's KLAX using the PMDG NGX, I'd like to push a button or key, and have my AI traffic drop from the current value (usually 100%) down to say 50% as I defined in the option box for the command. When I push the button/key assigment again, the traffic would go back to the previously set value before toggled, usually 100% in my case. I guess this request could be considered a variation of both the the Traffic_Density_Set and Traffic_Density_Toggle commands, combined. In other words, current percentage Value <toggle> defined percentage value <toggle> back to current percenatge value. Thanks in advance for considering. :cool: