Adamski

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.

First post, so a BIG hello to Fabio and all here! I have a problem trying to assign device shortcuts. My X52 Pro isn't being recognised though (strangely!) my rudders are. Is there a fix for this - or any way I could add it manually in the .xml file? This is with the latest version (downloaded today): FM-FlightControlReplayv4.5.2201.12CameraManagerUpdate. Win10x64. Recording/replay looking good so far (congratulations) but having problems saving video files (I'll start a new topic for that). Adam..

Worked great on my system too! Many thanks :-)

Thanks, Pete - welcome back!!! I hope you had a good break - straight back in the saddle, I see! Looking forward to 5.123d! Adam.

For me, 5.123a or even 5.123b worked as well as 5.122.

There's our problem, then LOL!!! I'd still be keen to hear if anyone else out there shares my problem. I can't be the only one, Shirley? Adam.

Thanks, Pete. Out of interest (it's all news to me): https://support.microsoft.com/en-gb/help/305097/how-to-view-the-system-registry-by-using-64-bit-versions-of-windows Maybe there's some mixup in the installer between the two versions of the HKLM keys (64/32-bit)? It does seem a coincidence that it's the HKLM path that's going weird. Adam.

OK ... here's the batch file code (you can try it on your system too): @echo off echo. REM echo Checking Prepar3d V4 location. reg query "HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3d v4" /v AppPath >nul 2>nul for /f "tokens=2*" %%a in ('REG QUERY "HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3d v4" /v AppPath') DO SET "P3Dv4_Path_HKCU=%%b" echo ------------------ echo HKCU: %P3Dv4_Path_HKCU% echo ------------------ reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4" /v SetupPath >nul 2>nul for /f "tokens=2*" %%a in ('REG QUERY "HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4" /v SetupPath') DO SET "P3Dv4_Path_HKLM=%%b" echo HKLM: %P3Dv4_Path_HKLM% echo ------------------ pause When run, I get two identical paths: H:\Program Files\Lockheed Martin\Prepar3D v4\ H:\Program Files\Lockheed Martin\Prepar3D v4\ So far so good ... BUT ... I ran "Regalyzer" which, unusually, appears to break down the keys in HKLM into 64-bit and 32-bit sections. The 64-bit section seems to be the active one (with my latest SDK entry etc. in there) but I have similar keys in the 32-bit section (but missing paths for Add-on Scenery and the SDK). Weird. The other oddity is that the 32-bit key uses "setuppath" whilst the 64-bit key uses "SetupPath". Can case be important? Both *values* of the key are the same (path), however. I edited the batch file for both spellings and both returned the correct path. I have to say I'm *way* out of my depth here, so you might be on your own! Adam.

Yay!!! See my comments after the log (P3D fires up OK and FSUIPC reports 5.103g): ===================================================== Installer for FSUIPC5.DLL version 5.103g Looking in registry for Prepar3D v4 install path: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v4! <<< ... AppPath=H:\Program Files\Lockheed Martin\Prepar3D v4\ =========================================================== INSTALLATION FOR Prepar3D v4: AppPath="H:\Program Files\Lockheed Martin\Prepar3D v4\" Checking version of the Prepar3D v4 EXE: ... Version 4.0.28.21686 (Need at least 4.0.20.21316) Checking if there's already a version of FSUIPC5 installed in: H:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL ... Version 5.102 found. Prepar3D v4 Modules folder already exists. Okay -- installed FSUIPC5 into "H:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Adam\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Adam\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Adam\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC5 section. ... FSUIPC5 section already exists but will be replaced. ... FSUIPC5 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Administrator\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC5 User Guide.pdf" okay Installed "FSUIPC5 for Advanced Users.pdf" okay Installed "The 2016 List of FSX and P3D Controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC5 History.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC CHECK Checking FSUIPC registration ... Registration check for FSUIPC5 was successful! (result code 00) *************** End of Install Log *************** ===================================================== Comments: 1) Regardless of *why* the registry lookup fails the first time, it seems to me that the [old] installer bombs out at that point, rather than skipping gracefully to the next look-up. 2) As to the "AppPath" in HKCU, I'm as mystified as you. I use a little home-grown batch file for adding aircraft add-ons (outside of P3D root) and it has a bit of code that queries exactly that entry. Here's the snippet: ------------------------------------- @echo off REM echo Checking Prepar3d V4 location. reg query "HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3d v4" /v AppPath >nul 2>nul if %ERRORLEVEL%==1 goto not_found for /f "tokens=2*" %%a in ('REG QUERY "HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3d v4" /v AppPath') DO SET "P3Dv4_Path=%%b" echo %P3Dv4_Path% pause ------------------------------------- When I run that, I get the correct/full path, but without the trailing triple periods that you see when you lookup the entry in regedit. I'll see what it looks like in another registry editor - see if those periods are just a display oddity. Is it possible that Windows security is somehow protecting HKCU? Wild guess ... clutching at straws. I'm also wondering why it appears to be just me with this problem (story of my life!). Anyway - I'm delighted that we're on the right track - though I really don't have a clue what's going on LOL! Adam. EDIT: Pete: ignore the three periods "thing". It's a red-herring - and appears to be just a weird Win7 Regedit display anomaly. The actual *value* doesn't have them. I checked the keys in two other registry editors and neither of them showed the damn' periods.

