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

P3D v5 P3Dv5.2 stock objects (again) overlay custom objects

I first apologize if this is NOT the correct place for this post.
LM just released P3Dv5.2 and for custom built airports, once again LM overlays the custom work with all manner of "stock objects". This time, however, many of the stock objects are not shown when opened with ADE or are shown as "black boxes". My fix was to take my customer airport (KAUS) and simply "load the stock objects" in my exiting project file. (Note: prior to doing this, my existing project file contain NO objects marked as "stock" in the listing). Once the stock data is loaded, I used the "List" option for each type of stock object and simply deleted all those that were in fact marked as STOCK. Compiled by project file and it appears to have solved the problem.
Tom, if you recall, when v5 came out LM made some sort of decision to fill the airports (most) scenery with all manner of objects, most, if not all, were totally inaccurate for a particular airport. All of these objects were part of the "stock" airports and when bringing a customized airport project file from v4, all of these scenery objects were "overlayed" onto the custom project file.
ADE (Jon M) was then modified to reset the "stock data" flag for all such in the original project file, then one would "load the stock data" and then "by list" delete all the "stock data" and compile leaving a "clean" scenery file. That all changed for many stock airports with the release of v5.2 and it all reverted back to the original problem as see with v5. (aka, LM did not eliminate / correct the original problem). In addition, LM added even more stock scenery objects to many medium/large airports in v5.2. All of these will simply overlay (as in duplicate) any custom scenery objects that you may have for a particular airport.
Net/Net, with the implementation of v5.2, you will need to follow the process described by Scruffyduck in the thread about moving a project file from V4 to V5, once again.
This is NOT an ADE issue/problem, but ADE is key to correcting it...