No response to FSUIPC7 assignments!

[SMN204]

Hi!
FSUIPC 7.3.25
What could have happened?
I start (before that, an hour ago - everything was without problems) "Piper PA-24-250 Comanche" and..... no response to FSUIP assignments!
FSUIP is started as usual (FSUIPC7: Simulator is available: Connected), in FSUP settings window (Buttons & Switches) it reacts normally and presets are displayed in "Control set when button is pressed" window
Rebooting MSFS - the same thing.
Rebooting PC - the same.
Making presets again - everything is done, but no reaction in the airplane!
I choose a new livery for the same airplane, create settings based on this and... everything works !
Very strange, especially since an hour ago everything worked without problems.Very interesting - what could be the reason?
Here is a "part of the log" ...., as I think, related to this problem.

 3110 Simulator detected
   128125 **** SimConnect open event not received in required time limit: Re-connecting now...
   248344 **** SimConnect open event not received in required time limit: Re-connecting now...
   325500 SimConnect_Open succeeded
   325500 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
   325500 MSFS version = 11.0.282174.999
   326156 Initialising SimConnect data requests now
   326156 Offset file 'C:\FSUIPC7\myOffsets.txt' not found (info only)
   326156 Mapping custom control numbers 69632 - 84232
   326172 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents)
   341125 User Aircraft ID not supplied -- trying default
   341781 F:\Game Setup\MSFS 2022 Install Packages\Community\a2a-aircraft-pa24\SimObjects\Airplanes\pa24-250\aircraft.CFG
   351188 Aircraft loaded: running normally now ...
   351594 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents)
   351594 Aircraft="A2A Piper PA-24-250 Comanche N8351P"
   351610 System time = 16/11/2023 17:01:46, Simulator time = 13:01:45 (14:01Z)
   351610  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '0 (>L:LandFlapsPos, Number)'
   351610  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:Battery1Switch, Bool)'
   351610  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352141  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352188  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352235  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352281  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352328  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352375  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352422  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352469  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   352516  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'

 

  404578  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   404610  [ERROR]: SimConnect_RequestClientData for config failed!!!!
   404625  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   404672  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   404719  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   404766  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   404813  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'
   404860  [ERROR]: Error setting Client Data Calculator Code [-1073741648]: '(L:NavInstrLightSwitchPct, percent) 10 + 100 min (>L:NavInstrLightSwitchPct, percent)'

[John Dowson]

25 minutes ago, SMN204 said:

Here is a "part of the log" ...., as I think, related to this problem.

Can you please attach your full FSUIPC7.log file - you can zip/compress it if is too large. Also attach your FSUIPC7.ini file.

 Looks like there is a problem/issue with the WASM/WAPI, but I need to see your complete log file. Also attach your FSUIPC_WASM.log file - see the WASM section in the Advanced User guide if you don't know how to find that file.

[John Dowson]

