Kimchi Posted December 21, 2024 Report Posted December 21, 2024 Since upgrade to 7.5.0 and now 7.5.1 i have issues using presets. Im using: FS 2020 + PMDG 737-800 + Self Loading Cargo + GSX + FStraffic. I use 4 different hardware devices i mapped buttons to PMDG presets. I start a flight cold and dark. I start the aircraft till is has ground power. Im using switches from a button box. Sometimes they don't work. I have to ALT TAB to FSUIPC and select the profile i created. Once in ground power state i always check if the flap lever and spoiler lever work. They do and i let GSX together with SLC do its thing while i prepare for flight. Once pushed back i want to set flaps 5 but nothing happens. I go back to FSUIPC and it does not recognise the flap lever anymore. When i go back to MSFS and back to the cockpit, the plane goes into complete C&D state again. I have to close down MSFS plus SLC. Start MSFS again and start from scratch, in the hope it all works. Is it possible to get the latest previous version of FSUIPC 7.4.8?
John Dowson Posted December 21, 2024 Report Posted December 21, 2024 If presets stop working, it is usually due to the WASM crashing. This is a known issue, and is caused by continua scanning for lvars. See this FAQ entry for details: With 7.5.0 and 7.5.1, this should be the default, i.e. LvarScanFrequency should be 0 by default in these versions. If it isn't, you have an FSUIPC_WASM.ini file in your WASM persistence storage area - remove that file or update there. If that is not your issue, I will need to investigate further. But this will be next year now as I am now on holiday until January, sorry. 17 minutes ago, Kimchi said: Is it possible to get the latest previous version of FSUIPC 7.4.8? This is available in several other topics if you search, but I do not usally provide older versions. 19 minutes ago, Kimchi said: Sometimes they don't work. I have to ALT TAB to FSUIPC and select the profile i created. If you need to select a profile, this means that the aircraft you loaded was NOT already associated to a profile. This is almost certainly due to you not using substrings for your aircraft profile names. Are you aware of this, i.e. once you add an aircraft to a profie, you should then edit the name of that aircraft in the profile to use a substring that matches all variants. If you don't do this, using the same aircraft but with a different livery will NOT match the profile. Alternatively, you can use the aircraft folder to determine profiles, using the UseAirLocForProfiles parameter. Please see the provided documentation on using profiles, profile substrings and using that parameter. Otherwise, I will need to see your files showing your issue. You should ALWAYS attach files if you have an issue - your ini and log files tell me a lot for such issues. And pleas give a topic an appropriate title....
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now