Button and key assignments lost

[BetterPilot]

I am having a strange combinations of problems outlined in some of the user's posts above. 

 

The axes is saved to my aircraft, however, the button and switches along with key presses are not working. It seems to forget the aircraft that had the button and switches along with key presses assigned even though they are included in my .ini file. This is occurring with all the aircraft I have profiles for. 

I have tried uninstalling and reinstalling several times, and the pattern I keep seeing is when I initially load into an aircraft after a fresh install of FSUIPC, it seems to work, then I get airborne and at some point, 5-10 min later, the button and switches along with key presses are forgotten and non functional. I have the app installed on my desktop which is not a protected folder to my knowledge. Never had the issue before with installing FSUIPC to desktop. Like I mentioned earlier, after I have a fresh install it seems to work for a few minutes, then forgets my assigned profiles with button and switches along with key presses. If it is not a fresh install instance, it doesn't remember anything , even when I manually re-assign the button and switches along with key presses to a specific aircraft. 

I also tried to uninstall Parallel 42 – SimFX and the issue is still there. I also tried FSUIPC7.4.13b and still got the same result. 

 

Thanks

FSUIPC LOG.txt FSUIPC7.ini

[BetterPilot]

Upon further testing, I am finding that the button and switches along with key presses are working when the FSUIPC7 window is selected, but not when my Flightsimulator.exe window is selected as the main window. Not sure if this is part of the issue, but I have never seen this behavior with FSUIPC before. When the MSFS window is selected the button and switches along with key presses is executed inside the sim. 

 

This behavior is only present on the PMDG 737 when I tested, the other aircraft I tested are unresponsive to button and switches along with key presses even when the FSUIPC window is selected. 

 

Thanks

[John Dowson]

11 hours ago, BetterPilot said:

I am having a strange combinations of problems outlined in some of the user's posts above. 

Your issue is not he same as the topic you posted in - I have moved your posts to a new topic.