Also maybe try the latest beta to see if you get the same issue - just download the FSUI{C7.exe and use it to replace your current one (or just rename your current FSUIPC7.exe so you can easily switch versions), available from 

John

[SMN204]

17 minutes ago, John Dowson said:

Cam you please attach your full FSUIPC7.log file - you can zip/compress it if is too large. Also attach your FSUIPC7.ini file.

 Looks like there is a problem/issue with the WASM/WAPI, but I need to see your complete log file. Also attach your FSUIPC_WASM.log file - see the WASM section in the Advanced User guide if you don't know how to find that file.

 Here are the logs (they are named "prev", I think they are related to the problem)

 

FSUIPC7_prev.log FSUIPC_WASM_prev.log

[SMN204]

11 minutes ago, John Dowson said:

Also maybe try the latest beta to see if you get the same issue - just download the FSUI{C7.exe and use it to replace your current one (or just rename your current FSUIPC7.exe so you can easily switch versions), available from 

I never had this problem ( and I don't have it now, I fly this airplane with a different livery...:-).

I'll try with the old one now....

[John Dowson]

Just now, SMN204 said:

I never had this problem

What problem? Version 7.3.25 contains a memory corruption bug, which is fixed in the latest beta, which is why I have asked you to test with this. I am finishing now, will take a look at your logs tomorrow.

John

[John Dowson]

Your log looks ok. You are getting these errors:

Quote

   184203  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:LandingLightRightSwitch, bool)'
   184203  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:LandingLightLeftSwitch, bool)'
   184203  [ERROR]: Error setting Client Data Calculator Code [-2147467259]: '1 (>L:Battery1Switch, Bool)'

As you are trying to use calculator code/set lvars before they have been loaded. You need to wait until the WAPI has started before you can do this, which is happening quite a bit later:

Quote

   260500   [INFO]: Connected to MSFS
   264797 C:\Users\SMN\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
   284484 -------------------- Starting everything now ----------------------
   290844 Lvars received: 2603 L:vars & 0 H:vars now available
   290859 Lvars/Hvars received - checking aircraft autos....
   290906 LUA.1: let's go!

   290922 LUA.1: PMCO: 18:10:50 - >>>>>> PMCO_FNX32X (V1.03) plugin started <<<<<<
   290938 LUA.1: PMCO: 18:10:50 - >>> Aborted before running the plugin! No Fenix A320 detected. <<<
   293000 Lvars received: 2627 L:vars & 0 H:vars now available
 

Looks like the Comanche is also very slow at creating its lvars - you are getting a lot of reloads:

Quote

   297188 Lvars received: 2648 L:vars & 0 H:vars now available
   299344 Lvars received: 2679 L:vars & 0 H:vars now available
   303688 Lvars received: 2700 L:vars & 0 H:vars now available
   305844 Lvars received: 2712 L:vars & 0 H:vars now available
   314500 Lvars received: 2715 L:vars & 0 H:vars now available
   316688 Lvars received: 2718 L:vars & 0 H:vars now available
   318844 Lvars received: 2721 L:vars & 0 H:vars now available
   439141 Lvars received: 2730 L:vars & 0 H:vars now available
   451859 Lvars received: 2733 L:vars & 0 H:vars now available
   472859 Lvars received: 2739 L:vars & 0 H:vars now available
   481359 Lvars received: 2751 L:vars & 0 H:vars now available
   487703 Lvars received: 2754 L:vars & 0 H:vars now available
   492016 Lvars received: 2769 L:vars & 0 H:vars now available
   496359 Lvars received: 2781 L:vars & 0 H:vars now available
   502859 Lvars received: 2793 L:vars & 0 H:vars now available
   505016 Lvars received: 2796 L:vars & 0 H:vars now available
   507203 Lvars received: 2805 L:vars & 0 H:vars now available
   513703 Lvars received: 2808 L:vars & 0 H:vars now available
   515859 Lvars received: 2823 L:vars & 0 H:vars now available
   518016 Lvars received: 2826 L:vars & 0 H:vars now available
   520203 Lvars received: 2841 L:vars & 0 H:vars now available
   535203 Lvars received: 2850 L:vars & 0 H:vars now available
   545859 Lvars received: 2853 L:vars & 0 H:vars now available
   633688 Lvars received: 2856 L:vars & 0 H:vars now available
   682844 Lvars received: 2859 L:vars & 0 H:vars now available
   693688 Lvars received: 2862 L:vars & 0 H:vars now available
   697844 Lvars received: 2865 L:vars & 0 H:vars now available
   704016 Lvars received: 2874 L:vars & 0 H:vars now available
   708359 Lvars received: 2880 L:vars & 0 H:vars now available
   717016 Lvars received: 2883 L:vars & 0 H:vars now available
   719188 Lvars received: 2886 L:vars & 0 H:vars now available
   806516 Lvars received: 2904 L:vars & 0 H:vars now available
   808688 Lvars received: 2919 L:vars & 0 H:vars now available
   810844 Lvars received: 2925 L:vars & 0 H:vars now available
   812844 Lvars received: 2934 L:vars & 0 H:vars now available
   815016 Lvars received: 2937 L:vars & 0 H:vars now available
   817188 Lvars received: 2940 L:vars & 0 H:vars now available
 

And as for your issue of missing assignments, this is usually due to using an aircraft with a different livery/name that doesn't match the one in your profile section, which is why I asked to see your FSUIPC7.ini file. Please show me/attach that.

John

[SMN204]

8 minutes ago, John Dowson said:

What problem? Version 7.3.25 contains a memory corruption bug, which is fixed in the latest beta, which is why I have asked you to test with this. I am finishing now, will take a look at your logs tomorrow.

John

Hmmm....  went back to the old airplane (7.3.25) - everything is OK !

[SMN204]

2 minutes ago, John Dowson said:

And as for your issue of missing assignments, this is usually due to using an aircraft with a different livery/name that doesn't match the one in your profile section, which is why I asked to see your FSUIPC7.ini file. Please show me/attach that.

FSUIPC7.ini

FSUIPC7.ini

[John Dowson]

Just now, SMN204 said:

went back to the old airplane (7.3.25) - everything is OK !

So it sounds like a problem with the aircraft name in your [Profile.xxxx] section. You should adjust these after creating to use substring matches, to catch all variants, rather than using the full aircraft name that FSUIPC adds.

[SMN204]

3 minutes ago, John Dowson said:

As you are trying to use calculator code/set lvars before they have been loaded. You need to wait until the WAPI has started before you can do this, which is happening quite a bit later:

Everything as usual... stay on RW and tried for about 2...3 minutes or more.

[SMN204]

8 minutes ago, John Dowson said:

So it sounds like a problem with the aircraft name in your [Profile.xxxx] section

I haven't changed anything there for a month since I started flying this airplane. And now I didn't change anything there, just added a second airplane.

It looks like some ghost was near me and did something there .... :-))

