Presets not working in 7.5.0 & 7.5.1

[Kimchi]

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]

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....

[gunny]

I have just updated to 7.5.1 and faced the same issue. Attached logs and inis.

 

FSUIPC7.ini FSUIPC_WASM.ini FSUIPC_WASM.log

[John Dowson]

The WASM log file shows that it was attached when MSFS was still running and that you hadn't even started a flight yet. Please always exit MSFS before attaching a WASM log file, and also please set Debug level logging.in the WASM (via the FSUIPC_WASM.ini file).
And I also need to see your FSUIPC7.log file generated showing your issue, preferably with WAPI debug logging set (Log->WAPI->Debug) as well as for Events and Buttons & Switches, so please attach that, but only once you have exited FSUIPC7.

You should switch to using substrings for your aircraft profile names in all your profiles. For example, for your B737 PMDG profile, change

Quote

[Profile.B737 PMDG]
1=PMDG 737-800 Ryanair (9H-QAH | 2019 | Operated by Malta Air)
2=PMDG 737-800 Ryanair (EI-GXK)
3=PMDG 737-800 Ryanair (SP-RKB | 2019 | Operated by BUZZ)
4=PMDG 737-800 Ryanair (G-RUKA | 2018)
5=PMDG 737-800 Transavia (PH-HXK) - Comet
6=PMDG 737-800 SWA (N500WR - Freedom)
7=PMDG 737-700 SWA (N727SW - Nevada)
8=PMDG 737-800 Ryanair (EI-EMI | 2017)
9=PMDG 737-800 SWA (N8681M - Triple Crown)
10=PMDG 737-800 vRYR Ryanair EI-GXK

to

Quote

[Profile.B737 PMDG]
1=PMDG 737-800

and

Quote

[Profile.FENIX A320]
1=FenixA320_BAWGBUSK
2=FenixA320_EZSHBJZY
3=FenixA320_DLHDAIZGAL4K
4=FenixA320_EZYGEZWC_4K
5=Fenix A320 - British Airways 'Standard' G-MIDS (2020)
6=Fenix A320 - easyJet Europe 'Standard' OE-ICN (2022)
7=Fenix A320 - easyJet 'Standard' G-EJCD (2023)
8=British Airways A320 G-MIDS
9=British Airways A320 G-EUUG
10=Fenix A320 - Lufthansa 'Say Yes to Europe' D-AIZG (2019)
11=Fenix A320 - British Airways 'Standard' G-EUUU (2023)
12=Fenix A320 - Lufthansa 'Standard' D-AIZD (2024)
13=Fenix A320 - Aer Lingus 'New' EI-DVK (2019)
14=Fenix A320 - Alitalia 'Standard' I-BIKA (2018)
15=Fenix A320 - Eurowings 'Standard' D-ABZE (2023)
16=Fenix A320 - Easyjet 'Nantes' G-EZUC (2023)
17=Fenix A320 - WizzAir (HA-LWN) 4K
18=Fenix A320 - TAP Air Portugal 'Standard' CS-TNJ (2018)
19=FenixA320 IAE British Airways G-EUUU 4K
20=FenixA320 ITA Airways EI-DSW-4K
21=Fenix A320 - KLM PH-AXA
22=FenixA320 CFM
23=Fenix A320 - easyJet Europe OE-IJE
24=Fenix A320 - Lauda Europe 'Standard' 9H-LOZ (2020)
25=Fenix A320 - Lauda Europe 9H-IHL

to

Quote

[Profile.FENIX A320]
1=FenixA320
2=Fenix A320
3=British Airways A320

This will prevent issues with the profile not being loaded when using a new livery.

20 hours ago, gunny said:

I have just updated to 7.5.1 and faced the same issue.

Updated from which version? There were hardly any changes between 7.5.0 and 7.5.1, and nothing that would effect presets.

John

[John Dowson]

3 hours ago, John Dowson said:

The WASM log file shows that it was attached when MSFS was still running and that you hadn't even started a flight yet.

