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 January 18 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 January 19 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.

 

[John Dowson]

14 hours ago, gunny said:

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.

You only have 4 assignments on 2 buttons (to the press and release of each button). Are those switches, sticky-buttons or momentary buttons? If the latter, then what is happening is that the taxi lights are being switched off when you press the button, and then back on on the release, That is how you have assigned, If that is not happening, then you need to set logging for Buttons & Switches and WAPI Debug level logging in FSUIPC, and also Debug level logging in the WASM.

You have nothing assigned to the pitch and elevator axes in FSUIPC.

[gunny]

To minimize errors, I started from scratch to verify if the assignments were correct. These are switches, assigned to the same exact commands that worked perfectly in version 7.4.18. Unfortunately, I thought I had Button & Switches logged, but apparently, I didn’t.

You mentioned that having the same controller listed multiple times in the .ini file isn’t an issue. Should I check the Windows 11 Device Manager to ensure there aren’t any duplications that might be causing a conflict?

Additionally, would it make sense to reinstall FSUIPC under *C:* to rule out any potential path-related issues?

Looking forward to your guidance.

[John Dowson]

1 minute ago, gunny said:

You mentioned that having the same controller listed multiple times in the .ini file isn’t an issue. Should I check the Windows 11 Device Manager to ensure there aren’t any duplications that might be causing a conflict?

You have no issues with any of your devices, and you don't have controllers listed multiple times, You have them listed with an id and with a letter - this is perfectly normal.

2 minutes ago, gunny said:

Additionally, would it make sense to reinstall FSUIPC under *C:* to rule out any potential path-related issues?

No, You will get more issues if you install under C.

I don't know why you are having such issues and why they are taking so long to resolve. From what I have seen so far, all your issues are due to the fact that you re-installed without installing the WASM.

Don't bother with attaching screenshots - it is the files I need to see.

And get into the habit of changing/shortening the aircraft names when you add them to a profile. This:

Quote

[Profile.B737]
1=PMDG 737-800 Ryanair (9H-QAH | 2019 | Operated by Malta Air)

should be

Quote

[Profile.B737]
1=PMDG 737-800

Try setting the required logging and looking at the files yourself. Is the assignment being triggered on FSUIPC? Setting logging for Buttons & Switches will show any assignment being triggered, and for presets setting WAPI Debug level logging will show the preset code being sent to the WASM. Then WASM Debug level logging will show the code being received and applied in the WASM. So try that, and if a preset isn't working, check to see if
    1. the button is triggering the assignment
    2. The assignment is sending the correct calc. code
    3. The calc. code is being received and applied in the WASM

 

[gunny]

I’m still unable to get things to work, neither on the Fenix nor on the PMDG. I followed the same assignment process as before, but nothing seems to respond to the commands.

Reviewing the log file at the end of the day feels overwhelming—it’s quite lengthy, and understanding it fully would take significant time. I’ve never experienced this level of trouble before. In the past, everything was straightforward to configure, and it all worked seamlessly.

Any guidance you can provide would be greatly appreciated.

https://limewire.com/d/c876b5ec-174d-4b85-af0a-ec0604c17624#jpl1hR4kmWEQOgJoDKtRHD6d9XggJNyOQ1Y2jdmjzyE

 

[John Dowson]

To diagnose issues with presets not working, I need to see 3 files from the same session:
   - your FSUIPC7.ini file. This shows me the assignments and profiles. Always attach after FSUIPC7 has exited.
   - your FSUIPC7.log file, with logging for Buttons & Switches, Events and WAPI->Debug level logging activated. This shows me the buttons/keys pressed,
     any assignments triggered and any calc. code sent to the WASM., Always attach after FSUIPC7 has exited.
   - your FSUIPC_WASM.log file, with Debug level logging activated. This shows me if the calc. cide has been received by the WASM and applied to the aircraft.
     Always attach after MSFS has exited.

You only attached a log file. This just shows several button presses triggering the PMDG_B737-7_LIGHTS_RUNWAY_BOTH_ON and PMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF presets:

Quote

