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

ADE v1.79 Dev fails to store some "stock" p3dv5 airports

Sorry Jon, I followed the above steps, used your file name locations as well. Immediately after the "save as", I went to my F:\Active_Data_Set\ADE Work Files\Projects
and it is empty.
The apsf file is as follows:
ProjectName|PHNL_NewLoc_tst
ProjectFolder|F:\Active_Data_Set\ADE Work Files\Projects
CompileLocation|0
culo|0
CustomCompileFolder|K:\My_Scenery
CustomXmlFolder|C:\MSFS\FS Design Tools\Airport Design Editor 1.79 Dev\P35\Xml
GpLayerOutOfBoundsAsked|false
CompileAirport|true
CompileGP|true
CompilePreLoad|true
CompileTerrain|true
KeepCvx|0
SaveXml|2
SplitCompile|false
CompileFileName|PHNL_ADEP5_LAL
AirportIdent|PHNL
ProjectID|cba513a5-855c-4884-a72b-519273fce803
Comment|
 
Again, this only happens with "some" stock airports...not all, as I mentioned earlier. I first found this with Honolulu International (PHNL) and with Portland (KPDX).
 
Jon, hang on...a little more testing here. This might not be "legal" for ADE to do, but I physically moved the stock airport bgl (APX05240.bgl) from P3Dv5 scenery\0003\scenery to the exact same place in the P3Dv4.5 folder (yes, I cut and saved the original v4 file FIRST). I then opened ADE (dev), selected V4 and went thru the same above process, same airport PHNL, and the results were the same "the airport was NOT stored". My guess is the problem is with any file attributes possibly associated with PHNL. Since LM and ORBX are "partners" now and ORBX has its "cityscapes" (which BTW there is one for Portland, as well as all of Hawaii), could they have kept the stock airport from being accessed (BTW, the stock airport in V5 is just like V4...extremely in accurate for flying into or out of..
Just a view from the cheap seats.
Cheers
 
Do you really have exactly the same folder on your computer as I have on mine?
 
OK I am at a loss with this. I will run a test here with the airports you tried. Can you also please repeat this but using a different set of airports and use Save rather than Save As. I need to see if the problem is in the common saving code (which is effectively standard Windows function) or in the custom code for Save As

I ran a test with the six airports you tried. In v5 mode I loaded each in turn from the stock airport list and immediately used Save As. All six went where I specified and there were no failures.
 
scruffyduck said:
OK I am at a loss with this. I will run a test here with the airports you tried. Can you also please repeat this but using a different set of airports and use Save rather than Save As. I need to see if the problem is in the common saving code (which is effectively standard Windows function) or in the custom code for Save As

I ran a test with the six airports you tried. In v5 mode I loaded each in turn from the stock airport list and immediately used Save As. All six went where I specified and there were no failures.
Click to expand...
Jon, given what you have seen on your end, I have decided to do a little "testing" on my end, starting with a complete uninstall of v5 and a full reinstall of v5 on another physical HDD. Then I will run some tests that you requested and advise the results.
Why am I going thru this...well, I have had v5 installed on an M.2 HDD and I want to remove all things that may be unique in their operation. Will advise, once the download (yes, going with a "fresh" copy) is up and running.
 
Thanks - I appreciate that. If we can pin down the issue to ADE then, of course, I will implement a fix
 
OK, I have completely uninstalled v5, then downloaded v5 onto a different SSD (standard sata). Installed v5 and SDK on that SSD (the same SSD that previous held for years, P3Dv3, which I deleted before downloading a new copy of v5). Registered and ran P3Dv5, no problems. Open ADE (Dev) set the folders to the new SSD location, kept the project files in the same place (on drive F...same as you have), loaded stock airports at random. Question, ADE spends an enormous amount of time (maybe the very first time) "Loading Detailed Footprints" and "Loading Data and Model Footprints"...minutes and once I just terminated the task it was taking nearly 5 mins.). Once loaded I did a Save Airport. The very same airports fail to save as before. Question...why did you pick Afghanistan for me to try...any particular reason? For all of this, on the new drive and a full new install. I am at a loss. I am not overclocking anything, all is vanilla. All SSDs are Samsung. If it would be of any help, I can mount up an HDD and run it off of it if you think that would be of any value.
Cheers
 
