• 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.

Recommended File Management

D

dcmiller58

Messages
349
Hello, all.

I know that FSX uses separate files for airport, terrain, and others.

In my first project I discovered my basic .xml file was getting really full. I had thought it was best to keep everything in one or two files for simplicity sake. So, I had scenery objects and airports in the same file.

Now I am thinking it would be beneficial to use one file for airports, one file for scenery objects and one file for terrain (the cvx file generated out of FSX_KML) for each location. My project has six locations (airfields).

What is your advice on managing the data by splitting it up into separate files?

Thank you in advance,

Derrick
 
I think it comes down to personal preference, bearing in mind that certain elements should precede others in an XML file (For BglComp anyway). If you split files generated using BglComp too much then you would need to be aware of the order that they are read by FSX if you do not want unexpected results.
 
Thanks, Jon. I can see that file size is not really much of an issue given the examples I have inspected with SDE. There is a lot of information.

I see that the airport info has to be ordered a certain way and contain specific elements. I am thinking scenery in one file, airports in one file, extrusions in one file, and terrain in one file is the way FSX does it.

That will be the pattern I think I will work. That should make BGLcomp happy as well as keep the number of files down for the end user to deal with.
 
I am thinking scenery in one file, airports in one file, extrusions in one file, and terrain in one file is the way FSX does it.
Click to expand...

Makes sense to me
 
You must log in or register to reply here.
Back
Top