...
  1209125 Button changed: bRef=0, Joy=1 (B), Btn=24, Released
  1209125 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 2=UB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_ON,0
  1209125  [DEBUG]: Calculator code sent: 0 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 0 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
...
  1209625 Button changed: bRef=0, Joy=1 (B), Btn=24, Pressed
  1209625 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 1=PB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF,0
  1209625  [DEBUG]: Calculator code sent: 100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
...
  1210141 Button changed: bRef=0, Joy=1 (B), Btn=24, Released
  1210141 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 2=UB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_ON,0
  1210141  [DEBUG]: Calculator code sent: 0 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 0 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
...
  1210562 Button changed: bRef=0, Joy=1 (B), Btn=24, Pressed
  1210562 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 1=PB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF,0
  1210562  [DEBUG]: Calculator code sent: 100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
...
  1211078 Button changed: bRef=0, Joy=1 (B), Btn=24, Released
  1211078 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 2=UB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_ON,0
  1211078  [DEBUG]: Calculator code sent: 0 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 0 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
...
  1211453 Button changed: bRef=0, Joy=1 (B), Btn=24, Pressed
  1211453 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 1=PB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF,0
  1211453  [DEBUG]: Calculator code sent: 100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
...
  1211828 Button changed: bRef=0, Joy=1 (B), Btn=24, Released
  1211828 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 2=UB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_ON,0
  1211828  [DEBUG]: Calculator code sent: 0 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 0 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
.....
  1212375 Button changed: bRef=0, Joy=1 (B), Btn=24, Pressed
  1212375 [Buttons.PMDG 737-800 Ryanair (EI-EMI | 2017)] 1=PB,24,CPPMDG_B737-7_LIGHTS_RUNWAY_BOTH_OFF,0
  1212375  [DEBUG]: Calculator code sent: 100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }
 

You need to check the FSUIPC_WASM.log to see if they are being applied. If they are being applied, and those presets are working, then the runway lights should have flashed on then off 3 times. Not sure why you are getting a button release before a press. I presume that his is either a switch or sticky button, and it was already in the on/pressed state when FSUIPC7 was started.
 

[gunny]

Dear John,

I have some good news: I tested on MS2024, and although there are a few conflicts (the flaps command triggers the spoilers), the assignments do work. Unfortunately, I’m experiencing issues with the aircraft I usually fly in MS2024, making it unviable for me right now.

Back to MS2020, I’m encountering the same problem: the controls are not responding to FSUIPC. I’ve attached the logs, which I believe are set up correctly.

Thank you for your help, and let me know if you need any additional information.

[John Dowson]

Please  set Debug level logging in the WASM via the FSUIPC_WASM.ini file.
Was the FSUIPC_WASM.log file attached when MSFS was still running? If not, the WASM has crashed, but I expect that MSFS was still running...

Your log file shows a few presets were triggered and sent to the WASM:

Quote

...
   459219 Button changed: bRef=0, Joy=1 (B), Btn=13, Pressed
   459219 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 10=PB,13,CPFNX320_LIGHT_STROBE_OFF,0
   459219  [DEBUG]: Calculator code sent: 0 (>L:S_OH_EXT_LT_STROBE)
   459485 Button changed: bRef=0, Joy=1 (B), Btn=13, Released
   459485 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 11=UB,13,CPFNX320_LIGHT_STROBE_AUTO,0
   459485  [DEBUG]: Calculator code sent: 1 (>L:S_OH_EXT_LT_STROBE)
...
   493594 Button changed: bRef=0, Joy=1 (B), Btn=12, Pressed
   493594 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 8=PB,12,CPFNX320_LIGHT_STROBE_ON,0
   493594  [DEBUG]: Calculator code sent: 2 (>L:S_OH_EXT_LT_STROBE)
   493985 Button changed: bRef=0, Joy=1 (B), Btn=12, Released
   493985 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 9=UB,12,CPFNX320_LIGHT_STROBE_AUTO,0
   493985  [DEBUG]: Calculator code sent: 1 (>L:S_OH_EXT_LT_STROBE)