Jon, this might just be adding to the confusion, so I apologize first off. I went back to the file name for the Kandahar airport in v5 (APX65200) and found it was the same location in v4 so I renamed the v4 file to ORIGAPX65200 and then I moved the v5 APX65200.bgl to the v4 location (\Program Files\Lockheed Martin\Prepar3D v5\Scenery\0802\scenery). First I ran ADE (general release:
Application 01.76.6715.14291
Engine 04.75.6712.18978
And "open stock airport" pointing to Kandahar. I received the error in the attached screen shot.
Then I exited ADE and opened ADE Dev, selected v4 and then "open stock airport". Opened like a dream, no errors. Then the bad news, I did a "save as" and nothing was saved.
FYI only...
I got to stop thinking about this for a while...its starting to hurt :)
Cheers
 

Attachments

  • Kandahar_5to4w_oldCapture.PNG
    Kandahar_5to4w_oldCapture.PNG
    646.8 KB · Views: 180
I chose Afghanistan because it is at the top of the country list and I don't work with those airports. I really have no explanation for what is happening. It seems perverse. v5 airport bgl structures are different than v4 so putting one into v4 is likely to cause an error.
 
scruffyduck said:
I chose Afghanistan because it is at the top of the country list and I don't work with those airports. I really have no explanation for what is happening. It seems perverse. v5 airport bgl structures are different than v4 so putting one into v4 is likely to cause an error.
Click to expand...
I ran into a similar situation with ADE in working with P3Dv4 and the work I was doing with KDFW. It was the same problem and the only way I fixed it was to reduce the total size of the AD4. With v5 and if you look at a couple of the stock airports that fail to "save" they have a "massive" number of scenery objects over the same in v4. That is what led me to this situation, I wanted to delete many of these stock scenery objects from PHNL because they actually dont belong on the airport itself. LM has inundated us with all manner of buildings that in real life do not exist and I have yet to figure out their logic in doing such. I would like to be able to play with the size of say PHNL (honolulu) or OAKN (Kandahar) so if on your end you can "save" either of these v5 airports, could you send me either save that I can edit with ADE to remove the incorrect stuff, etc.? Are there any specific versions of such things as visual C++ or .Net or other that I should / should not have installed, etc?
 
Maybe this helps. I did Bagram(failed to store), Kandahar(failed to store) and Kabul(stored). Both Bagram and Kandahar had NDB related approaches. Navaids list for both shows no NDB's visible. Compiling the defaults failed with NDB errors. Files attached.

Starting to look like LM didn't update all the approaches to align with the new Nav data,
 

Attachments

Last edited:
gsand said:
Maybe this helps. I did Bagram(failed to store), Kandahar(failed to store) and Kabul(stored). Both Bagram and Kandahar had NDB related approaches. Navaids list for both shows no NDB's visible. Compiling the defaults failed with NDB errors. Files attached.

Starting to look like LM didn't update all the approaches to align with the new Nav data,
Click to expand...
So you too found that Kandahar and Bagram failed to store?? If yes, can you also try Honolulu and Portland International? Honolulu compile fails the same as you have listed for Bagram and Kandahar. Curious if your Honolulu and Portland fail to store, even without a compile, just open the stock airport and save or save as.
 
OK - remember the thing here is that this is actually just a file Save As operation after loading a stock airport and not related to compiling.

The errors you report gsand are old error fixed in the current version of 179. Please update to 1.79.7422 and try again. Approach Type -4 is a TACAN approach
 
Last edited:
PHNL Save As works fine here and goes into the expected folder.

1588240393507.png
 
Also I see Lemon mention slow load times for Object Footprints. This is because you set up a new installation and again has nothing to do with saving the project file
 
scruffyduck said:
Also I see Lemon mention slow load times for Object Footprints. This is because you set up a new installation and again has nothing to do with saving the project file
Click to expand...
SUCCESS!!!!!...I just updated to your latest ADE
Application 01.79.7422.11357
Engine 04.75.7421.37709
I am now able to "save" or "save as" PHNL, KPDX, OAKN and I suspect others. Can I gather from this that changing the airport boundary to reduce the massive number of stock objects did the trick?
 
You must log in or register to reply here.
Back
Top