John Dowson

I have checked this here now and it looks like in both cases (i.e. when using FS Controls and when using presets) what is happening is that both controls are being sent, but the FS is only responding to the first control. I am not sure why this is happening, but really you shouldn't be sending the slow/small inc/.dec control when sending the fast one. To prevent this, add another preset condition in the slow control to be only sent when the trigger button is off, i.e. change: to John

Cam you please attach your FSUIPC7.ini and FSUIPC7.log file, the latter with logging for Events and Buttons & Keys activated and showing your issue, i.e. load an aircraft, activate the flaps Increment and then exit. Also check that the button is not assigned in MSFS2024..

Better to disable controllers in P3D completely, otherwise it has a habit of silently re-assigning them. So please first try with controllers disabled. If you still get the same issue, please activate logging for Axes Controls and show me / attach both your FSUIPC6.ini and FSUIPC6.log files and I will take a look. Note that I have now finished for the holiday season, but I will take a look at your files over the weekend when I find some spare time. Regards, John

I have finished now for the day (and year really!), but will take a look over the weekend when I have some spare time...

Please attach files rather than posting extracts... It is strange that I cannot see a button 2 press event logged, but the condition does change from false to true, and the control is being activated. The fast controls use offset 0x07D4 and set the AUTOPILOT ALTITUDE LOCK VAR simvar. If this is not working, then the aircraft doesn't use that simvar (or uses it in conjunction with something else) . Try assigning to the AS1000 presets instead, i.e. AS1000_AP_ALT_INC_100 AS1000_AP_ALT_INC_1000 AS1000_AP_ALT_DEC_100 AS1000_AP_ALT_DEC_1000

Try/start with the User manual. I provide extensive documentation do I don't have to answer such questions, and there are many on-line resources. And please don't hijack unrelated topics for your question - if there is no appropriate topic, pleas start a new one. John

The standard way to have both slow and fast inc/dec on a rotary is to use fast/slow buttons in each direction. Some rotaries do have two buttons in each direction for this, one for a fast turn and one for a slow turn. For rotaries that only have one button in each direction, you can use a lua script that can turn this one button into two virtual buttons, one for the fast action and one for the slow action. Such a lua script is included in the lua examples zip file (in your FSUIPC Documents folder) called Rotaries.lua. But you should also be able to do this using a button. If this isn't working, try using logging to work out what is happening - activate logging for Buttons & Switches and see what is logged (use Log -> Open Console to see the log in real-time). If you want further help with this, show me / attach your FSUIPC7.ini file, and an FSUIPC7.log file generated with logging for Buttons & Switches activated and showing both the slow and fast assignments. Well, you will still get the regular assignments unless you add another compound condition to these to only send when the activation button is not pressed. But what is probably happening is that you are using a momentary button and not a switch, so when you press it it is instantaneous, so when the rotary assignment is triggered it doesn't recognise the activation button as being pressed. If this is the case, then you should switch to using the button flag instead. See the section on using button flags in compound conditions in the Advanced User guide - here is an extract: John

