I have all my airports in the Community folder (via the AddOnLinker), and nothing in folder Community2024. 
What is the use of Community2024?

Do users have airports in there?

Nico 

Edited January 9Jan 9 by kiek

I honestly don't know but I believe both work.

I thought about use AL and putting my native 2024 stuff in that folder.

But meh hehe

It is only in use if you have both MSFS2020 and MSFS2024 installed. If you only have MSFS2024 forget it. Everthing should be in the Community folder.

I understand from the asobo forums that if you are using both 2020  and 2024 sims, the former is not checking the 2024 community folder. We are supposed to put the native 2024 addons   there only  so that they do not create issues for an fs2020 setup. For 2024 only users,  there is no real benefit in separating addons in different folders. 
 

as mentioned above by Cap737Delta

 

 

Edited January 9Jan 9 by Thanos68

This is still confusing, all my 2020 and 2024 add ons are in the same "community" folder and everything is ok. My "community2024" folder is empty and I don't think (for now) will put anything on it unless would become mandatory someday. If it ain't broke, don't fix it.

1 hour ago, Cap737Delta said:

It is only in use if you have both MSFS2020 and MSFS2024 installed. If you only have MSFS2024 forget it. Everthing should be in the Community folder.

I have both simulators installed, but the MSFS Community folder is separate from the MSFS 2024 Community folder.

Edited January 9Jan 9 by kiek

  

33 minutes ago, kiek said:

I have both simulators installed, but the MSFS Community folder is separate from the MSFS 2024 Community folder.

Then it's not for you. It's for people who want to share the folder.

Edited January 9Jan 9 by Tuskin38

18 minutes ago, Tuskin38 said:

  

Then it's not for you. It's for people who want to share the folder.

Yes. It’s a weird use case - someone who uses both 2020 and 2024, and has addons that they want to use on both, but don’t want to keep two copies - so you have a shared community folder between 2020 and 24. 
 

I really don’t see the point, but I presume some people do this? 

The way I understand it, but not using it as I only have 2024 for the last year , is that if you have a native 2024 addon you put it in the relevant folder and fs2020 is simply not checking it …. A way to make sure that the FS2020 will not try to use an addon that is natively using the 2024 SDK , a safety net for 2020 users…  

if you use 2024 only does not really matter… now if you want to separate the native 2024 addons this gives you a separate repository…but it is not mandatory 

In my addon linker I have defined the usual community as the community and kept the 2024 community as a separate repository … one could of course do it the other way around 

 

 

 

Think its got to do on where you have installed your msfs, in my case i got msfs2020 installed on my e drive and msfs2024 installed on my c drive. I have 2 communities folders one for each on  the drives on where  the sims are installed

21 minutes ago, pete_auau said:

Think its got to do on where you have installed your msfs, in my case i got msfs2020 installed on my e drive and msfs2024 installed on my c drive. I have 2 communities folders one for each on  the drives on where  the sims are installed

No, that's not what we're talking about. This is about something different.

2 hours ago, kiek said:

I have both simulators installed, but the MSFS Community folder is separate from the MSFS 2024 Community folder.

same here

13 minutes ago, pete_auau said:

same here

Right, but this is not what we are saying 🙂

After SU4, 2024 has TWO community folders (even if you don't have 2020 installed at all on your PC). One folder is called Community, and one is called Community2024. This is a new change introduced after SU4, for the reasons discussed above. The purpose is to have the same addon used by both 2020 and 2024, but you don't need to keep two copies of the same addon. It's a niche use case and most people can simply ignore this completely. 

It has nothing to do with having both 2020 and 2024 installed and thus two entirely separate community folders that have nothing to do with each other. 

 

Here's what it looks like. Note that I do NOT have 2020 installed at all. Just 2024, and I never installed 2020 after I reformatted my machine. 

 

Edited January 9Jan 9 by JonathanC

Okay everyone, in summary, we have 3 situations:

• 1 - For those who only have MSFS2024 and native airports:
• Community - install the native airports for MSFS2024 here
• Community2024 - install nothing here
•  
• 2 - For those who have MSFS2020 and MSFS2024:
• Community - install the native airports for MSFS2024 here
• Community2024 - install the airports compatible with MSFS2024 that were also from MSFS2020 here - Note: the developer always informs whether the airport is compatible with MSFS2024 or not.
•  
• 3 - For those who only have MSFS2024 and want to use compatible MSFS2020 airports:
• Community - install the native MSFS2024 airports here
• Community2024 - install the MSFS2024 compatible airports that were also from MSFS2020 here - Note: the developer always informs whether the airport is compatible with MSFS2024 or not.

Note: even if you have MSFS2020 and MSFS2024, the folders are in different locations and there will be no conflict, this is correct.

Asoso got it right.

On 2/7/2026 at 3:51 PM, HighTech said:

Note: even if you have MSFS2020 and MSFS2024, the folders are in different locations and there will be no conflict, this is correct.

Asoso got it right.

I'm about to uninstall 2020 and have had 2024 running for about a year.  Do I need to move anything from the original 2020 Community folder into the one associated w/ 2024?