Thanks, Pete. I've just rung a buddy (with P3Dv4). He has exactly the same as me: \... on the end of the HKCU entry (not on HKLM).. I'll remove the redundant P3Dv3 and P3Dv2 entries then run a registry defrag. Then I'll have another go ;) Adam. EDIT: No luck after the registry defrag/cleanup, I'm afraid. Same error, exactly as before. Over to you, Sir!

I must admit it's odd. I've never had it do this to me before ... ever! Sorry - I should have said .... it was from HKLM. In HKEY_CURRENT_USER, I only have "AppPath" - which has the same path as in HKLM (except it has three periods after it: H:\Program Files\Lockheed Martin\Prepar3D v4\...). This appears to correspond to what the installer is expecting (going by my successful 5.102). I appear to have entries in HKCU for P3Dv2 and P3Dv3 (but not in HKLM)... should I remove them? Adam. EDIT: Wait a minute. If you check my (successful) 5102 log, it says it couldn't find the path in HKLM (SetupPath) but then successfully finds it in HKCU (AppPath). Yet my HKLM entry *is* there. Is this a clue? That the 5103 installer is misreading the first entry then (somehow) error-ing on the HKCU search? Yet I now get the error on both 5102 and 5103. Weird!

Pete - thanks for taking this on! Here's the error window. Hard to screengrab, as Windows takes focus on the 2nd error window: The registry entry: The FSUIPC log itself appears to be fine - and updates itself everyu time I run P3D. The install log (also in "Modules") is the old 5.102 one - and doesn't seem to have been updated by the [failed] 5.103 install. Here it is anyway, just in case it's useful. Installer for FSUIPC5.DLL version 5.102 Looking in registry for Prepar3D v4 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v4 Parameter"AppPath" ... >>> OK! FOUND Prepar3D v4! <<< ... AppPath=H:\Program Files\Lockheed Martin\Prepar3D v4\ =========================================================== INSTALLATION FOR Prepar3D v4: SetupPath="H:\Program Files\Lockheed Martin\Prepar3D v4\" Checking version of the Prepar3D v4 EXE: ... Version 4.0.23.21468 (Need at least 4.0.20.21316) Checking if there's already a version of FSUIPC5 installed in: H:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL ... No previous valid version found. Prepar3D v4 Modules folder created okay! Okay -- installed FSUIPC5 into "H:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Adam\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D v4\Prepar3D.CFG for all users, including this one Looking in "C:\Users\Adam\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Adam\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.CFG" Now checking DLL.XML ... ... No previous DLL.XML found, creating new one. Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Administrator\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\DefaultAppPool\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC5 User Guide.pdf" okay Installed "FSUIPC5 for Advanced Users.pdf" okay Installed "The 2016 List of FSX and P3D Controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "FSUIPC4 Offsets Status.pdf" okay Installed "Profiles in Separate Files.pdf" okay Installed "FSUIPC5 History.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "Offset Mapping for PMDG 777X.pdf" okay Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay =========================================================== All installer tasks completed. Registration dialog exit: selected FSUIPC REGISTER Providing FSUIPC registration dialogue ... Registration for FSUIPC5 was successful! (result code 00) *************** End of Install Log *************** Anything else I can do to get more info? Many thanks, Adam. EDIT: Sorry - I forgot to add - I'm using the same Avast as you (free version). Here's the Windows error entry: Faulting application name: Install FSUIPC5.exe, version: 5.1.0.3, time stamp: 0x59515139 Faulting module name: Install FSUIPC5.exe, version: 5.1.0.3, time stamp: 0x59515139 Exception code: 0xc0000005 Fault offset: 0x0000b5c4 Faulting process id: 0x199c Faulting application start time: 0x01d2fd60fdd82c31 Faulting application path: F:\_Archive\P3D_Archive\_PAID\P3Dv4_Utils_PAID\FSUIPC\FSUIPC5103\Install_FSUIPC5103\Install FSUIPC5.exe Faulting module path: F:\_Archive\P3D_Archive\_PAID\P3Dv4_Utils_PAID\FSUIPC\FSUIPC5103\Install_FSUIPC5103\Install FSUIPC5.exe Report Id: 3ba806ae-6954-11e7-a5ad-6c626d3b5dfd

Hi Pete! I'm sorry to say that I've also been struck by some installation weirdness ... after so many years of using FSUIPC with no problems. I tried to install 5.103 and the installer pops up the familiar install window, gets as far as querying the P3Dv4 registry entry, then crashes every time. This is P3Dv4 with Hotfix1. 1) The zip is properly extracted (no errors). 2) Win7x64. I'm logged in as "Admin" - and have also tried "Run as Administrator". 3) Comodo Firewall and Avast A/V temporarily disabled. 4) The install log never gets created. 5) I checked my registry entry for P3Dv4 - the setup path is in there OK. Is the installer faioling because it looks for (and can't find) entries for P3Dv3 and/or FSX? I still have FSX active on my system. 6) FSUIPC 5.102 is working fine in P3Dv4. 7) Installing immediately after a restart/hard reboot doesn't help. OK ... so I tried re-installing my current 5.102 (over the top) ... but now I get the same problem as for 5.103. I suspect that the very latest Microsoft [security] update may have something to do with it - or updates to Avast or Comodo. Maybe a complete uninstall of both (Avast+Comodo) would help, then reinstalling them after the FSUIPC update, but I'd hate to have to do this every time FSUIPC gets an update. Anything else I could try? I have the Windows crash report zipped up - should I PM you that? As ever, thanks for your amazing contribution to the FS world! Adam.