What about in 7.4.18, the previous version to 7.5.0? There was a change introduced in 7.4.18 that could cause this: So, if using a 3rd party traffic injector, you need to set that ini parameter. This is the documentation for this parameter (from the Advanced User guide: John

Yes, very strange... I will be releasing 7.5.1 later today, and I am going to switch to using version numbers on the downloadable file which should help with this cache issue. Cheers, John

Ok, sorry I cant be of more help. And a Merry Christmas and Happy New Year to you! Regards, John

...and I will be releasing 7.5.1 tomorrow (only minor updates to help users with 3rd-party software using FSUIPC that hasn't been updated for MSFS2024) so maybe try that once released.

I don't understand this, unless you download from here (i.e. these forums) and didn't clear your browser cache, in which case the older cached version was downloaded. The download forums on this server will be removed soon, so you should use fsuipc.com. I will be moving everything to there, and support via Discord, over the next few months... Regards, John

Ok, I have corrected it there. But you only need to download that if not using FSUIPC7. Yes, I updated this after the beta, or maybe in the final beta. It will overwrite, but I think this was changed a day after the initial release, so if you downloaded early it would have had the old value. As I said, I think the initial release still had this set as -15. As this was causing issues, especially in MSFS2024, I decided to make 0 the default, but I didn't release/update the version number for this change. If this fixes the issue, could you post this on the IniBuilds forums so that anyone who has this issue can check that setting. I still don't understand how a WASM crash can cause the a/c to freeze though, very strange.... John

What website? Use fsuipc.com, as the zip file may have been cached if using the download links in this forum. I have checked the zip file again and it is definitely set to 0.

Yes, that is an error and will be corrected in the next release, sorry. The log file shows that the WASM crashed. Try disabling lvar scanning, see the following FAQ entry: Basically you just need to set the WASM ini parameter LvarScanFrequency to 0. In fact. the latest release should have this already set, but may be overridden if you have an FSUIPC_WASM.ini file in your persistent storage area. If you do, remove that or change/update there. I don't see how a WASM crash can freeze the sim though, unless the A300 is using the WASM... John

But you don't have to go back to the main menu to exit the sim - use the FSUIPC7 menu option MSFS->Exit

Then the log file should be here: AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvarmodule\work i.e. under MSFS2020 not MSFS2024. There is an error in the document that I will correct. It will get created, as it is created when MSFS starts the WASM during start-up. However, if you kill the sim it won't exit correctly. No point in doing this.... Of the FSUIPC WASM module is installed, that folder will/must exist. You are just looking in the wrong place... The folder and log file will exist regardless of whether you use the WASM or not, if the WASM is installed.

That is wrong - for Steam installs, its under: AppData\Roaming\Microsoft Flight Simulator 2024\WASM\MSFS2020\fsuipc-lvar-module\work The folder will only be there if you are using the FSUIPC WASM module. Ok, I didn't realize it was 2024 only... Well, its the FSUIPC_WASM.log file that I need to see, and attached only once MSFS2024 has exited.

This is an MSFS issue and nothing to do with FSUIPC. You should use the MSFS/Asobo forums for this issue, not this FSUIPC forum. Sorry, but I can only help with FSUIPC issues, not MSFS issues. I will leave this post in case anyone else has any suggestions, but you are better off using the Asobo forums for such issues. I have also moved your post to the FSUIPC7 / MSFS forum as you posted in the main support forum. John

In what way? They should have been the same... InBuilds did say: so they have no issues with the FSUIPC WASM. Yes - in the WASM persistent storage area, under your AppData\Roaming folder. See the Advanced User guide (WASM section) if you don't know where this is - the details are there. Please only attach this file after exiting MSFS. Your FSUIPC7 log files look ok. Do you have anything else om your Community folder? If so, have you tested with these removed? Does this occur in MSFS2024 only, or also in MSFS2020?

Yep - all looks good now! Cheers, John

I don't have the A300, and, as I said, I cannot see how the FSUIPC WASM module can freeze the sim, especially just for this one aircraft. But I need to see the log files as mentioned in my last post before anything else. What were you using before? Are you using FSUIPC7? You only need the FSUIPC WASM module installed for the following reasons: - using presets/hvars/lvars/calc. code functionality in FSUIPC7 - if using any other add-on that requires it John

Looks like your Saitek Pro Flight Rudder Pedals weren't connected - are you still using these? Please try the attached ini - this shou;d correct things (your registry now looks good!). Connect the rudder pedals, if using, start FSUIPC7 and exit and show me the files again. John FSUIPC7.ini

I don't know what that is, but looks to ne an error with ProSim reading the NavData database - you should ask ProSim. Yes - but no log file attached.... it looks like you are using offsets in the range assigned to "Nico Kaan for Lekseecon(Level D 767, 757)" for this. The landing gear is not assigned in FSUIPC, so I can't really help. Presumably you get the same if you try and move the landing gear lever in the VC? This sounds like an issue with the aircraft (ProSim), or possibly wherever your Landing Gear is assigned. I think you should ask ProSim about this. You should also update FSUIPC6 to the latest and only supported version, 6.2.1 (you are using 6.0.5). John

These are the registry entries, with the ones causing issues in bold: To correct this, first takw a back-up of your refistry (using the Windows Registry Editor). Then unplug the following devices (without FSUIPC or the FS running!): WINWING URSA MINOR CIVIL FLIGHT STICK R WINWING MFD1-L WINWING MFD1-R WINWING Orion Throttle Base II + F18 HANDLE Then download and run (i.e. double-click it) this file: removeDevices.reg Reboot your PC, then re-connect those devices. Then run FSUIPC7 and exit, and show me those 3 files again. Everything should be ok, but I will check the files just in case there is an id or GUID change that may need correcting. John