Hi, according to this post in the official MSFS forums, it appears that we can override the CFG files and override other files in MSFS 2024, by mimicking the folder structure of the plane we want to override in the Community folder, according to this post:

https://forums.flightsimulator.com/t/su3-beta-finally-able-to-download-default-aircraft-airports-and-scenery/721198/308

One of the issues with using the VFS system to view the CFG file was that it was uncertain whether you could override the CFG values and get MSFS 2024 to accept the new CFG values.  But if this method of overriding the default CFG file works as suggested by hobanagerik in the official MSFS forum SU3 beta thread, that would add even more flexibility to those who want to tinker and modify their planes.

Edit: Matt Nischan confirmed here, that yes, we can override various files by using the Community folder: 

 

Edited May 22, 20251 yr by abrams_tank

In my experience overriding files works, but it is backwards to MSFS 2020.

In FS24 you have to make sure that your own file appears in the file system before the file you want to override. In FS20, the last  file with the same name on a certain path wins.

In short, in FS24 you put "aaa_" in front of your package name, while in FS20 it is "zzz_". Note that the package has to be complete, it needs both manifest and layout JSON files.

Edited May 22, 20251 yr by Lorby_SI

Looks like they're still encrypted though 😕

Would like to see be able to see and play with the new tensor parameters that are being used in the SOBO C172 and Extra300, but it's not going to be possible AFAIK :_/

27 minutes ago, jcomm said:

Looks like they're still encrypted though 😕

Would like to see be able to see and play with the new tensor parameters that are being used in the SOBO C172 and Extra300, but it's not going to be possible AFAIK :_/

According to Matt Nischan, if you know the folder structure for the encrypted planes, you can override those encrypted planes as well.

But I have no idea how to figure out the folder structure of the encrypted planes since it is encrypted 🤣

For the Standard Version planes, they are not encrypted. You can just use the VFS system to get the folder structure of the Standard Version planes.

Edited May 22, 20251 yr by abrams_tank

This is precious information. As for the files being encrypted... well, that's just sad but we know how MS works.

1 hour ago, abrams_tank said:

According to Matt Nischan, if you know the folder structure for the encrypted planes, you can override those encrypted planes as well.

so where is the problem then?

Bert Pieke to the rescue again! he did it before.

   https://docs.flightsimulator.com/msfs2024/html/2_DevMode/Menus/Tools/The_Virtual_File_System.htm?agt=index
 

Edited May 22, 20251 yr by turbomax

16 minutes ago, Nuno Pinto said:

This is precious information. As for the files being encrypted... well, that's just sad but we know how MS works.

The Premium Deluxe and Deluxe planes were always partially encrypted in MSFS 2020. I think Asobo removed some encryption, but they never removed all of the encryption for the Premium Deluxe and Deluxe planes in MSFS 2020.

They will always be partially encrypted because if they don't partially encrypt it, people will just pirate them and then there is no point of selling the Premium Deluxe and Deluxe versions of MSFS 2020.

Edited May 22, 20251 yr by abrams_tank

The A310, A330 aren't premium deluxe aircraft and even the harmless aircraft.cfg is encrypted. This is what i mean.

16 minutes ago, Nuno Pinto said:

encrypted

I always thought that this is just how the Store system works.

TMBK you can also access the VFS using the FS24 developer mode.

In short, you would do this:

1. Create a new package in your Community folder, naming it "aaa-my-package-whatever" or "zzz-my-package-somethingelse" depending on sim.
2. Copy the file you intend to override into this folder, recreating the exact path where the file resides (starting from the source package)
3. Copy the layout.json and manifest.json from the source package to yours
4. Edit the manifest.json (using any text editor of your choice) and replace the author's data with your own.
5. Edit the layout.json, remove all file references except the one that you want to override.
6. Theoretically you should also update the size in bytes for the file and in the manifest.json for the whole package. But in most cases it will work anyway.

For my own use I made a small tool that reads the contents of the package and then creates the json files accordingly.

Nobody wants to hear this but I will mention it anyway: Be mindful that in most cases you will be violating the end use license. Every EULA on this planet has a section in it that says "no decompile - no alteration". If you do this, do it for yourself. Don't share the results on public outlets. Or at least ask the developer first.

Edited May 22, 20251 yr by Lorby_SI

3 hours ago, Lorby_SI said:

In short, in FS24 you put "aaa_" in front of your package name, while in FS20 it is "zzz_".

Are you sure about this? I have packages with zzz_ in my MSFS 2024 community folder and they are working.

1 minute ago, Alvega said:

Are you sure about this?

Quite. At least it was this way until very recently with my WebFMCs. Doesn't have to be the same for all files of course.

Edited May 22, 20251 yr by Lorby_SI

2 minutes ago, Alvega said:

I have packages with zzz_ in my MSFS 2024 community folder and they are working.

I made some of those too but they contain plugins - they don't override anything.

1 hour ago, Nuno Pinto said:

The A310, A330 aren't premium deluxe aircraft and even the harmless aircraft.cfg is encrypted. This is what i mean.

Did you use the VFS system to check?  Follow these instructions to view the CFG files for Standard Version aircraft: 

It works, I tried it for the Cessna 172 G1000. I can view the CFG files just fine. If you didn't use the VFS system, of course it appears that the files are encrypted.  But they aren't encrypted for Standard Version aircraft, you need the VFS system to view the CFG files.

8 minutes ago, abrams_tank said:

Did you use the VFS system to check?  Follow these instructions to view the CFG files for Standard Version aircraft: 

It works, I tried it for the Cessna 172 G1000. I can view the CFG files just fine. If you didn't use the VFS system, of course it appears that the files are encrypted.  But they aren't encrypted for Standard Version aircraft, you need the VFS system to view the CFG files.

Ah... Important detail, maybe it decrypts them and you can see them through there which it would work for me. I'll check it out later, thanks!