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

MSFS ADE 2020 Alpha 21 HotFix 4

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
This is a cumulative fix which can be applied to existing Alpha 21 Installations. Do not use it with any earlier alpha versions.

If you are using an ADE 2020 version earlier than Alpha 21 or wish to try out the application then first install the base Alpha 21 which can be downloaded from here: https://www.mediafire.com/file/tzdvz57ksx4357n/ade_2020_alpha_21_installer.zip/file. Full installation instructions are here: http://scruffyduck.org.uk/ade_2020_help/Process.html

Hot Fix 4 can be downloaded from here https://www.mediafire.com/file/i3re6lm87g48w09/ade_2020_alpha_21_HF4.zip/file Patch installation instructions are here: http://scruffyduck.org.uk/ade_2020_help/Process1.html

Updated version should show 20.21.8008

Release Notes

Added
  • Loading an addon-bgl file where there is a single airport will also load any associated scenery object placements and user included exclusion rectangles. This matches the behavior before the change of decompiler but load times are faster.
  • displayName (Comment) and group attributes added for Aprons. Some other elements have these attributes already and the next release will extend coverage
  • ILS are now included in projects and can be added using ADE. Two way Editing of ILS appears to work. NOTE We have recently confirmed that ILS headings in MSFS are magnetic. Previous sims such as FSX and P3D used true headings for ILS localizer beams. It is not clear what the impact of this is. ADE therefore loads and displays ILS from stock using a mag heading. This results in ILS localizer beams appearing in the display at an angle to the runway based on magnetic variation. ADE creates new ILS with magnetic headings although there is the option when creating them to use true headings if desired.
Updated
  • Project Path in lower right status bar now shows base folder for current project HF4
Fixed
  • Bug that lost secondary approach lights
  • Bug in approach light types
  • Bug that lost or messed up VASI
  • Replaced '\' and '/' in airport names with '-'
  • Bug that could cause jetway connector links not to show in Sim (there may be other issues that could cause this)
  • Bug that allowed library object scale to be zero or negative
Removed
  • Old Comment attribute which cannot be stored in XML (use displayName where available instead)
 
Messages
134
Thank you for the ILS work. I figured out the magnetic bearing for MSFS ILS when I first started work with Alpha 17 (I believe), and yes the localizer symbol will appear angled to the runway centerline in ADE but that is how is works now.

I notice that Navigraph navaids for MSFS now include ILS distances up to at least 50 nm., and the SDK documentation does not provide a maximum range; however, ADE has always put a 30 nm limit for this variable. I cheat by editing the xml directly. Is this limit still in place.

