Adamski

Thanks, John (and hi!!) ... you're quite correct, as ever. It turns out I was forgetting to pass the axis through FSUIPC (I'd been fiddling with Axis & Ohs) .... mega DUH!!! I wrote the scripts almost exactly two years ago ... I'm amazed they still work, LOL! I'm amending it so it can work across the board (without checking for autopilot engage y/n) - mainly for the aircraft that use detents (FBW A320 or Fenix A320) where it's easy for the throttle to creep out of the slot. I think a more effective solution would be to do a hardware mod on the throttle (clear the jelly/gloop). Unbelievable how Saitek/Logitech produce this expensive cr*p! Thanks again, Adam.

A thousand apologies if this has already been covered (I couldn't find it). It's been a *long* time since I did any LUA programming - and my grey cells aren't what they used to be!! I suffer from the dreaded Logitech X-56 "throttle creep" and used to use a LUA script I wrote to disable all throttle inputs when in autopilot, using the offset 310A. The scripts (on/off) appear to work (and write a value to that offset) but the throttle remains active. Does MSFS use a different offset? If so, how can I find out what it is? I've Googled without success, but think I should be able to track/trace it when flying ... but how? TIA! Adam.

Thanks, John! I created a new topic in User Contributions: As to the window sizing, I opted to use a FIXED window as it's less obtrusive - and added instructions on how to resize/move it in the readme 🙂 Thanks again! Adam.

https://www.nzfsim.org/?smd_process_download=1&download_id=3241 I have an X-56 stick/throttle combo and often find that when panning around in external view (taking screenshots) I can't help moving the stick slightly - disturbing (or even de-activating) the autopilot. Also - my X-56 suffers from [the dreaded] "throttle creep", which is particularly bothersome with the FBW A32NX when it drifts out of one of the detents. These scripts are an attempt to lock/disable all flight controls (including throttle) when the autopilot is active. 1) AP_Freeze_ON ======================= Checks to see which A/P is enabled (GEN or FBW). If either is enabled, all controls axes are disabled (Offset 0x310A set to 255). 2) AP_Freeze_OFF ======================= Resets/enables all controls axes (Offset 0x310A set to 0). The scripts are mapped to separate switches on the throttle base, using the FSUIPC "Button & Switch Assignments": BUTTON 1 (toggles freeze to ON): Control sent when button pressed: Lua AP Freeze On Control sent when button released: Lua Kill AP Freeze OFF BUTTON 2 (toggles freeze to OFF): Control sent when button pressed: Lua AP Freeze OFF Control sent when button released: Lua Kill AP Freeze On IMPORTANT: For FSUIPC to be able to read the status of the FBW autopilot, the following two lines need to be added - either to fsuipc.ini or (if using profiles) to your FBW profile. Make backups of the original files! [LvarOffsets] 1=A32NX_AUTOPILOT_1_ACTIVE=UB0x66C0 After the first run, the size/position of the windows can be changed in the [ExtWindow] entry (x,y,size x,size y). [ExtWindow] Fixed Window Freeze ON=[30,30,130,56] Fixed Window Freeze OFF=[30,100,130,56] DISCLAIMER This is my first ever foray into LUA programming (!), so these scripts may be far from perfect - please use at your own risk! CREDITS 1) John Dowson for his patience. 2) Jason Fayre (the original author of the MyDisplay.lua script that was a starting point for mine. 3) Pete Dowson for the original FSUIPC. I can't imagine running any sim without it. ======================================================================= Adamski_NZ www.nzfsim.org

Thanks, John - much appreciated!!

Firstly - thanks, John, for fixing the LVARS scroll problem!!! Now ... I'm thinking of allowing people to download my script(s) but I'm wondering if I could prevail on anyone here to run through what I've done to see if there are any "gotchas" <?>. The archive is (temporarily) at: https://www.nzfsim.org/?smd_process_download=1&download_id=3241 Here's a copy of the README that goes with it (should I just paste the Lua files here as well?): Autopilot Freeze - FSUIPC LUA Scripts ==================================================== I have an X-56 stick/throttle combo and often find that when panning around in external view (taking screenshots) I can't help moving the stick slightly - disturbing (or even de-activating) the autopilot. Also - my X-56 suffers from [the dreaded] "throttle creep", which is particularly bothersome with the FBW A32NX when it drifts out of one of the detents. These scripts are an attempt to lock/disable all flight controls (including throttle) when the autopilot is active. 1) AP_Freeze_ON ======================= Checks to see which A/P is enabled (GEN or FBW). If either is enabled, all controls axes are disabled (Offset 0x310A set to 255). 2) AP_Freeze_OFF ======================= Resets/enables all controls axes (Offset 0x310A set to 0). The scripts are mapped to separate switches on the throttle base, using the FSUIPC "Button & Switch Assignments": BUTTON 1 (toggles freeze to ON): Control sent when button pressed: Lua AP Freeze On Control sent when button released: Lua Kill AP Freeze OFF BUTTON 2 (toggles freeze to OFF): Control sent when button pressed: Lua AP Freeze OFF Control sent when button released: Lua Kill AP Freeze On IMPORTANT: ============= For FSUIPC to be able to read the status of the FBW autopilot, the following two lines need to be added - either to fsuipc.ini or (if using profiles) to your FBW profile. Make backups of the original files! [LvarOffsets] 1=A32NX_AUTOPILOT_1_ACTIVE=UB0x66C0 DISCLAIMER ============= This is my first ever foray into LUA programming (!), so these scripts may be far from perfect - please use at your own risk! CREDITS ============= 1) John Dowson for his patience. 2) Jason Fayre (the original author of the MyDisplay.lua script that was a starting point for mine. 3) Pete Dowson for the original FSUIPC. I can't imagine running any sim without it. ======================================================================= Adamski_NZ www.nzfsim.org 19 April 2022

Thanks again, John. Luckily, the next time I ran it, the LVAR in question was near the top - and updating nicely. Still having fun getting the script to work though LOL! UPDATE: Good News!!! I have the script working! I added the LVAR to the .ini file and pointed it to a user offset. Yippee!

The aircraft was loaded and ready. It turns out a PC/MSFS reboot got that going 🙂 *However* I now have another problem. When I list the LVARS (in WASM - now working, thank you!) ... I get a long list - but can't scroll it in any way, so can't get to see the actual LVARS I need (!!). I tried resizing the window etc. but to no avail. This was Win10x64 + all latest .net (as far as I know). In the meantime, I'll try the .ini method!

Thanks, John! I found those two Lvars earlier, but after a fair bit of Googling and reading, I couldn't find a way of reading the Lvar value. Bear in mind that this is my first foray into LUA programming and (at this stage) understanding the docs is a bit of a struggle!!! I've used FSUIPC for donkeys' years but have never need to "look under the hood" before! The functionality is mind boggling! I tried enabling WASM but all the options were greyed out - and my test script still couldn't serve up a value. I'm obviously missing a few steps, so will re-visit those [advanced] docs!!!

OK - so far so good! With the FBW A32NX and X56 Throttle, I get an annoying "throttle creep" that often takes me out of the detent (regardless of how I set the friction). I thought this newly created "freeze controls" LUA would cure that - but the offset for the FBW A/P must be something else. Does anyone happen to know what it might be? I'll ask in the FBW channels as well.

Fantastic!!! I just set 0x310A to 255 when the autopilot (0x07BC) is set. This effectively disables the lot 🙂 Now I can pan around and customise my views for screenshots without upsetting things! Thanks again!

Many thanks, John - I'll let you know how I get on!

Is there a way (in MSFS/FSUIPC) to disable all flight controls input when the autopilot is engaged? I spend a lot of time screenshotting (in external views) and often move the controller when panning/zooming. I know there's an option to disconnect the elevator TRIM axis for A/P mode - and wondered it could be possible to add similar options for the primary controls.

I've upgraded my setup to an X56 (which FCR picks up with no problems) ... so (sadly) I can no longer test FCR with the X52. Hopefully, some other X52 user(s) may be able to help debugging!

You're a star - many thanks!! BTW - I use FSUIPC (paid) ... and tried running without it (in case it was getting in the way) but same problem.