...
   626875 Button changed: bRef=0, Joy=1 (B), Btn=13, Pressed
   626875 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 10=PB,13,CPFNX320_LIGHT_STROBE_OFF,0
   626875  [DEBUG]: Calculator code sent: 0 (>L:S_OH_EXT_LT_STROBE)
...
   627157 Button changed: bRef=0, Joy=1 (B), Btn=13, Released
   627157 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 11=UB,13,CPFNX320_LIGHT_STROBE_AUTO,0
   627157  [DEBUG]: Calculator code sent: 1 (>L:S_OH_EXT_LT_STROBE)
...
   627391 Button changed: bRef=0, Joy=1 (B), Btn=12, Pressed
   627391 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 8=PB,12,CPFNX320_LIGHT_STROBE_ON,0
   627391  [DEBUG]: Calculator code sent: 2 (>L:S_OH_EXT_LT_STROBE)
...
   627922 Button changed: bRef=0, Joy=1 (B), Btn=12, Released
   627922 [Buttons.Fenix A320 - British Airways 'Standard' G-EUUU (2023)] 9=UB,12,CPFNX320_LIGHT_STROBE_AUTO,0
   627922  [DEBUG]: Calculator code sent: 1 (>L:S_OH_EXT_LT_STROBE)
...

But I don't understand these log messages:

Quote

   612766 FirstButtonChange res=00000103 (0.1, 3)
   613610 FirstButtonChange res=00000103 (0.1, 3)
   614094 FirstButtonChange res=00000105 (0.1, 5)
   615438 FirstButtonChange res=00000103 (0.1, 3)
   615969 FirstButtonChange res=00000103 (0.1, 3)
   616907 FirstButtonChange res=00000105 (0.1, 5)
   617282 FirstButtonChange res=00000105 (0.1, 5)
   618735 FirstButtonChange res=00000103 (0.1, 3)
   619438 FirstButtonChange res=00000122 (0.1, 34)
   620250 FirstButtonChange res=00000124 (0.1, 36)
   620860 FirstButtonChange res=00000120 (0.1, 32)
   621250 FirstButtonChange res=00000122 (0.1, 34)
   621797 FirstButtonChange res=00000126 (0.1, 38)
   622391 FirstButtonChange res=00000124 (0.1, 36)

Not sure why those are logged as that message is only logged when the button assignment panel is open. They are all buttons (3,5,32,34,36,38) on your throttle (1) that have no assignments.
Was the assignments window open here?

You need to set Debug level logging in the WASM. then test again - keep the logging console window open (Log->Open Console) and add the DontLogThese ini parameter to your [Profile.FENIX A320] section, i.e.

Quote

[Profile.FENIX A320]
DontLogThese=66068,65957,66519
1=FenixA320
2=Fenix A320
3=British Airways A320

and for your [Profile.B737 PMDG] profile:

Quote

[Profile.B737 PMDG]
DontLogThese=66068,65958,66519,66074
1=PMDG 737-800

This will prevent excessive logging of those events that are continually seen and filling the log.

Then test a few buttons that you have assigned to presets  (with the logging console window open), check the button is triggered and the calc. code sent in the FSUIPC7.log file, and if the calc. code was received and applied in the FSUIPC_WASM.log file. 

[gunny]

Maybe because I have MSFS2020 and 2024 installed I have two 

Both have the log set to debug (I copied them both in the attached package).

In any case, I a logged an entire flight here, hopefully it'll shed some light.

Next step would be cleaning up and reinstalling everything.

FSUIPC debugging.rar

[John Dowson]

13 hours ago, gunny said:

Maybe because I have MSFS2020 and 2024 installed I have two 

You will have separate WASM installations for each version. Debug level logging was active in the WASM log you attached.

If you want assistance, can you PLEASE answer my questions. I cannot help you if you do not answer my questions or follow my advice. You are giving me no information that I can work with at the moment.

Did you attach that FSUIPC_WASM log file AFTER exiting MSFS, or was MSFS still running? Please answer this question, it is VERY important to my understanding of this issue.