The SDK documentation is hopelessly vague in areas. For example, the runway object has a bearing parameter but SDK doesn't specific if its magnetic or true (it is true) and the ILS object has a bearing parameter and here the SDK doesn't specify magnetic or true (it's magnetic). It's really demonstrating that the Asobo code smashers don't know very much about aviation.

It's doubly odd that the ILS object has a magvar parameter, but uses magnetic bearing so the magvar parameter for ILS is a dummy element. Does nothing.
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
I notice that Navigraph navaids for MSFS now include ILS distances up to at least 50 nm., and the SDK documentation does not provide a maximum range; however, ADE has always put a 30 nm limit for this variable. I cheat by editing the xml directly. Is this limit still in place.
It is still there at the moment. It's not clear why Asobo changed the localizer heading from true to magnetic. I will ask them to make the documentation on this clearer in the SDD docs
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
Experimental

I have found that it is possible to manage comms frequencies in this version. Loading a stock airport will load the stock comms for the airport.

1638778733992.png


These can be added, deleted or edited in List > Comms

1638778787542.png


You can use delete flags to hide the stock values. Use Tools > Raw Data View and access the DeleteNavigation and Airport Delete records

1638778965475.png


I am not sure if DeleteAllFrequencies acts on comms. It may also act on some nav frequencies but the delete flags in the Airport Delete Record should work

1638779110345.png


Save your project and build it to see if your edits have worked. I have tested as far as I can and the sim appears to use revised comms for ATC.

Two Way Editing

Currently Dev Mode does not allow the editing of comms. However it does appear to keep the XML source for comms when saving or building a project in Dev Mode. I have tried both and the comms data remains in the airport source XML

I understand that editing comms could be in a future SU.
 
Messages
80
Country
us-northcarolina
I don't know what is going on but I am using HF4 and am still loosing the secondary approach lights. I copied the project to ADE20 and did a build. Still no secondary approach lights. I have other airports that I have built that do have the secondary approach lights. I can't figure out what the problem is with this one. Runway 24/6 is the only one with approach lights.
 

Attachments

  • KBHM-Birmingham-Shuttlesworth-Intl.zip
    2.5 MB · Views: 140

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
I can see the secondary approach lights in the runway properties and the source XML - are they not showing up in sim?
 
Messages
80
Country
us-northcarolina
Correct, they are not showing up on the secondary in the sim. Furthermore, I have found that they do not show up on one of the secondary runways, but do on the other, on my other airports as well.
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
is this a specific type of approach light?
 
Messages
80
Country
us-northcarolina
It doesn't matter. I tried changing types but neither showed. I had one airport earlier that had the approach lights underground. Had to use a flatten to lower the ground. Didn't understand that one either.
 
Messages
80
Country
us-northcarolina
I changed the airport flatten to the lowest end of the runway and extended it out to the end of the approach lights and now the approach lights are visible at both ends of the runway. Also, it appears that the Snap to Ground doesn't work for the approach lights.
 
Messages
2
Country
unitedstates

Thank you so much for making the ILS addition possible. ADE is such a great tool.
Are there any plans to develop also an approach, or is that still not possible due to msfs coding?
Thanks again.
 
Messages
110
Country
russia
Hi! I can't for the life of me figure out how to assign a name to a taxiway. The option is greyed out... If I add a new taxiway name using the "+" sign I still do not see the assignment anywhere, new taxiways also do not take any name by default. Am I missing something here?
 

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
Hi! I can't for the life of me figure out how to assign a name to a taxiway. The option is greyed out... If I add a new taxiway name using the "+" sign I still do not see the assignment anywhere, new taxiways also do not take any name by default. Am I missing something here?

At the moment it is not easy to do with the property grid. You need to know the index number of the taxi name and enter that

1639562335948.png


The taxi name appears as read only.

An alternative is to turn off Use Property Grid for Edit in Settings > Options > General

1639562466780.png


That will show the old property dialog

1639562561878.png


The reason the Grid is preferred is that the Dialog does not contain new properties.

Finally if you select a taxiway path from the List View and use the edit button you will currently get the old Dialog to edit with. This is true even if Use Property Grid for Edit is checked
 
Messages
352
Country
italy
problem with PAMR stock, airport. I wanted to add lights to runways,but I received various errors and it is impossible to send errors with log.
first message.jpg attribute'type' isnt valid. the Value '10' isn't valid for the type of data 'stVasi'- Enumeration constraint failed.
second error.jpg
Third error.jpg

Ade close itself and doesn't save the project, but I sent you the xml. I solved and I created my project, deleting vasi22 on secondary runway on my xml ( but you have the orignal).
 

Attachments

  • PAMR.zip
    141.3 KB · Views: 128
Last edited:

scruffyduck

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,841
Country
unitedkingdom
problem with PAMR stock, airport. I wanted to add lights to runways,but I received various errors and it is impossible to send errors with log.
View attachment 78966 attribute'type' isnt valid. the Value '10' isn't valid for the type of data 'stVasi'- Enumeration constraint failed.
View attachment 78967
View attachment 78968

Ade close itself and doesn't save the project, but I sent you the xml. I solved and I created my project, deleting vasi22 on secondary runway on my xml ( but you have the orignal).

Replicated it and looking into it

EDIT
Fixed in next update
 
Last edited:
Messages
352
Country
italy
Building a little scenery, when I save, it appears this error:

System.IO.DirectoryNotFoundException:Unable to find part of the path:
'C:\MSFS_2020\ade2020\F20\Vietnam\Vietnam.xml'.
in System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
in System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
in System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
in System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
in System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
in System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
in ScruffyDuck.AirportDesignEditor.MainForm.SaveFS20ProjectData()
in ScruffyDuck.AirportDesignEditor.MainForm.OnSaveAdeMenuItemClick(Object sender, EventArgs e)
in System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
in System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
in System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
in System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
in System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
in System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
in System.Windows.Forms.Control.WndProc(Message& m)
in System.Windows.Forms.ToolStrip.WndProc(Message& m)
in System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
Messages
134
I learned back in my first alpha build that it is best to change your projects location away from under ADE. I have ADE in my c: drive and ADE20 projects on a different drive.

Be sure to run with admin rights.
 
Top