2 hours ago, Reader said:

 Hello,
I am trying not to confuse, just to explain what I think Asobo and Microsoft intended.
I don't think that they ever intended for anyone to take one of their default MSFS 2020 aircraft

you are trying to move a default plane from 2020 -> 2024, correct?

Understood and yes. Well Asobo did indeed not intend so, but it's very challenging to edit/tweak aircraft in FS2024 because of the ridiculously convoluted virtual file system, which is a hell of a palava, whereas edit/tweaking a simple text file or two is so much easier in fs2020 and takes around a twentieth of the time.

I need the donor aircraft from within fs2020 rather than fs2024 because it's config files are so easy to access. The question is where does the donor aircraft go. BTW I have the steam version so my packages are in a different place but that's no problem. Thanks for your help.

>I think you need your original plane in the location where all the default planes are, and then your mod as usual in the normal community folder. <

Maybe so.

 

1 hour ago, JonathanC said:

 

 

Give this a shot if you haven't already tried it. 

OK, thanks.

I moved the 2020 beaver to 2024 because I didn't like the canoe on the 2024 version. The 2020 version works great in 2024. 

Well Contrail also puts addons in comm and comm..2024 folder. You can go into settings and manage where to put the files if you don't like how it handles them.

4 hours ago, Todd2 said:

I moved the 2020 beaver to 2024 because I didn't like the canoe on the 2024 version. The 2020 version works great in 2024. 

Where did you put it?

One more time.. they all go into the Community folder.  Check the names.. z has priority over ABC etc.

Well over a thousand potential addons, all in my own set of folders and managed by Addons Linker.

My sim is set to use "E:\MSFS2024"

It has all those folders mentioned originally.

But ALL my addons are placed (linked) into the same old "community" folder. If any product installs itself initially into anything like "community2024" it gets moved out of there into my own structure and is managed by AL, so ends up being used via the standard community folder. No issues, and no problems.

I have no control over the stuff that is streamed, i.e. bought via marketplace, so I don't worry about it. Various techniques to hide/enable/disable that stuff, none of which are truly satisfactory for me but that's the way it is.

3 hours ago, Reader said:

Where did you put it?

I had to zip the file and unzip it in my regular community folder.

2 minutes ago, Todd2 said:

I had to zip the file and unzip it in my regular community folder.

Was that to get round the file protection?

19 minutes ago, Reader said:

Was that to get round the file protection?

I'm not sure but I read online that you have to zip the file first. I had to reinstall 2020 to get the plane I haven't used 2020 since 2024 came out. Since I put the 2020 plane in the community folder it overides the 2024 Beaver and you don't get that one but I like the 2020 version much better as you can remove the canoe which I don't like having all the time in the 2024 version. I figure since I own 2020 and 2024 that there is no problem with me using it in 2024.

ASOBOsisation... the Art of making the simple and intuitive, complex and abnoxious ...

They're French !!! That's it 🤣

4 hours ago, jcomm said:

ASOBOsisation... the Art of making the simple and intuitive, complex and abnoxious ...

They're French !!! That's it 🤣

Indeed, even w/o the complexity of (multiple) community folders, I find the labels in My Library for the items I (automatically) inherited from MSFS2020 rather confusing (I’m now exclusive MSFS2024 user).

For example, if I filter on MSFS2020, I find 4 types of labels; Permanently Incompatible, Temporarily Incompatible, Unverified, and No Label. I understand that “Unverified” implies, use at your own risk; the (famous) PMDG MSFS2020 737 NG being in this category (the EFB causes CTD in MSFS2024 for me, otherwise fully functional).

“Permanently Incompatible” implies, I should simply write them off, some of which were (once) perfectly good payware in MSFS2020 (e.g., livery repaint packs).

“Temporarily Incompatible” implies someone (Asobo or/and developer) is currently working on them to make them usable in MSFS2024; a good example been this week’s notification that my (metallic) C208 repaints have been upgraded, at a minimal extra cost (that’s fair).

And, finally the items with “No label” i.e., just MSFS2020 on them, probably imply that they are now good to go in MSFS2024…hopefully…until tested…

8 hours ago, Bert Pieke said:

One more time.. they all go into the Community folder.  Check the names.. z has priority over ABC etc.

No, not true. What is the source for this information? There is no alphabetical priority. That's XPlane. 

38 minutes ago, JonathanC said:

No, not true. What is the source for this information? There is no alphabetical priority. That's XPlane. 

@robert young I can only go by my personal experience with MSFS..  If there is a written explanation by MS, I have not seen it.

When MSFS 2024 was first released,  I decided to try some default 2020 aircraft because I did not like the visuals of the new Bonanza and King Air cockpits.  I copied them over from 2020 into the new Official2020 folder, and they worked!

However, with SU3 (I believe) they stopped working and I had to move them from the Official2020 folder to the Community folder, and they worked again, to this day.  I have nine 2020 default aircraft in my Community folder.

For the various mods to take priority over the default aircraft, their name needs to start with a letter greater than A, since the default 2020 planes all start with "asobo-aircraft".  This priority scheme has been with us since the early 2020 days..

1 hour ago, Bert Pieke said:

For the various mods to take priority over the default aircraft, their name needs to start with a letter greater than A, since the default 2020 planes all start with "asobo-aircraft".  This priority scheme has been with us since the early 2020 days.

You are correct. I forgot this, and was mistaken. I apologize.