The first public release beta for ADE9X is now available. This is the first version of ADE to support both FS9 and FSX. It is beta and therefore you should not use it for any production work or on your valuable airport files! Please read and act on the readme file - you have been warned.
It can be downloaded from here:
For information I am reproducing the readme information below:
ADE Version 1.42.08
INTRODUCTION AND WARNINGS
This is a beta version of ADE9X
ADE9X is the dual FS Version of ADE and supports both FS9 and FSX. Each version is handled separately so that users can have different settings depending on which version they are working with.
- Use it on any valuable project
- Try to load any of your existing FSX ADE projects in FS9 mode. It is possible but if you value your FSX work please dont!!
- Load this version over any existing ADE installations,
- Either start by importing an existing airport bgl file or by loading a stock airport.
- FSUIPC. If you do not have it then you need to download FSUIPC for each version of FS you wish towork with. The unregistered versions work and you can get them here http://www.schiratti.com/dowson.html. ADE no longer uses SimConnect directly for either version
- Microsoft dotNet Framework 3.5. I think more people have this now - certainly with Vista.
- copy all the contents of the folder here called ADE 142.08 into a suitable location on your system.
- If you wish make a short cut to Airport Design Editor.exe
- Run Airport Design Editor.exe
- A selection screen will open showing what versions of FS ADE has found. You need to repeat the new user wizard installation for each available version. so
- Select a version and Click OK. ADE will start in that mode. Once loaded go through the New User Wizard and when it is completed close down ADE.
- If you have a second version of FS available then repeat the above.
ADE should now be installed and working for each version of FS you have on your computer.
If you are not familiar with ADE for FSX then please download the appropriate manual (English or German) from www.downloadcenter.scruffyduck.org.uk. While there are some differences in this version the current manual explains how things work.
Loading from stock in ADE9 or ADEX is the same - nothing has changed. ADE will load the stock airport and then all the stock data associated with it. You can then use ADE to work on your airport in whichever version.
Starting from an existing bgl file. We expect that a lot of FS9 users will want to load an existing AF2 file to work on and extend. This is still being worked on so feedback on this is very important to the design team. This is how we suggest it is done:
Load you AF2 file using the open from bgl option. This will bring in all the data from that file. You can, of course just work with that if you wish however to bring it up to a full ADE project you need to load the stock data.
Select Tools > Load Stock Data. You will see a dialog asking you what categories you wish to import. Generally tick them all and then click Import. This should load all the stock data for the FS9 airport into the project.
You could choose just to load some categories. ADE will remember which categories you have loaded. This loader is experimental and the following observations are made:
- If you have loaded from stock you cannot change the status of Objects, taxi signs or approaches.
- If you untick any of the following after they are loaded: Comms, Fixes/Naviads, Nearby Airports, Objects; then all stock items in those categories will be removed from your project
- Unticking Approaches or Taxi signs will not remove them. As mentioned abover this loader is experimental so the behavior is not fixed!
That it is - after that you should be able to use ADE9 as ADEX.
One of the major issues arising from loading AFCAD files into ADE9 (or ADEX) is the treatment of stock ILS. AFCAD does not keep a copy of stock ILS unless you move it or otherwise edit it. ADE always keeps a copy. Thus to get all the ILS you must import the stock data.
Neither FS9 nor FSX allow the deletion of stock navaids. In most cases this is not so important. It is, however, important when it comes to ILS. These cannot be deleted. Deleting a runway in AFCAD that contains ILS creates some odd situations. ADE uses a concept of Orphan ILS. An orphan ILS is one where the runway it is assigned to no longer exists or one that a user has 'deleted' The microsoft compiler insists that all ILS are assigned to a runway. ADE uses a concept similar to cross wind runways and adds a small 'Orphans' runway. Any ILS not assigned to a runway will be attached to this runway. The same applies to a stock ILS if the user 'deletes' it. The orphan runway with the orphaned ILS is located north of the airport reference point at 5000m. If this location, or the heading of the ILS feathers is likely to conflict with another airport then you can drag the orphan runway or rotate it to change the position or heading of the orphans. All orphans are named 'DO NOT USE' This probably won't affect many users and is still experimental.
COLOR CODING OF TAXIWAY LINKS
There is a new option that allows you to change the color of taxi links (not runway links). This is available from the property dialog and is intended to allow designers to identify sections of complex taxi networks.
Use this at your own risk! ADE9X is copyright ScruffyDuck Software and respects the copyright and ownership of all the component parts. If you modify someones work then it is up to you to make sure you have permission.
Please report any issues etc in this forum. Please start a new thread and don't post error or other reports in this thread.