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

Major Bug XML file size doubling after every save (Build R26)

S

sawblade5

Messages
32
Country
us-kansas
I am posting this to report a major bug in FSX Build R26. I have been working on the Springfield/Branson Airport (KSGF) from stock and modifying it by changing all taxiways to concrete and adding gates. I came upon the bug when I was noticing that every time I saved it took longer and longer each time. I soon realized that for some reason my XML file gotten to over 10 MB in size when it should be alot smaller.

The next thing I did was checked to see what was going on with my XML file and I was noticing it was duplicating all the scenery each time I saved. So basically every time I saved my airport it was doubling in size each time, without my knowledge.

I did find my own way of fixing problem and getting the file back to its proper size. Doing this involved:

1. Saving the airport (yea it will take time becasue of the bug)
2. Closing the airport in FSX Planer
3. Reopening the same Airport.
4. Saving the airport again this time using the "Save As" function.

For now I would recommend this until this bug is fixed hopefully in the next version. I would love to be able to attach the buggy airport but my quota doesn't allow files of more than 1 MB.
 
I have finally identified this bug! It was to do with decompiling a file and then using the 'save' versus the 'save as' option. The 'save' option saves all data in memory even if it wasn't associated with the airport, wheras the 'save as' saves only that data that is associated with the airport. (This is necessary in order to keep xml files intact if they contain more than one airport.) However, this meant that scenery object, etc were being duplicated unneccessarily. This led directly to the huge file sizes that some people have experienced.

This fix will appear in the next release.

The solution suggested above will fix the problem for current files. Thanks for that. :)

-Russell
 
Because this issue can cause some very large xml files to be created we have put out a fix for it. You can update to release 26b, but wither using the File -> Check For Updates option, or by redownloading FSX Planner from the website: www.zbluesoftware.com/fsxplanner

-Russell
 
sawblade5 said:
1. Saving the airport (yea it will take time becasue of the bug)
2. Closing the airport in FSX Planer
3. Reopening the same Airport.
4. Saving the airport again this time using the "Save As" function.

For now I would recommend this until this bug is fixed hopefully in the next version. I would love to be able to attach the buggy airport but my quota doesn't allow files of more than 1 MB.
Click to expand...

Thanks for this solution.

I was getting compile errors, for no apparent reason, and was beginning to pull my hair out trying to find the cause of the issue - the open and re-save as solved it.

For your info : I was already running the 26b version, but still had to do the save as trick to correct the compile error.

Andy
 
You must log in or register to reply here.
Back
Top