Your ini file is in a bit of a mess with its profiles, so lets sort that out first. You should try to understand how FSUIPC matches the aircraft name to profiles, and ALWAYS look at your aircraft name when you add it to a profile (in the ini file under the [Prodfile.xxx] section, and edit the name to use a substring to match all variants.  So, for exa,ple, you can replace this:

Quote

[Profile.PMDG 737]
1=PMDG 737-800
2=PMDG 737-800 ASA (N559AS - Xaat Kwaani)
3=PMDG 737-800 SWA (N8710M - Imua)
4=PMDG 737-800 AAL (N947NN - Logo WL)
5=PMDG 737-800 SWA (N8645A - HeartTwo)
6=PMDG 737-800 AAL (N337PJ - Red WL)
7=PMDG 737-800 PMDG House (N738BW | 2022)
8=PMDG 737-800 DAL (N377DE)
9=PMDG 737-800 Ryanair 9H-QCC
10=PMDG 737-800 AAL (N838NN - One World)
11=PMDG 737-800 DAL (N395DN)
12=PMDG 737-800 SWA (N8301J - Warrior)
13=PMDG 737-800 SWA (N8660A)
14=PMDG 737-700 PMDG House (N737BW | 2021)
15=PMDG 737-700 American (N850NN - 2015)
16=PMDG 737-700 American Airlines BW Weathered
17=PMDG 737-800 United (N14242)
18=PMDG 737-700 Sun Country (N714SY)
19=PMDG 737-700 SWA (N430WN)
20=PMDG 737-800 LOT (SP-LWA Niepodlegla)
21=PMDG 737-800 LOT Polish Airlines SP-LWF
22=PMDG 737-800 Southwest Airlines Shamu One (N715SW)
23=PMDG 737-800 Norwegian Air Shuttle AOC LN-NIB
24=PMDG 737-800 American Airlines (N811NN - 2013)
25=PMDG 737-800 KLM (PH-BCA)
26=PMDG 737-800 Lufthansa D-ABEH
27=PMDG 737-800 American 'Legacy Heritage' (N921NN)
28=PMDG 737-800 American 'AirCal Heritage' (N917NN)
29=PMDG 737-800 SunCountry (N817SY - 2022)
30=PMDG 737-700 Southwest Airlines (N714CB | Classic)
31=PMDG 737-800 Qantas (VH-VXM - 2017)
32=PMDG 737-800 American 'Reno Air Heritage' (N916NN)
33=PMDG 737-800 DAL (N3772H)
34=PMDG 737-800 Jet2 (G-JZHP | 2016)
35=PMDG 737-700 Air Canada Ice Blue (C-JNGZ)
36=PMDG 737-800 Caribbean Airlines (9Y-ANU)
37=PMDG 737-800 Air Europa (EC-MPS)
38=PMDG 737-800 SWA (N8647A)
39=PMDG 737-800 AeroMexico XA-AMM CDMX
40=PMDG 737-800 Air Serbia (YU-ANI | 2014 | BW)
41=PMDG 737-800 Alaska Airlines (N915AK - Seattle Kraken)
42=PMDG 737-700 United Airlines (N25705 | 2010 | Merger)
43=PMDG 737-800 Georgian Airways (4L-TGC | 2021)
44=PMDG 737-800 Lauda (OE-LNK- 2011)
45=PMDG 737-800BDSF DHL EC-NUG
46=PMDG 737-700 Brussels Airlines (OO-VEK | 2007)
47=PMDG 737-800 WestJet (C-FUSM)
48=PMDG 737-800 TUI Airlines Netherlands B737-8K5(WL) (PH-TFA - 2021)
49=PMDG 737-700 Alaska Airlines (N612AS | 2019)
50=PMDG 737-800 Alaska Airlines (N520AS | Icicle)
51=PMDG 737-800 United Airlines (N37267 | 2019 | EvoBlu)
52=PMDG 737-700 Luxair (LX-LBR | 2019)
53=PMDG 737-800 Norwegian Air Shuttle AOC LN-ENQ

with this:

Quote

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

I have changed one I can for you in the attached in (please use this going forward), but there are some conflicts that you need to resolve.

First, your 787 profiles, for which you have 2

Quote

[Profile.KURO 787-8]
1=KURO 787-8
2=Boeing 787-8
3=Air Canada C-GHPV B787-8

[Profile.787]
1=Boeing 787-8 British Airways
2=Boeing 787-8 American
3=Boeing 747-8F Atlas Air N856GT
4=Boeing 787-9 (GE) HorizonSim House
5=United Airlines N20904 B787-8
6=LATAM Airlines Chile CC-BBA B787-8

One problem here is the boing entry in bold. If you load, say, the 'Boeing 787-8 British Airways' then entry 2 in your KURO 787-8 profile will match, as well as entry 1 in your 787 profile. Which profile do you want to use with this aircraft?
Also, entry 3 in your KURO 787-8 profile and entry 6 in your 787 profile look suspicious, as these are the same aircraft, different livery, and so really should be using the same profile.
Should this be:

Quote

[Profile.KURO 787-8]
1=KURO 787-8

[Profile.787]
1=Boeing 787-8
2=Boeing 787-9 
3=United Airlines N20904 B787-8
4=LATAM Airlines Chile CC-BBA B787-8

?

You have a similar issue with two A310 profiles:

Quote

[Profile.A310]
1=A310
[Profile.INI A310]
1=Airbus A310-300

If you load the 'Airbus A310-300', then this will match the entry for the A310 profile (A310) and so either profile may be used (i.e. it is not possible to determine which one will be used).

Can you please clean-up these issues, as I cannot look into your issue until I know which profile is being used.

The log file you attached is also pretty useless, and has far too much logging activated.

Can you download and use the attached FSUIPC7.ini file please. Then correct your profile issues, as explained above.
Once that is done, please generate a log file showing your issue, and attach your updated FSUIPC7.log and FSUIPC7.ini files and explain what you did and what the issue was.

12 hours ago, BetterPilot said:

I have tried uninstalling and reinstalling several times

Don't do this - re-installing achieves nothing, and should only be done to update to a new version, changed installed components (i.e. to switch auto-start methods), or to change the installation folder.

12 hours ago, BetterPilot said:

I am finding that the button and switches along with key presses are working when the FSUIPC7 window is selected,

This should only happen with XInput devices, such as the XBox One controller. This has always been an issue with FSUIPC7 - see the readme.txt where there is a solution to this.
Key presses should be recognised when MSFS has the focus.

12 hours ago, BetterPilot said:

This behavior is only present on the PMDG 737 when I tested, the other aircraft I tested are unresponsive to button and switches along with key presses even when the FSUIPC window is selected. 

This sounds very strange...

Anyway, please use the attached ini, correct thos profiles I mentione. Then run MSFS and FSUIPC7, load an aircraft (which has a profile), test a button assignment and a key assignment (when MSFS has the focus), and if not working, exit FSUIPC7 and show me the FSUIPC7.log file together with your FSUIPC7.ini file. Then restart FSUIPC7 and test again. Do you still get the same issue? If so, exit FSUIPC7 and show me the new FSUIPC7.log file (or, if you do both tests, attach the FSUIPC7_prev.log and also the FSUIPC7.log, as well as the FSUIPC7.ini file).

John

P.S. You also have some assignment errors in your A300 keys section - either correct or remove these:

Quote

[Keys.A300]
1=78,10,P,0 << ERROR 24! Line ignored >>
2=81,9,P,0 << ERROR 24! Line ignored >>

 

[BetterPilot]

Hi John, 

 

I cleaned up the .ini file as you suggested and everything is working perfect now. 

 

Thanks for the help!

[John Dowson]

3 minutes ago, BetterPilot said:

I cleaned up the .ini file as you suggested and everything is working perfect now. 

Ok, good. And sorry - I had done most of the work for you but looks like I forgot to attach your FSUIPC7.ini in my last post. Sorry about that. There are other profile sections that need cleaning. 

I have also just released 7.4.13, so please download and use this. Correct the remaining profile sections to use substrings, then add the following parameters in the [General] section to force an auto-tune:

    StartUpTuningActive=Yes

John