One year later

I bought several add-ons for 2020. When 2024 was announced there was a promise of compatibility. That promise has been broken

Just flight ATR, PDMG 737 and 777 are still not compatible. None of my scenery or other smaller add-ons work either.

I’ve gotten promises and that’s all.

The only game in town is the Fenix a320 at more that 80€!:rofl::rofl::rofl::rofl:. Funny that’s it both expensive and the only study model fully compatible.. One year later. This situation is very bad and my question is… is Asobe the issue or are the vendors getting lazy and greedy?

2 Likes

The only compatible study level for FS24? What about the iFly B38M? PMDG 777-200/300ER? Just Flight RJ100?

The aircraft certainly have had some issue requiring compatibility updates. Though many are working fine now.

But, the vast majority of airports and scenery have worked fine almost since day 1.

The A2A Aerostar is a native MSFS 2024 addon. There are others that while not native are compatible.

The Fenix a320 isn’t 80 Euros. It’s less than 50 quid which, by a quick check, is around 57 Euros. Erm, :rofl: :rofl: :rofl: :rofl:

I’ve got the 737 working. Just a flickering efb map bug. But I hear ya.

1 Like

Our 777 is released for FS2024 (not a port, but a true FS2024 product), and that one is free for all existing FS2020 customers. So you are incorrect to state it is compatible.

We do not really care a lot about backwards compatibility. When the platform offers new options and has new demands, the products from the old platform lose relevance very fast. That’s why we do not ‘port’ our 737, but do the same and restructure it for the new platform. Only that way do you end up with efficient code.

And yeah, promises… Most people knew it would be very hard to keep. Remember when FS2020 was promised to have FSX compatibility? In the end, there was zero compatibility. Nobody cared as those products would be 8 years old.

Mathijs Kok
PMDG

7 Likes

Please do tell how you got the PMDG 737 working in FS24.

You have to enable it in 2024 even though it says not verified compatible. Then copy the folder “pmdg-aircraft-736-liveries” from 2020 and put it in your 2024 community folder. Start a flight on the runway. The first time it won’t work. Reset the flight. Next time it takes a minute but everything starts up. Set up a panel state on the FMC to start with runway. You might try other states but not cold and dark. The map on the efb flickers but pretty much everything will work. It’s not perfect but it works and has only crashed on me a few times. If you’re on Xbox I have no clue.

Edit: Change 736 to 738 or whatever you’re flying. If you want to know how to get the liveries to show up in one place I’ve figured that out too so let me know.

There are other ways to do it do. Just doing a Google search will give you an AI overview of all the steps though I haven’t tried them all. So it’s common knowledge out there. Knowing PMDG, they will more than likely have some kind of update to break it.

Oh, and I have the marketplace version. If you bought it from their store the process might be different.

1 Like

Yous really need to up your game though based on the latest Fenix update. :face_with_bags_under_eyes:

5 Likes

I don’t think that’s in their culture. Their culture is $$$$

4 Likes

@captainbond4197
FYI, this topic by @Stardrifter2232 is an unofficial 3rd-party compatibility list, compiled from user feedback:

Who are you claiming “promised” compatibility?

The exact words from the devs, if I recall correctly, were “the vast majority of Marketplace addons will work.” So you citing three products that don’t work is hardly indicative of broken promises, especially as the PMDG aircraft are known to be some of the most complex coded addons available. The more complex the addon, the lower the probability that it will work out of the box. And as Mathijs has said, there are reasons why not every developer will want to make compatible products. Microsoft can’t make promises on behalf of third party devs.

They also mentioned about, “dev opt in”, along with, “possible problems where the dev/s have gone dark”.

Could it have been communicated better? Heck yes it could.

To the OP, it would help to know what sceneries you speak of?

What I find very strange is that the Carenado Cessna 182Q is marked as “Permanently Incompatible” in the library, yet it seems to be working fine so far?

Because it’s the MSFS 2020 version.

1 Like

But this seems to be the only version I have. Are you saying it’s supposed to automatically put a 2024 version into my library if I bought the 2020 version a couple of months before I even had 2024 installed?

I’m pretty sure that if I disable the 2020 version, I don’t have any version in my hanger.

I have no idea. I bought it for 2024 and no longer have 2020 installed to check.