PMDG liveries not working

[Kimchi]

Hi John, 

Im using several PMDG liveries. Only the Transavia and Air New Zealand work. The Quantas does not work. I have set ShortAircraftNameOk=Substring

All three are modded liveries. And even if i choose a default liveries that come with the 737-800, they wont work. 

[Profile.PMDG 737-800]
1=PMDG 737-800 Transavia (PH-HXK | 2017)
2=PMDG 737-800 Air New Zealand (ZK-XXX)
3=PMDG 737-800 Qantas (VH-VXB | Yananyi)

[Buttons.PMDG 737-800]
0=PE,18,CPPMDG_B737_BATT_GUARD_SWITCH,0     -{Preset Control}-
1=UE,18,CPPMDG_B737_BATT_ON_OFF_SWITCH,0     -{Preset Control}-

 

I have solved the issue in which FSUIPC would stop function. It had to do with Self Loading Cargo scanning for FSUIPC functions "Attempt to detect PMDG seatbelt sign position". There are more options like this and i turned them all off and now FSUIPC behaves normal again
 

[John Dowson]

On 5/1/2025 at 2:35 AM, Kimchi said:

I have set ShortAircraftNameOk=Substring

That should be the default. i.e. no need to set this.

On 5/1/2025 at 2:35 AM, Kimchi said:

All three are modded liveries. And even if i choose a default liveries that come with the 737-800, they wont work. 

[Profile.PMDG 737-800]
1=PMDG 737-800 Transavia (PH-HXK | 2017)
2=PMDG 737-800 Air New Zealand (ZK-XXX)
3=PMDG 737-800 Qantas (VH-VXB | Yananyi)

You are not using substrings...change that section to:

Quote

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

Then any aircraft whose title matches the substring 'PMDG 737-800' will use that profile. That is how substring matching works. Any time you add an aircraft to a profile, or create a new profile for an aircraft, you should edit the aircraft name in the [Profile.xxx] section to be the shortest substring that matches all aircraft you want to capture/use in that profile.

If a profile isn't loaded for a particular aircraft and you think it should, check the title of the aircraft (as logged in the FSUIPC7.log file) and make sure it is captured by an entry/substring match to the names used in the profile section.

On 5/1/2025 at 2:35 AM, Kimchi said:

I have solved the issue in which FSUIPC would stop function. It had to do with Self Loading Cargo scanning for FSUIPC functions "Attempt to detect PMDG seatbelt sign position". There are more options like this and i turned them all off and now FSUIPC behaves normal again

No idea what this means. SLC should not prevent FSUIPC from working, although SLC itself may not work if not configured correctly.

John

[Kimchi]

Thanks for the help!

[Kimchi]

Hi John, just removed the liverie lines. 

Going from this: 

[Profile.PMDG 737-800]
1=PMDG 737-800 Transavia (PH-HXK | 2017)
2=PMDG 737-800 Air New Zealand (ZK-XXX)
3=PMDG 737-800 Qantas (VH-VXB | Yananyi)

[Buttons.PMDG 737-800]
0=PE,18,CPPMDG_B737_BATT_GUARD_SWITCH,0     -{Preset Control}-
1=UE,18,CPPMDG_B737_BATT_ON_OFF_SWITCH,0     -{Preset Control}-

to this: 

[Profile.PMDG 737-800]

[Buttons.PMDG 737-800]
0=PE,18,CPPMDG_B737_BATT_GUARD_SWITCH,0     -{Preset Control}-
1=UE,18,CPPMDG_B737_BATT_ON_OFF_SWITCH,0     -{Preset Control}-

And now none of the aircraft work anymore. What do i do wrong?

 

[John Dowson]

1 hour ago, Kimchi said:

And now none of the aircraft work anymore. What do i do wrong?

You have NO aircraft name strings in your profile:

1 hour ago, Kimchi said:

to this: 

[Profile.PMDG 737-800]

How do you expect that to work? I suggested to use this:

Quote

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

I also explained how this works:

Quote

Then any aircraft whose title matches the substring 'PMDG 737-800' will use that profile. That is how substring matching works. Any time you add an aircraft to a profile, or create a new profile for an aircraft, you should edit the aircraft name in the [Profile.xxx] section to be the shortest substring that matches all aircraft you want to capture/use in that profile.

And explained what to check if a profile isn't loaded:

On 5/2/2025 at 9:40 AM, John Dowson said:

If a profile isn't loaded for a particular aircraft and you think it should, check the title of the aircraft (as logged in the FSUIPC7.log file) and make sure it is captured by an entry/substring match to the names used in the profile section.

Why is this not clear? Sorry but I don't know how else to explain this....

John

[Kimchi]

Hi John, 

Its not clear because its not working for me and i dont know why. I have read the advanced user guide Appendix 2 and i understand your comments above. This is what happens: 

I start MSFS with Current FSUIPC ini: 

[Profile.PMDG 737-800]

1=PMDG 737-800

[Buttons.PMDG 737-800]
0=PE,18,CPPMDG_B737_BATT_GUARD_SWITCH,0     -{Preset Control}-
1=UE,18,CPPMDG_B737_BATT_ON_OFF_SWITCH,0     -{Preset Control}-

The plane i use has X livery and in the aircraft,cfg i see the following: 

[VERSION]
major=1
minor=0

[VARIATION]
base_container = "..\PMDG 737-800"

[fltsim.0]

title=PMDG 737-800 Virgin Australia (VH-YFK | 2019 | Long Beach)
atc_airline=Velocity

I load the aircraft and none of the buttons work.

1) I ALT TAB out of MSFS

2) close FSUIPC.

3) I open the FSUIPC.INI and i delete "1=PMDG 737-800"

4) I save the FSUIPC.INI

5) I start FSUIPC

6) ALT TAB back into MSFS and buttons work. 

HOW?? I have set the parameter: ShortAircraftNameOk=Substring

 

 

 

 

[John Dowson]

If you have issues with presets not loading, please show me both your FSUIPC7.ini and FSUIPC7.log files, the latter with logging for Buttons & Keys activated and showing a button press assignment that is in the profile that should be loaded but is not working.