What happens if you enable a 2020 scenery pack and/or aircraft that exists in 2024?

Discussion Hub General Discussion
, , ,
1

Given the following:

  • Aircraft “X” exists in the edition of FS-2024 you purchased, perhaps even by the same author as an available payware or freeware aircraft in FS-2020
  • Aircraft “X” also exists on your system as a purchased and/or downloaded aircraft you installed within MS-2020
  • It exists in the “My Library” list in 2024 as a 2020 asset, but is disabled.
  • You don’t remember exactly which aircraft are installed in the edition you have.

And. . .

  • You inadvertently enable an aircraft in 2020 that already exists in 2024.

OR

You do the same thing with a scenery overlay.

  • 2024 has a specially detailed version of airport “X” that did not exist in 2020.
  • You downloaded a specially detailed version of airport “X” in 2020 because the original version stank.
  • You enable the 2020 airport overlay in 2024.

What happens?

2

I did exactly this. Too many defects with the FS 2024 SR22T, so I disabled it. I own Premium Deluxe FS2020, so it automatically subbed in the FS2020 version of the aircraft - even warned me about it.

Note you have to explicitly disable the newer version in order for that to happen.

1 Like
3

And how would I know there’s even a conflict in the first place?

When I rebooted after enabling aircraft from the first version, there was no indication that I was trying to install (or enable) two different copies of the same aircraft or scenery object.

I recognized that the Cirrus (Y-tail) jet already exists in 2024 so I didn’t enable it, but I make no bets for any other aircraft, (except for the Rutan Long EZ which I know 2024 doesn’t have.)

4

I did this as well, for the 2020 Premium Deluxe 787-10 in lieu of the 2024 version. I did so because the 2020 version has Simbrief integration, while the 2024 version doesn’t (apparently Asobo wants you to use their integrated flight planning tool which I find to be unsatisfactory).

1 Like
5

There wouldn’t be. The sim by default will do two things:

  1. If there is a 2024 version of 2020 content, it will default to the newer version being Enabled and Disable the older one.
  2. If the vendor tells MS my 2020 product is not 24 ready or MS hasn’t received explicit approval from them - it will say Disabled, not Vendor Approved. You will need to enable it.

So there’s no danger of two exact versions of the same SimObject being in play at the same time.

6

But. . . if you unknowingly enable the 2020 version. . .?

7

Pre SU1 I found it didn’t work. You needed to explicitly disable the newer version. Since I joined the Beta, I have made no such changes so I can’t say it’s the same behaviour now.

1 Like
8

Beta?  We don’t need no stinkin’ beta!

Where is it? Can the two versions coexist so that they can be compared?

9

Sorry, what? :smile: I’m not sure what you’re asking for.

10

AFAIK, an Xbox account can only run one version of the game at a time. For MSFS 2024, this means (at the moment) one can choose to use either v1.2.11.0 (RTM + Latest Hotfix) or v1.3.7.0 (SU1 Beta).

11

Can both the beta and normal versions coexist on the same system at the same time?

This would be useful to determine if a defect is either a regression or a new defect, or is it simply a preexisting problem.

12

Excellent information!

My system is a PC based “native”, (not Steam), installation; however I am sure that this will help other Xbox users with the same question.

Are you planning to join the beta and lend your expertise to the development process?

Thanks!

13

Indeed. I’m running the beta version.

Absolutely! If the devs want me to review any coding in the sim, I’d be happy to do so. Would need to be in Fortran, though… :laughing:

1 Like
14

And how did you get there?  By invitation?

15

Nope - anyone can join. See:

1 Like
16

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.