• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Using FSX object libraries in MSFS

rhumbaflappy

Administrator
Staff member
Resource contributor
Messages
6,514
Country
us-wisconsin
A quick way to use an existing FSX library in MSFS involves creating a package without using Devmode or fspackagetool.
Using the correct folder structure and contents (attached is a zip file of such a package folder}, just copy the FSX folders containing scenery and textures to the package folder.

I used my base FSX objects folder which I found here on my computer:
D:\Programs\Steam\steamapps\common\FSX\scenery\Global\
I copied the scenery folder and the texture folder to the fsxobjects package folder.

Untitled1.png


I then used MSFSLayout Generator to update the layout.json in the package, and then copied the mess to my MSFS Community folder. Done.
Now the FSX object libraries can be used in MSFS.

Brandon Filer's MSFSLayout Generator on GitHub
 

Attachments

Last edited:
Many thanks, Dick. :wizard:

This looks to be an even easier alternative to the MSFS "FSX Compatibility" mode methods you first described 11 Sep 2020 here: :idea:


GaryGB
 
It is simpler. Some nl2000 library objects. (Make sure the BGL contains the text MDLX.
Untitled.png
 
The same general principle works for SimObjects... but airplanes, rotorcraft, vehicles and boats don't work well, if at all.
 
A quick way to use an existing FSX library in MSFS involves creating a package without using Devmode or fspackagetool.
Using the correct folder structure and contents (attached is a zip file of such a package folder}, just copy the FSX folders containing scenery and textures to the package folder.

I used my base FSX objects folder which I found here on my computer:
D:\Programs\Steam\steamapps\common\FSX\
I copied the scenery folder, and it's subfolders and contents to the package folder.

AFAIK the non-Steam DVD retail store (FSX Standard / Deluxe /Acceleration / Gold) equivalent of that FSX_SE folder path is:

[Flight Simulator X install path]\Scenery\Global\Scenery\

[Flight Simulator X install path]\Scenery\Global\Texture\


I then used auto-json to create the layout.json in the package, and then copied the mess to my MSFS Community folder. Done.
Now the FSX object libraries can be used in MSFS.

Brandon Filer's auto_json on GitHub

View attachment 82941

IIUC, MSFSLayoutGenerator auto_json requires a "layout.json" file for input.

Also, MSFSLayoutGenerator auto_json will only write to a "layout.json" file for output.


On my computer, your example fsxobjects.ZIP shows only this:

fsxobjects folder
|_manifest.json file
|_ContentInfo sub-folder
....|_fsxobjects sub-folder
........|_Thumbnail.jpg file


Where does one get the "layout.json" file required for use with auto_json ? o_O


Thanks in advance for your further explanation of the process for those seeking a simple guide to avoiding MSFS' "XML Hell". :)

GaryGB
 
Last edited:
Hi Dick:

Sorry, but I must be missing something here; at the URL above, [ Code ] offers a ZIP download which contains no Auto_json.exe:

https://github.com/HughesMDflyer4/MSFSLayoutGenerator/archive/refs/heads/master.zip


However, within that Master,ZIP, the ReadMe.md file offers this URL:

https://github.com/HughesMDflyer4/MSFSLayoutGenerator/releases/tag/v1.1.0

...which links to a:

MSFSLayoutGenerator.exe

If that is run as Administrator, I get this CMD console message:

No layout.json paths specified.
Usage: MSFSLayoutGenerator.exe <layout.json> ...


Press any key to exit...


Where exactly do we get Auto_json.exe ? o_O


FYI: A Google search found a AutoJson on a French site that had a restricted or dead download link. :banghead:



GaryGB
 
Last edited:
Sorry about the reference to the vaporware auto_json.exe. You can use Brandon's MSFSLayoutGenerator.exe easily by making a blank layout.json as a text file. It will then fill it with the right info.
 
(...Our posts crossed on the server)

OK, by:

...copying all files within these (2) sub-folders:

[Flight Simulator X install path]\Scenery\Global\Scenery\

[Flight Simulator X install path]\Scenery\Global\Texture\


...into these corresponding target folder chains:

C:\Users\Admin\Documents\MyFSProjects\fsx objects\Scenery\Global\Scenery\

C:\Users\Admin\Documents\MyFSProjects\fsx objects\Scenery\Global\Texture\

...then:

creating an empty layout.json in the root of that same [fsx objects] folder chain path

...and running this batch file:

Code:
MSFSLayoutGenerator.exe "C:\Users\Admin\Documents\MyFSProjects\fsx objects\layout.json" "C:\Users\Admin\Documents\MyFSProjects\fsx objects\layout.json"

PAUSE

I get this (over-written) layout.json in the ZIP attached below (which IIRC, represents only FSX default objects).


Now I'm going to try this:

I then used auto-json to create the layout.json in the package, and then copied the mess to my MSFS Community folder. Done.
Now the FSX object libraries can be used in MSFS.

...with the resulting (non-compiled "package" ?) file / folder structure placed into the \MSFS_Packages\Community sub-folder. :stirthepo


UPDATE: Hmmm... "no cigar" thus far; I'll try a fresh scenery project package to see if I can find / place any of the FSX objects.

GaryGB
 

Attachments

Last edited:
I cleaned up the initial post, added a visual aid, and changed the attached zip... which now includes a blank layout.json.
 
This is great! Someone should do a Friday Harbor redux, you know, Acceleration/Steam default and do it complete with the Air Creations trike air start.

maxresdefault.jpg

 
Hi Dick:

Could you elaborate on where and how we are intended to find / select / place these objects in DevMode GUI after the above type of (non-compiled "package" ?) file / folder structure is placed into the \MSFS_Packages\Community sub-folder, and we then run MSFS ?

Thanks again for your initiative with this FSX scenery objects option. :)

GaryGB
 
Last edited:
Hi again:

I finally got some time to adapt Dick's workflow above, and I am very pleased with the results. :cool:

MSFS_2020_2B2_FSX_Test-1.jpg


Many thanks again, Dick for sharing your insights from testing this workflow.


GaryGB
 
Back
Top