• 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 v2 Stock Airport objects

R

rwcatherall

Messages
65
Country
canada
This refers to my post 6/10/14 regarding stock airport objects showing after compile. This problem appears to be back again with v1.65.5396. It was fixed in the previous version.

Bob
 
Bob - it would have made it easier for me to find out what you are referring to if you had posted on the original thread ;) Please attach the project file here that is causing problems or email it to me. I don't think we touched that code in the latest update - but anything is possible
 
Bob

I cannot replicate what you are seeing with duplicate objects.

I have many .ad2 project files that I save and recompile into PD3 V2.4. I have to be very careful that I do not duplicate the bgl and end up with 2 airports. Be sure you delete any bgl file that was made using the .ad2 project file from P3D.

Always run the Simple Airport Scanner and check for duplicate airports.

As Jon posted, attaching your project file would also help if the problem continues.
 
My findings are similar to Jim's. I ran all the same tests that were run to test the fix for the problem we had before and they all passed. The primary issue for P3D was ADE not setting the DeleteAllTowers flag and that is certainly being set now.
 
Sorry I didn't get back to you sooner. However the problem appears to happen when I separate Airport and Scenery files. If I don't separate there is not duplication. This is seen where taxiway signs have been moved from the original stock location. I would suppose that any stock items that haven't been moved would not be noticed. I tested this using to different ad4 files and had the same results. Duplications showed only when the box ticked to separate Airport and Scenery bgl files.

Bob
 
OK I will check that scenario. I also need to check where signs go in a split compile.
 
I ran more test with .ad2, saved to .ad4 and then split compiled. Could not find any problems. I would have to see the airports that Bob is working with in order to see what might cause duplicate taxiway signs and objects.
 
I can replicate something going on in P3D v2.4 I don't see objects being deleted with either split compile or single compile. I am also seeing some other problems that I don't understand. It all works fine in FSX.
 
Hi Bob

no need. I have found one or two weird things with P3D v2. I tend to test in FSX and assume that the code will behave the same way in P3D - I have come to realize this is not the case so I need to run a bunch more tests with P3D now.
 
OK - perhaps we do need to see the project files. I went back to a clean installation and tested deleting stock objects including the tower, taxi signs, generic buildings and library objects. The respective objects were deleted in P3D v2.4 and it did not matter whether I split the compile or not. I did find a problem with the aircraft symbol display being slightly off (which I think is now fixed). But as far as I can see there are no problems with deleting or moving stock objects. My problem was a rogue bgl file and I should know better :oops: My rule is to always remove all third party bgl files before running a test like this and I broke it this time :(
 
That's a good question Jon. The problem showed after converting ad2 to ad4. Taxi links had to be set and then file compiled. If we compiled separating Airport and Object bgl files then the stock scenery objects showed. If compiling done without separation then no stock scenery objects displayed. That's about it. I also noticed that Setting Options->Project->Separate Airport and Object Bgl if set had no effect.

Bob
 
Well I tried with both the ad2 file and the ad4 file. I could not see any problems with stock objects whether the compile was split or not. As far as I can tell the two look identical. I noticed that the micro excludes are visible so at some point this was started from a bgl file. I am not sure that would make any difference. Sorry Bob but I can't replicate this. I did make suer first that I did not have any bgl files in the addon scenery folder that might be related to this airport.
 
Bob

In your P3D .ad4 project file there are no micro excludes for any of the stock taxiway signs. This is why you see stock items such as the duplicate taxiway signs. There are some exclude issues with generic buildings which will also cause duplicates.

Since your .ad4 project file did not start from the stock KLAX but started it life from Ray's KLAX bgl it has the very old single taxiway exclude and some of the generic building excludes that ADE no longer uses.

If you have Prokey you can use Raw Data View and look at the very last exclude. This is the one that will say exclude taxiway signs.
 
Okay Jon and Jim sorry for the confusion. I do have Prokey and will take a look at the Raw Data View. I have to admit that I've just finished KLAS, did a split compile, and no duplications. Regarding KLAX maybe you can shed light on why no duplications when the file isn't split but only when it is split.
 
Bob

I saw on FlightSim that Ray gave permission to use his LAX. Attached is your .ad4 project file. It will spilt compile and no duplicates should exist. Here is a list of changes I made

1. Your current .ad4 is based on the ADE ver 1.47. It is now a ver 1.65 file.
2. Deleted all old style excludes (including the single large taxiwaysign) and added back current micro excludes.
3. You will notice your .ad4 file is larger since it now has 3 times the amount of excludes
4. Removed all the Navaids (VOR's, NDB's, Waypoints) that were part of the old ADE version
5. Rebuilt all the approach code to use current Navaids that do not get compiled in ver 1.65
6. Added all stock Terminal_Waypoints
7. Added nearby Airports, Comms,
8. Set Draw Flags for Taxi Links

Note: In order for me to compile and check I had to set the 2 Models to my path. Open the List Model and select Jetway01 and then edit to your path and save. Do the same for the jetway02. The Red bar in the lower corner of ADE will now turn to Green.

let me know if you have any problems
 
Last edited:
rwcatherall said:
Okay Jon and Jim sorry for the confusion. I do have Prokey and will take a look at the Raw Data View. I have to admit that I've just finished KLAS, did a split compile, and no duplications. Regarding KLAX maybe you can shed light on why no duplications when the file isn't split but only when it is split.
Click to expand...


When LAX was not split it was using the large taxiwaysign exclude that covered the entire airport. Back in the day when ADE used a taxiway sign exclude for the entire airport it had to be listed either first or last (can't remember which). When excludes cover other excludes it can cancel out what is trying to be excluded.

I can only assume since I have not looked at where signs and their excludes go in a split compile that something was not honoring the XML code as per FSX/P3D.

ADE is very residual even when reading backward compatibility. Most of what I did to your .ad4 file would not stop the airport from showing properly except for exclude issues.

Jon would have to give a more indepth answer.
 
You must log in or register to reply here.
Back
Top