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

MSFS20 ADE 2020 Alpha 21 HotFix 4

Hi Scruffy,
first of all, thank you for your work!
Next, I was trying to change a parking spot type at LHBP' MSFS stock airport using the last ADE beta HF and when I have loaded that airport, the impression I have is that my aircraft is down to uphill is in front of me. My aircraft was parked just in the rear left side of the changed parking spot.
Hope the .jpgs could help.

Thanks a lot!
 

Attachments

  • ADE-LHBP-curve.jpg
    ADE-LHBP-curve.jpg
    1.1 MB · Views: 238
  • ADE-LHBP-mod.jpg
    ADE-LHBP-mod.jpg
    616 KB · Views: 238
As soon as two or more localizers are present, ADE gives an error message when checking XML source via Tools and during compiling of BGL.
As an example just create a new project and process it based on default EDDF, where multiple localizers exists with different Idents and GP angles.
When only one Localizer per RWY is present it seems to work.

Btw. would it be possible to have an export mode that just would create a BGL with modified Localizer / GP / DME definitions and nothing else / absolute minimum that edited / added Localizers / GPs /DME need to work to make sure that nothing else but ILS get overwritten.
 
Hi Scruffy,
attached you'll find the request project backup.
Thank you
 

Attachments

  • lhbp-test_Backup.zip
    1.3 MB · Views: 159
I've been doing some studies of the handmade airports by Asobo and Microsoft in the standard packages and it's updates. For the most part, Microsoft's airports are full of errors which show up when the ADE or A2P recompilations are loaded into the DevMode. Asobo's airports are much better.

asobo-airport-kdfw-dallas-fort-worth recompiled from ADE shows taxipoint errors in DevMode. A2P recompiled shows no errors in DevMode.
If I do a transplant of the TaxiwayPaths from the A2P asset XML to the ADE XML, Devmode happily accepts this, so it seems ADE is doing something different in the creation of the paths.
 
Last edited:
rhumbaflappy said:
asobo-airport-kdfw-dallas-fort-worth recompiled from ADE shows taxipoint errors in DevMode. A2P recompiled shows no errors in DevMode.
If I do a transplant of the TaxiwayPaths from the A2P asset XML to the ADE XML, Devmode happily accepts this, so it seems ADE is doing something different in the creation of the paths.
Click to expand...
I found the error.
A2P uses the <TaxiWayPath> type="ROAD" ADE changes this to <TaxiWayPath> type="TAXI" and that causes the error in DevMode. I think roads don't need hold_shorts or be connected to the main network of paths.
 
rhumbaflappy said:
I found the error.
A2P uses the <TaxiWayPath> type="ROAD" ADE changes this to <TaxiWayPath> type="TAXI" and that causes the error in DevMode. I think roads don't need hold_shorts or be connected to the main network of paths.
Click to expand...

Thanks Dick

I seem to recall that in the early days there was an issue with ROAD type and I set them to be changed. Seems an update has made them viable or perhaps I just got it wrong
 
skatesoft said:
Hi Scruffy,
first of all, thank you for your work!
Next, I was trying to change a parking spot type at LHBP' MSFS stock airport using the last ADE beta HF and when I have loaded that airport, the impression I have is that my aircraft is down to uphill is in front of me. My aircraft was parked just in the rear left side of the changed parking spot.
Hope the .jpgs could help.

Thanks a lot!
Click to expand...
Hi Scruffy,
I have the exact same problem at LHBP. I have only edited taxiway designations and a few parking spot numbers. In fact, the entire apron west of the terminal is now full of large bumps. It looks as though a flatten area has disappeared. Skatesoft has already sent his backup file which must tell the whole story so I won't add mine.
Thanks!
 
Patrick Germain's decompiler is not finding the airport flatten flag, so ADE isn't seeing it:

Untitled.png


The default airfield has the flatten applied. You need to change this in your LHBP ADE project.
Patrick might need to add this to the BGLViewer and A2P.
 