13 hours ago, gunny said:

In any case, I a logged an entire flight here, hopefully it'll shed some light.

 

But why? And no, it sheds no light whatsoever. PLEASE follow my instructions. I need to see short log files showing your issue, not huge log files that time to go through looking for errors.
Did you actually have any issues during that flight, and if so, what were they? I see no button presses logged, and no presets called. Just load an aircraft, test a few of your assignments, then exit. You do NOT need to complete a flight, you don't even need to take off...

Did you try what I suggested? You need to test with the logging window open and see what is logged when you press a button. And remove excessive logging by using the DontLogThese ini parameter.

 

[gunny]

Hi John,

I develop software for a living and always do my best to follow your advice. To answer your question: yes, I attached the WASM log after closing MSFS. Feel free to remove any unnecessary details from the file if that’s easier than having me continually revise the .ini.

When I open the FSUIPC window and attempt to reassign buttons, everything seems responsive and correctly identified. But once I return to MSFS, it’s as if FSUIPC isn’t active at all. Interestingly, this issue doesn’t occur in MSFS2024.

Thanks for your support.

[gunny]

Hi John,

I might have found a clue by comparing MSFS2020 and MSFS2024. In MSFS2024, the WASM module works correctly, but in MSFS2020, it’s not even present in the menu.

I followed the standard installation process, but I’m not sure what went wrong. I tried copying the fsuipc-lvar-module folder from the MSFS2024 Community folder into the MSFS2020 folder, but my system won’t allow it—apparently my organization’s policy blocks copying that folder or any of its files, despite allowing other add-ons.

Could this be the root cause? What should I do to get the WASM module running properly in MSFS2020?

[gunny]

A quick update: I attempted to force copy the fsuipc-lvar-module into the MSFS2020 Community folder so that WASM would activate, but I’m still not getting any control response in the simulator—despite FSUIPC correctly identifying inputs.

Oddly enough, everything continues to work fine in MSFS2024.

Let me know if you have any other suggestions.

[John Dowson]

On 1/24/2025 at 10:22 PM, gunny said:

To answer your question: yes, I attached the WASM log after closing MSFS.

Then that would indicate that the WASM had crashed. However, this is not the known issue in the WASM as it did not occur when scanning for lvars.
And in the last set of logs you attached, no button presses (that have assignments) were detected.

On 1/25/2025 at 3:15 PM, gunny said:

but in MSFS2020, it’s not even present in the menu.

But that doesn't make sense. Your log file shows that the WASM was detected and the WAPI enabled:

Quote

   118219 WAPI enabled

However, it does look like the lvars were received but not the initial lvar values, which maybe why the WASM menu is not active, but it should certainly be there.

So it does look like you may be getting a WASM crash, but I have no idea what could be causing this. You could try setting Trace level logging on the WASM. This will generate a huge FSUIPC_WASN.log file.

On 1/25/2025 at 3:15 PM, gunny said:

I followed the standard installation process, but I’m not sure what went wrong. I tried copying the fsuipc-lvar-module folder from the MSFS2024 Community folder into the MSFS2020 folder, but my system won’t allow it—apparently my organization’s policy blocks copying that folder or any of its files, despite allowing other add-ons.

That is very strange - there should be no access issues to the community folder.... Have you moved the Community folder from its default location? Is the path correctly specified in your UserCfg.opt file (InstalledPackagesPath)?

On 1/25/2025 at 3:15 PM, gunny said:

Could this be the root cause? What should I do to get the WASM module running properly in MSFS2020?

That is very suspicious and could be causing these strange issues. The WASM module should be installed in MSFS2020 by the installer. If it is not installing correctly, please show me your InstallFSUIPC7.log file.

But your initial issue was that the WASM module wasn't installed, and I thought you had corrected this. You have also attached WASM log files, so I don't understand why you think this is no longer installed or running,,,

It is hard for me to make any sense of all this. Maybe you should uninstall and re-install MSFS2020. Uninstall FSUIPC7 for MSFS2020 first, and re-install again after you have re-installed MSFS and ran it at least once.