[John Dowson]

Change this:

Quote

[Profile.Piper PAЦ24Ц250 Comanche]
1=A2A Piper PA-24-250 Comanche N8351P
2=A2A Piper PA-24-250 Comanche N822JH

to this:

Quote

[Profile.Piper PAЦ24Ц250 Comanche]
1=PA-24-250 Comanche

You also have various profile for the PMDG 737:

Quote

[Profile.PMDG 737 FSUIPC7]
1=PMDG 737-800 Qantas (VH-VXM | 2021 | Mount Hotham)

[Profile.PMDG House (N738BW/2021)]
1=PMDG 737-800 PMDG House (N738BW | 2022)

[Profile.Jet2 G-JZBL]
1=PMDG 737-800 Jet2 (G-JZBL)

[Profile.737 RDS Cargo]
1=PMDG 737-800BCF RDS Cargo Group OM-EDA

[Profile.737-700BDSF TNT OE-IAR]
1=PMDG 737-700BDSF TNT OE-IAR

[Profile.PMDG 737 Sunwing Airlines]
1=PMDG 737-800 Sunwing Airlines (C-GNCH | 2019)

[Profile.PMDG 737-800 Virgin Australia (VH-YIV)]
1=PMDG 737-800 Virgin Australia (VH-YIV)

[Profile.PMDG 737-800 United Airlines  Star Wars]
1=PMDG 737-800 United Airlines (N36272 | 2020 | Star Wars)

You really don't need so many profiles for the same aircraft, different variants. and any new variant you try will need another profile to be created, or to be added to an existing one. You just need one profile:

Quote

[Profile.PMDG 737 FSUIPC7]
1=PMDG 737

or possibly two if you have different assignments for the 700 variant vs 800, but usually not necessary. Choose one profile (not necessarily the 'PMDG 737 FSUIPC7' one - you should choose the one which is most complete), and try using that for all variants. Of course, you can use separate profiles if you so wish, but no need if it is just a livery change. Your profile aircraft name should be a substring of the actual aircraft name that catches all variants of the aircraft you want to use with that profile. Please see the User guide on how to use profiles.

John

[SMN204]

6 minutes ago, John Dowson said:

You really don't need so many profiles for the same aircraft

I got it, thanks.

But the problem with "A2A Piper PA-24-250 Comanche" was when there was only one profile, it's now two...

[John Dowson]

21 minutes ago, SMN204 said:

But the problem with "A2A Piper PA-24-250 Comanche" was when there was only one profile,

Yes, and you (most probably) loaded a different variant, so it did not match that full aircraft name in your profile, so the profile wasn't loaded and therefore you didn't have your assignments. You have no general axis assignments, and only 3 general button assignments, so you would have had no (or hardly any) assignments when you load any variant that wasn't the one in your profile. That is how profiles work....

[SMN204]

16 hours ago, John Dowson said:

You really don't need so many profiles for the same aircraft, different variants. and any new variant you try will need another profile to be created, or to be added to an existing one. You just need one profile:

I "cleaned up" the ini file following your recommendations 👍
For all PMDG 737-800s - now like this:

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

For all Piper PA-24-250 Comanche:

[Profile.Piper PA-24-250 Comanche]
1=PA-24-250 Comanche

[John Dowson]

👍