Thats not strictly true - it could be that the WASM couldn't acquire a simconnect connection, which may be your issue. This is usyally caused by another third party app taking too many connections. FSUIPC can sometimes cause this, if nadly tuned, but the auto-tuning facility should detect this and set auto-tuning to run, and after FSUIPC7 has been ran a few times (2 or 3) it should have tuned itself.
Anyway, if thats the case, the FSUIPC7.log file may help. but I may also need to see a SimConnect.log file to see what is taking all the connections. But let me see the FSUIPC7.log file first, and follow my other suggestions.

John

[gunny]

Dear John

thanks for your reply.

I wanted to attach the new logs but the page won't let me do it...

1 file would exceed the total allowed size of 0.938kB, and was skipped

 

As soon as you can tell me in what other ways I can provide the updated logs I'll be happy to upload them!

In response to your questions, I have uptgraded from 7.4.x (don't remember exactly which) skipping 7.5.0.

I'll adjust the ini file as you suggested, thanks for that hint. In any case, today even the mobi db for "select for preset" was just blank... I have a screenshot for this but see above, I can't upload any file.

I have the FSUIPC_wasm.ini file in two different places: appdata\local\community and wpsystem\.....\appdata\local\packages....\community. I have updated both according to your instructions.

Even after updating the ini file as you suggested there's no connection between FSUIPC and my controls setup, neither there's a chance to reassign the buttons.

I look forward to hear from you again and have your lovely piece of software back at work!

Edited Saturday at 09:40 PM by gunny

[John Dowson]

Your upload limit is rather restricted as you are a new forum user - it will increase the more you post. You can try compressing/zipping it, but if still too large you can use one of the free file exchange services, e.g. https://filetransfer.io/

13 hours ago, gunny said:

I have the FSUIPC_wasm.ini file in two different places: appdata\local\community and wpsystem\.....\appdata\local\packages....\community. I have updated both according to your instructions.

You only need to update the one, but it doesn't matter.

13 hours ago, gunny said:

neither there's a chance to reassign the buttons.

Ok, so the buttons on your controllers/devices are not recognised? If thats the case, please also attach your FSUIPC7.ini and FSUIPC7.JoyScan.csv files. And that would explain why nothing is working, but is not exactly the issue of this topic...

[gunny]

https://limewire.com/d/26649d49-e69e-42d2-8c45-7c2721fb029f#9uiya8w1SPIazag7Hr_bFglN1Szq_y2_3iIMUdY63UI

I have attached all the required files from my latest flight!

I restored the old fsuipc.ini config (the one with all the liveries) because it messed up my control probably because the mobi reference is missing.

Edited yesterday at 03:21 PM by gunny

[John Dowson]

48 minutes ago, gunny said:

I restored the old fsuipc.ini config (the one with all the liveries) 

But you did not run FSUIPC afterwards. The version of the ini is 7.4.18, but the log reports 7.5.1. So this ini was not used by that log file. O need to see files from the same session.

50 minutes ago, gunny said:

because it messed up my control probably because the mobi reference is missing.

No, those changes could not affect MobiFlight in any way. You should make those changes as advised, and if you have issues report them and we can investigate. But if you don't follow my advise, I can't help you.

Nothing was working in the aircraft you tried as all the assignments are empty:

Quote

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=RA,38,C65607,0     -{ELEV_TRIM_DN}-
2=UB,19,C0,0     -{Custom control: <0>}-
3=RA,36,C0,0     -{Custom control: <0>}-
5=RA,32,C0,0     -{Custom control: <0>}-
6=PA,34,C0,0     -{Custom control: <0>}-
7=PA,38,C0,0     -{Custom control: <0>}-
8=UA,34,C0,0     -{Custom control: <0>}-
9=UA,38,C0,0     -{Custom control: <0>}-
10=PB,22,C0,0     -{Custom control: <0>}-
11=PB,21,C0,0     -{Custom control: <0>}-
12=UB,21,C0,0     -{Custom control: <0>}-
13=PB,6,C0,0     -{Custom control: <0>}-
14=PA,4,C0,0     -{Custom control: <0>}-
17=PB,10,C0,0     -{Custom control: <0>}-
22=PA,3,C0,0     -{Custom control: <0>}-
23=UA,3,C0,0     -{Custom control: <0>}-
24=RA,14,C0,0     -{Custom control: <0>}-
25=RA,16,C0,0     -{Custom control: <0>}-
26=PA,18,C0,0     -{Custom control: <0>}-
27=RA,15,C0,0     -{Custom control: <0>}-
28=RA,17,C0,0     -{Custom control: <0>}-
0=RA,36,C65615,0     -{ELEV_TRIM_UP}-

Not sure why that is, but you should remove those and re-assign.

And for your PMDG / FBW / Fenix profiles, they all use presets and won't work as you have not installed the FSUIPC WASM module:

Quote

   145000 *** FSUIPC WASM module not detected - not adding WASM menu

If you selected to install the WASM and it wasn't installed, then check your installation log for errors. You cn try re-installing and install the WASM, and if any issues check the documentation or previously reported issues. There are various known issues that can prevent the WASM being installed.

You may also have issues if you have installed FSUIPC under the Windows Program Files folder:

Quote

Reading options from "D:\Program Files\FSUIPC\FSUIPC7.ini"

?

If that is one you created then thats ok (it is not under c:\), but otherwise it could create issues.

 

[gunny]

Hi John a couple of things just to clarify the situation.

1. With 7.4.18 everything was working perfectly, and I have been using your software for a couple of years I believe. 

2. I have tried to follow your instructions, really appreciated, so there's no need to say "if you don't follow my advise...". 

3. The assignments got empty after I updated the config file following (or at least thinking to be following) your instructions. That's why I restored the previous file. 

4. The log I shared is from the last flight that I made, a few minutes before sending you the logs.

When I installed the 7.5.1 I checked that the WASM module was flagged. I will reinstall it again: should this fix the issue?

All of my simulation software has always been installed on drive D, I did not change anything.

[John Dowson]

5 hours ago, gunny said:

2. I have tried to follow your instructions, really appreciated, so there's no need to say "if you don't follow my advise...". 

I am just saying that you need to follow my advise and change your profile names to use substrings, otherwise your profiles won't work when you use aircraft with different liveries. For example, in the log file you attached, you used the aircraft 'PMDG 737-800 vRYR Ryanair EI-DCJ' which doesn't match any aircraft in your B737 PMDG profile and so the profile  won't have been loaded and you will not have any of your PMDG assignments available.

5 hours ago, gunny said:

3. The assignments got empty after I updated the config file following (or at least thinking to be following) your instructions. That's why I restored the previous file. 

They are empty in the one you attached. If you have one where they are not empty then use that, otherwise you should delete them and re-assign.

5 hours ago, gunny said:

When I installed the 7.5.1 I checked that the WASM module was flagged. I will reinstall it again: should this fix the issue?

If you selected to install and it didn't, check the InstallFSUIPC7.log  file for errors, and see the installation and registration guide on how to resolve any issues.

Once the WASM is installed, your presets should work, but you will have lost your general assignments unless you can install them from backup.

[gunny]

Dear John,

It has been a long day at work, but I’ve tried all the recommended actions:

1. Reinstalled FSUIPC.
2. Loaded a livery where I had already assigned buttons.
3. Amended the .ini file as you suggested.

The good news: I can now see the MobiFlight presets list and assign them again.
The bad news: No action is triggered, even after reassigning the commands. Additionally, the pitch and elevator axis response speed has slowed down by at least half, which has never happened before.

I also tried starting from scratch by deleting the .ini file to let FSUIPC generate a new one, as I noticed that my joysticks were listed twice. However, even after reviewing the user guide, I couldn’t determine why this is happening. Unfortunately, the situation remains unchanged.

At the following link, you’ll find all the logs and screenshots I’ve collected in the hope that we can finally resolve this issue.

Thank you for your continued assistance.