Sorry double-post, please delete

Edited September 9, 2025Sep 9 by Daube
double post, please delete

7 hours ago, Langeveldt said:

Ah the monthly ritual

1. Learn of a new MSFS 2024 beta on Avsim

2. Fire up said MSFS 2024 beta. 

3. Stutter, stutter, crackle, crackle.

4. Fire up MSFS 2020.  

5. Enjoy.  

 

7 hours ago, MassiveSim32 said:

Nah.  Step four is -> Go back to MSFS2024 SU3, then enjoy.

Jase

Well, in reality step 4 should be something like "Don't be a useless beta tester and report the issues you've found instead, after ensuring that your sim is configured properly after update". 😉

Early days but no perceptible increase in performance and getting regulator CTDs which has rarely been the case previously. 

I just read this on MSFS forum : 

 

Hi folks,

I can confirm that @CriminalPilot understands this new feature correctly. This is for players who have both MSFS (2020) and MSFS 2024 installed on the same PC and don’t want to duplicate the same mods in two different Community folders, one for 2020 and one for 2024.

To summarize, what it does is this:

Both sims allow you to specify the location of your Community folder. Point both to the folder called “Community”.

If you have a mod/add-on that is compatible with both sims, put it in this Community folder. Both sims will search this folder for mods upon startup.

If you have a mod/add-on that is compatible with only MSFS 2024 but not MSFS (2020), put it in the new Community2024 folder. Only MSFS 2024 will search this folder (in addition to the regular Community folder) for mods.

This ensures that MSFS 2024 will load all your add-ons, but MSFS (2020) will NOT load 2024 mods that aren’t compatible with the older sim.

Thanks,
MSFS Team

 

So for users that have only MSFS 2024, which is the procedure? we move everything on the new folder? If yes , then we need to change the path to addon linker, Orbx, contrail,inibuilds etc 

 

Update: just checked LGAV from FlyTampa which is installed on my community folder and worked with out any issue. Still dont understand why to use the new one ( community2024)

 

Edited September 9, 2025Sep 9 by Seth2021

I guess if you only have MSFS2024 installed, you must do exactly nothing

Getting "license failure" on loading RJ100.

 

19 minutes ago, Seth2021 said:

I just read this on MSFS forum : 

 

Hi folks,

I can confirm that @CriminalPilot understands this new feature correctly. This is for players who have both MSFS (2020) and MSFS 2024 installed on the same PC and don’t want to duplicate the same mods in two different Community folders, one for 2020 and one for 2024.

To summarize, what it does is this:

Both sims allow you to specify the location of your Community folder. Point both to the folder called “Community”.

If you have a mod/add-on that is compatible with both sims, put it in this Community folder. Both sims will search this folder for mods upon startup.

If you have a mod/add-on that is compatible with only MSFS 2024 but not MSFS (2020), put it in the new Community2024 folder. Only MSFS 2024 will search this folder (in addition to the regular Community folder) for mods.

This ensures that MSFS 2024 will load all your add-ons, but MSFS (2020) will NOT load 2024 mods that aren’t compatible with the older sim.

Thanks,
MSFS Team

 

So for users that have only MSFS 2024, which is the procedure? we move everything on the new folder? If yes , then we need to change the path to addon linker, Orbx, contrail,inibuilds etc 

 

Update: just checked LGAV from FlyTampa which is installed on my community folder and worked with out any issue. Still dont understand why to use the new one ( community2024)

 

Frankly, it's much better to have separate community folders because some addons are different/incompatible (for example the handlebar remover) or not needed in 2024 (for example the Aurora addon, Rex Accuseason, Rex airport signs, etc.).

The new approach is more prone to cause crashes and unwanted behaviors, how did Asobo not think about that?

Personally, I created symbolic links with the command "mklink /j" only for the addons that are in common, namely Animated taxi ribbon and FSLTL base (the liveries). Safe and elegant solution without the need of 3rd party apps.

Anybody tried the Maddog yet?

24 minutes ago, MrFuzzy said:

The new approach is more prone to cause crashes and unwanted behaviors, how did Asobo not think about that?

Personally, I created symbolic links with the command "mklink /j" only for the addons that are in common, namely Animated taxi ribbon and FSLTL base (the liveries). Safe and elegant solution without the need of 3rd party apps.

I'm not really sure how this approach is more prone to cause crashes?

This isn't for people who use jlinks ( like you) or products like addon linker (which use junction links). It's for people who sets custom community folders, it allows them the flexibility to designate what are native FS24 addons via the new folder and what are FS24 compatible via the old folder.

For anyone using addon linker or junction links, there's nothing new you need to be doing.

Wow! 

LOVE ASOBO !!!!

6 hours ago, JonathanC said:

The smoothness is incredible! At inibuilds EGLL, with the Fenix, 4K Ultra.. it was 60+ fps the entire way through the takeoff roll.. with ZERO stutters.. It was incredible. Flying through cloud now and it's just super duper smooooooth. 

This is great news. I can't wait to try it

Looks like some good performance and quality of life improvements there, but people need to try it for themselves before believing the early reports, as we had the same 'wow' reports at the start of of SU3 testing.

On performance, I have just got mine fixed at 60fps anyway with FG (pointless going higher as my 4k monitor can only do 60 fps), but anything that makes the PC run cooler and quieter is welcome.  I hope we can find a way of introducing FSR4 for frame generation during the beta (whether officially or not), as I find it better than DLSS FG apart from some ghosting around props and shadows.  Apparently FSR4 has vastly reduced this.

As for the new community folder, I understand why they are doing it, and it will save me some space for sure.

I hope REX can fix Atmos soon, as I was just starting to really enjoy the new look with it.

Edited September 9, 2025Sep 9 by bobcat999

1 hour ago, Lucky38i said:

I'm not really sure how this approach is more prone to cause crashes?

"Both sims allow you to specify the location of your Community folder. Point both to the folder called “Community”."

With such instructions, many users will just throw everything they have in one folder and point both sims to it. 

12 minutes ago, bobcat999 said:

Looks like some good performance and quality of life improvements there, but people need to try it for themselves before believing the early reports, as we had the same 'wow' reports at the start of of SU3 testing.

Absoluetly, my bet is still on reduced settings after the update that half of them not yet realized 🙈🤣

3 minutes ago, AnkH said:

Absoluetly, my bet is still on reduced settings after the update that half of them not yet realized 🙈🤣

Maybe try it yourself before knocking other people's experience?