Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Community folder, liveries, questions

Featured Replies

9 minutes ago, NovemberUniform said:

I want to do exactly the same. There must be some kind of tool / converter to generate the layout.json and manifest.json files to inject the package from the community folder into the sim (on top of the core files - replacing them at runtime).

If I only knew how...

There are three tools to generate the JSONs.

1) The SDK make package tool will do this for you, but requires a package definition XML file (basically an SDK project file). If you're not already using the SDK this can be a pain.

2) There's a python script written and being used by the A320NX group available on their github; you need python installed to run this.

https://github.com/wpine215/msfs-a320neo

3) There's an FSX conversion tool that's a little bit of a misnomer. It actually builds a package out of an existing simobject folder. It also has a secondary function in the application that is specifically made to update the layout.json file when the contents of the package are updated. It just reads the contents and builds the file. This also, to my knowledge, has only been released as visual studio code that needs to be compiled with the Build function in visual studio 2019.

https://forums.flightsimulator.com/t/fsx-import-showcase/165910 (can be found just under the first post, a github link).

The manifest.json file is set and forget - it just defines what is in the package, what it is called, what version of the sim is required to use it and if there are any dependent packages.

The layout.json is critical as it tells MSFS what to do with the files in the folders - it basically tells MSFS to use these files in lieu of any existing official files from the Official content, as well as calling out any new files to be loaded into the virtual file system.

Hope that helps!

5800X3D | Radeon RX 6900XT

4 hours ago, cwburnett said:

Hope that helps!

I'm sure it does. I will first try to follow the official way of the sdk. Thanks for the very comprehensive information. 

cheers,
NiIs U.

AMD 5800X3D | 32GB DDR4 RAM @ 3200MHz | RTX 4070 12GB @ 1920x1050px

On 9/3/2020 at 12:25 AM, cwburnett said:

2) There's a python script written and being used by the A320NX group available on their github; you need python installed to run this.

After sniffing a bit in the sdk documentation I decided to try the above approach, because I have Python installed already for other reasons. It worked indeed. I was able to place my own flight dynamic mods in the community folder and the sim reads them correctly. Thanks again!

cheers,
NiIs U.

AMD 5800X3D | 32GB DDR4 RAM @ 3200MHz | RTX 4070 12GB @ 1920x1050px

I should mention because it has tripped up a bunch of folks that have private messaged me - the manifest.json needs to be in the folder before you run the build, because it must be included in the layout.json file. Otherwise the package won't load into the simulator. So be sure manifest.json is one of the files listed in the layout.json file...

5800X3D | Radeon RX 6900XT

1 hour ago, cwburnett said:

Otherwise the package won't load into the simulator.

Mhhh, that's interesting. The build.py script does not write the manifest.json into the layout.json, even if it's in the package folder. My mods (have tried 2 so far) still work...

cheers,
NiIs U.

AMD 5800X3D | 32GB DDR4 RAM @ 3200MHz | RTX 4070 12GB @ 1920x1050px

28 minutes ago, NovemberUniform said:

Mhhh, that's interesting. The build.py script does not write the manifest.json into the layout.json, even if it's in the package folder. My mods (have tried 2 so far) still work...

I suppose there's always the chance that I'm wrong about that 😉

5800X3D | Radeon RX 6900XT

  • 1 month later...

Just wondering if anyone can help - just downloaded the latest mega livery pack - i then went into my community folder deleted what I thought was the old mega livery folders! - copied the new pack in and it said a "layout.json" and "manifest.json" file already existed in this community folder (i kept both rather than deleted the old one!) but i can't seem to find either of these files sitting in the new or old pack! (except 1 level down in each of the different livery folders) - just wondering whats going on and where the files causing the "message" were actually located ?

  • 2 months later...

I use the MSFS Layout generator...I install it inside the MSFS folder (not community)..go and find the exe in the second folder and create a shortutcu and copy and paste it to your folders were you have the layout..manifest and then anytime you make a change..copy and paste the layout json on the msfs layout generator exe shortcut and it will update your layout automatically.

 

TaNXMMh.png

 

GitHub - HughesMDflyer4/MSFSLayoutGenerator: A drag-and-drop application for updating layout.json files in Microsoft Flight Simulator (2020) packages.

 

Hope this helps 

 

BobM.

 

Edited by unc1rlm

Bob M

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.