I get this error message popped up when creating a stock airport, any hint what this causes?
 

Attachments

  • 05.02.2022_21.28.01_REC.png
    05.02.2022_21.28.01_REC.png
    4.7 KB · Views: 154
rhumbaflappy said:
Patrick Germain's decompiler is not finding the airport flatten flag, so ADE isn't seeing it:

View attachment 80041

The default airfield has the flatten applied. You need to change this in your LHBP ADE project.
Patrick might need to add this to the BGLViewer and A2P.
Click to expand...
Thanks for the explanation.
I have not found a "flatten airport" option in the ADE menu so I set the flag in the xml and created a new project from xml. The airport is now tortilla-flat. I hope this was the proper way of doing this and that I have not lost something else in the process. I am a novice...
 
Dumb me! I had not clicked on the arrow at the top left to display my project data. All I saw was the empty "new" ADE properties.
Learning every day.
Cheers!
 
Well, in my case ADE20 isn't that talkative. When setting up a project I'm answering each presented question, nonetheless ADE answers any attempt using [strg]+s by a message the an empty path is not allowed (translated). I can safe the project without hassles via the file menu.

What I did wrong?
 
FlyingAxx said:
Well, in my case ADE20 isn't that talkative. When setting up a project I'm answering each presented question, nonetheless ADE answers any attempt using [strg]+s by a message the an empty path is not allowed (translated). I can safe the project without hassles via the file menu.

What I did wrong?
Click to expand...
Is this a project from stock or from scratch or something else. Can you provide some screen shots as I am not clear what questions you mean?
 
scruffyduck said:
Is this a project from stock or from scratch or something else. Can you provide some screen shots as I am not clear what questions you mean?
Click to expand...
Jon, as I have to leave right now I only can do it this afternoon (probably about 15:30Z). Thanks for reacting so quickly.

EDIT: Ha, appointment is canceled...

The project is from stock. I loaded EDDT via ADE and started the work. However, I'm still not sure whether my understanding of all information to be filled in at the beginning is correct (as it seems, not!).

1646221665471.png


This is how it looks at the moment. My uncertainty is first, which information will be used for the folder containing the package for later use in MSFS and second how to deal with the project data being expected in the top right column.

It's most likely my own fault not reading properly the available help docs (even if I tried to).
 
Last edited:
I think you mean the folders specified for the project?

1646235278143.png


If so then ADE creates the needed folders in the project folder

1646235346108.png


It does this automatically under the project folder when you create the project and you should not change them from what ADE gives you. It is a limitation of the alpha that you shouldn't try to change these

The package that is transferred to MSFS is in the Packages folder

1646235487473.png


The output folder is an internal folder for the project and should be left as a period.

1646235775854.png

It is not easy to see! But don't change it and the actual output package to go into MSFS is in the Packages Folder
 
scruffyduck said:
I think you mean the folders specified for the project?

View attachment 80621

If so then ADE creates the needed folders in the project folder

View attachment 80622

It does this automatically under the project folder when you create the project and you should not change them from what ADE gives you. It is a limitation of the alpha that you shouldn't try to change these

The package that is transferred to MSFS is in the Packages folder

View attachment 80623

The output folder is an internal folder for the project and should be left as a period.

View attachment 80624
It is not easy to see! But don't change it and the actual output package to go into MSFS is in the Packages Folder
Click to expand...
Thanks Jon, I already had set it back to the dot ("."), I posted a "trial" as I tumbled over the following message when using "[strg]+s" = "[ctrl]+s".
1646244880618.png
"An empty path is invalid". Via File->Save Project it works - why ever.

BTW, the package-BGL was compiled while having the previous (correct) settings.

EDIT: Is there any way selecting a different folder for the fianlly copied package, instead of the MSFS community one?
 
Last edited:
You must log in or register to reply here.
Back
Top