My guess here is there is some issue with the Virtual File System and the installed Marketplace versions (-600 & -700) conflicting with the PMDG direct (-800) installed version, but I’d have to reinstall it all to test.
I’m a bit exhausted by QA Simulator.
It can be a lot.. The hours I’ve spent trying to figure out what is happening under the covers. This issue with the wrong configuration for a PMDG aircraft loading is easily in double digit hours.
I’ve never had any luck in any iteration of flight sim with any PMDG product loading the correct configuration, and beyond that, carrying over the maintenance state. For example, maintenance hours have never counted down and saved, so the Service Based failures never come into effect.
Are you saying that this screen is supposed to automatically load the tail number when you select the livery? I don’t personally own the latest paid upgrades of PMDG products, but a buddy I regularly fly with says it never populates automatically and he has to manually input it, otherwise his config doesn’t load correctly.
Yes, it is supposed to load the tail number for selected aircraft. Before SU3/SU4, it worked reliably. PMDG uses this tail number to identify the proper configuration, maintenance, etc for a given airframe. It makes total sense they would.
While better now, in some conditions FS does not update the tail number when changing aircraft or variants UNLESS you also pick a new livery. As long as you always click on the livery for the variant you switched to, the tail number is correct and everything is happy.
If I have time over the weekend, I’ll re-record that video I did showing how this happens and how to reproduce so you can avoid it.
NixonRedgrave, we are not aware of any such issue, and I have not seen it in our support or on our forums. I quickly tried to recreate the issue on my machines but was unable.
I suggest you contact our support so they can have a look.
Mathijs Kok
PMDG
I did already, but Chris sort of gave me the brush off saying I need to restart the sim when switching variants. His suggestion didn’t work, at all – every restart/every variant/every livery all had the same cockpit config. Restore Original did nothing.
I have wrttten back a number of times with the various things that I had tried to fix the issue, but I have heard nothing back from him.
Perhaps the update to SU5 release didn’t play nicely with the 737s and I need to fully reinstall them all. As I last stated, though, I currently only have the -600 installed with just the Janet livery and that, at least, solved my immediate problem with it.
I wanted to fly, not play QA, so I haven’t reinstalled any other variant/livery.
Thanks for the reply. 
I just loaded first time in SU5 and I can no longer select my different liveries for the PMDG 738. The configure button does nothing.
UPDATE: After searching in more forums, it appears it was Parallel42’s Flow Pro that was conflicting causing buttons to not work in the sim. Sigh. Updated FlowPro and all is fine.
I just upgraded to the 737-700 2024 version (Marketplace) and I am not seeing any of the liveries I install via OC3 in the sim. One thing I noticed is OC3 says installed build is 3.00.112 while in my library the 737 version seems to be 4.0.44. Am I doing something wrong?
That indicates a 2020 version. Did you ever use the 2020 version in 2024?
At any rate, you should probably open a ticket with PMDG Support.
Thanks, yes, I had already installed the 2020 version in my Library, since I understood it was a prerequisite for the Marketplace to offer the update. I actually did that a couple of days before the upgrade option finally appeared in the MS Marketplace.
I was asking here in case anyone had recently gone through the same process and could share their experience.
Download their Operation Center it should detect your install and you can get liveries from there.
I don’t think that is really correct. The fact that you owned the 2020 version through the Marketplace is recorded in your XBox account, not whether you had the 2020 version installed. The upgrade pricing is based on your ownership of the 2020 version through that account, not whether it was installed.
But again, if you haven’t gotten it figured out, reach out to PMDG Support and they will get you sorted. If you’re on PC, open a ticket through OC3 or go to https://support.pmdg.com
Correct, our shop would recognize that, just as the Marketplace does.
Mathijs Kok
PMDG
Is it possible to bind external lights switches (landing/taxi) to controllers or a keyboard in the game? I am not asking about LVARS and 3rd party mapping tools. I tried a few default commands for lights but nothing works.
You can assign any keybinds to functions like ‘toggle landing lights,’ ‘strobes,’ and ‘taxi lights.’
I tried, they don’t do anything in this plane. Will give it another go next time.
I’m on Xbox and have pretty much all of the light switches bound to my MIAP Pro and Turtle Beach yoke (obviously via default key commands).
It might be that we used non-standard functions for that (often needed to get the correct behavior). Support will know.
Mathijs Kok
PMDG
As far as I can recall landing lights and taxi lights were bound to bog-standard commands. I certainly don’t recall any issues binding them when I bought the 737s.
I have a Honeycomb Bravo; the PMDG aircraft are the only ones that don’t respect my default landing/taxi light bindings. I’m sure that’s solvable, but I haven’t bothered since all the other planes work fine.
