ADE9X feedback

[scruffyduck]

Hey Jon,
I have deleted the installation complete, i have deleted the registry entries and the files in the paperbasket.

Then i changed the country settings to UK, unpacked all to a directory. first run, scan, all without problems. Then end the program, change settings to german, start ADEX choose FSX and it hangs. Close ADEX, change settings to UK, start ADEX and it runs perfectly. I think, thats the last entries in the log file.
The problems with german settings are:

16:14:52:INFO_:
16:14:52 ====== BEG Program.Main =====
16:14:52:INFO_: Enable Visual Styles
16:14:52:INFO_: Check Single Instance
16:14:52:INFO_: Target Version: FSX
16:14:52 ====== BEG ADEUtil.TryUpdate =====
16:14:53:INFO_: No Update Available
16:14:53 ====== END ADEUtil.TryUpdate 0,491s =====
16:14:53:INFO_: Start Splashscreen
16:14:53:INFO_: New Mainform16:14:53 ====== BEG MainForm.Constructor =====
16:14:53:INFO_: ADE v01.42.08
16:14:53:INFO_: SDELib v04.03.10
16:14:53:INFO_: CommonLib v01.04.00
16:14:53:INFO_: Execute MainForm.initForm
16:14:55:INFO_: Execute MainForm.preLoadChecks
16:14:55:INFO_: Execute MainForm.testModelListForUnknown
16:14:55:INFO_: Execute MainForm.initSettings
16:14:55:INFO_: Log Level INFO_
16:14:56:INFO_: Execute MainForm.initHandlers
16:14:56 ====== BEG MainForm.modeChanged =====
16:14:56:INFO_: Pointer > Pointer
16:14:56 ====== END MainForm.modeChanged 0,006s =====
16:14:56:INFO_: Execute MainForm.initSignData
16:14:56:INFO_: Execute MainForm.initStockAirports
16:14:57:INFO_: Execute ADEUtil.LoadStockComList
16:14:57:ERROR: Exception Mainform.constructor
Die Eingabezeichenfolge hat das falsche Format.
bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
bei System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
bei System.Double.Parse(String s, NumberStyles style, NumberFormatInfo info)
bei ScruffyDuck.Flightsim.Types.FSComRecord..ctor(String data)
bei ScruffyDuck.AirportDesignEditor.Helpers.ADEUtil.LoadStockComList()
bei ScruffyDuck.AirportDesignEditor.MainForm.initStockAirports()
bei ScruffyDuck.AirportDesignEditor.MainForm..ctor()
16:14:59 ====== END MainForm.Constructor 6,185s =====

(I installed and tested it more times)

This error is reproducable.
Maybe reading the new ComList.dat?

Regards

Horst

Horst

Thank you for the feedback. I think you are correct that it is ComList.dat.

Tomorrow I will change the country settings to German on the development machine and see if I can replicate the problem

 

[scruffyduck]

Horst

Thank you for the feedback. I think you are correct that it is ComList.dat.

Tomorrow I will change the country settings to German on the development machine and see if I can replicate the problem

I have now replicated this problem and we will work on a fix. Thanks for all your help

EDIT

I believe this is now fixed and ready for testing

 

[gregloones]

Hey ADE team!

Testing ADE9 has been very exciting until now. What a huge step forward!

I have read the complete manual for v140 but still have a few questions. Excuse me if this has been asked before for earlier versions but I've never done anything for FSX, so I don't know if it's FS9 specific or not. I've got quite a lot of experience with AFCAD as a member of the MAIW team though.

1. Is there a night modus in ADE so the lights can be checked? I can't seem to find anything about it in the manual or I must be overlooking it.

2. The surface type of "Runway Links" and "Apron Links" is taken automatically from the underlying surface and can not be changed in ADE, opposed to AFCAD where you could. I know that FS9 does not draw any surface for these types of links but changing the surface type for them did have an impact.

Example 1: The runway is a tarmac one. The runway link automatically takes "TARMAC" as surface type. However, all the intersections from this runway will now initially be in tarmac. This is okay at position 2 in the screenshot but I would like to have a complete asphalt intersection at position 1 without the tarmac (black) portion. In AFCAD this could be achieved by dividing the runway link in different sections with a simple node and changing the surface of the runway link around position 1 to asphalt. In ADE this is not possible.

Example 2: The apron links automatically take concrete as surface, which sometimes results in a part of the tarmac taxiway to become concrete, which looks sloppy. In AFCAD this was avoided by changing the surface type of the apron link to tarmac, but can not be done in ADE.

In short: is there any way to work around these problems in ADE. If not, is it possible to allow the user to change the surface types of runway links and apron links?

Thank you for your time! I hope I don't annoy you too much with my I-could-do-this-in-AFCAD-and-can't-in-ADE9-questions

As I've said: ADE9 is a huge step forward and will be without any doubt the new standard tool!

Greg

 

[GHD]

is it possible to allow the user to change the surface types of runway links and apron links?

Go into Settings/Options and uncheck "Auto set Parking and Apron Link Surfaces":



Highlight the link and press <Enter> and you should be able to change the surface type.

 

[gregloones]

Excellent, thank you George! I remember that option from the manual now

Only the "lights" modus and surface type for the runway link left then

Greg

 

[FlyingMasterChef]

Excellent, thank you George! I remember that option from the manual now

Only the "lights" modus and surface type for the runway link left then

Greg

As for the lights, there is no way to do this as of yet in ADE. It is, however, on the to-do-list for upcoming version.



- Greg

 

[scruffyduck]

Runway links have no surface type I think. The problem may be related to the apron or taxi link going to the runway. There are others more expert than me in fixing these problems but I think it might involve adding a node on the edge of the runway and changing the surface type to that of the runway.

Jim or George are better than me for this sort of thing.

As for the night mode, as Greg says it is not in the current releases. However it should be part of the release after this one (1.50). The next release is 1.45 and is basically what you see now in the beta (hopefully with the bugs ironed out)

 

[gregloones]

I see with you mean with adding a node on the edge of the runway, Jon, but then I'd lose the "fillets" as you call them in the manual...

Because you can change the runway link surface in AFCAD, I assumed it would also be possible to make such an option in ADE (it's grayed out now), but I guess it's more complicated than that

Except the fact that ADE9X doesn't like my Dutch country settings (even after a fresh install as per your instructions), everything seems to work like a charm! Well done!

Greg

 

[scruffyduck]

I see with you mean with adding a node on the edge of the runway, Jon, but then I'd lose the "fillets" as you call them in the manual...

Because you can change the runway link surface in AFCAD, I assumed it would also be possible to make such an option in ADE (it's grayed out now), but I guess it's more complicated than that

Except the fact that ADE9X doesn't like my Dutch country settings (even after a fresh install as per your instructions), everything seems to work like a charm! Well done!

Greg

Thanks for the feedback

The country setting bug (one of them anyway) should be fixed in the next release.

 

[robystar]

Quick question.
What do you mean by Dutch country settings? or is that only applicable to the FS9/FSX beta?

 

[robystar]

Forget it. Too hasty. Sorry.
Couldn't delete it.

 

[gregloones]

Quick question.
What do you mean by Dutch country settings? or is that only applicable to the FS9/FSX beta?

I meant the country setting in Windows, which is "Dutch (Belgium)" for me. This causes problems in ADE9X Beta as has been explained by Jon.

Greg

 

[robystar]

Thanks Greg, but as I said, I was too hasty.
It was not doubledutch to me.

 

[gregloones]

Geen probleem.

I thought you'd made a double post, but you wanted me to disregard the question... misunderstanding

Greg

 

[gregloones]

Thought I'd let you know that country settings are no longer an issue in RC1

Secondly, I don't know if anyone reported this before, so:

Opening an AFX bgl in ADE9 worked without any problems, but ADE9 would not always load stock data when asked via the Tools menu. With some bgl's it gave a "Stock Airfield not found" error, and then this:

I have found out that ADE9 doesn't like the AFX excludes. When I remove all excludes in an AFX bgl with AFX first, ADE9 loads the stock data without problems.

Greg

 

[jvile]

Thought I'd let you know that country settings are no longer an issue in RC1

Secondly, I don't know if anyone reported this before, so:

Opening an AFX bgl in ADE9 worked without any problems, but ADE9 would not always load stock data when asked via the Tools menu. With some bgl's it gave a "Stock Airfield not found" error, and then this:

I have found out that ADE9 doesn't like the AFX excludes. When I remove all excludes in an AFX bgl with AFX first, ADE9 loads the stock data without problems.

Greg

Greg

AFX does not use the SDK compiler and also uses non-compliant type incomplete madeup sceneryobject codes/exclusions.

ADE9 is designed to open a true FS9 AFCAD (Lee Swordy's utility) airport but we cannot guarantee how much ADE9 can do with a AFX FS9. The AFX FS9 is not AFCAD and in some cases you may be better off starting out with a stock airport using ADE9 if a true AFCAD type airport does not exist.

 

[scruffyduck]

Thought I'd let you know that country settings are no longer an issue in RC1

Secondly, I don't know if anyone reported this before, so:

Opening an AFX bgl in ADE9 worked without any problems, but ADE9 would not always load stock data when asked via the Tools menu. With some bgl's it gave a "Stock Airfield not found" error, and then this:

I have found out that ADE9 doesn't like the AFX excludes. When I remove all excludes in an AFX bgl with AFX first, ADE9 loads the stock data without problems.

Greg

Greg

Could you please email me (jon AT scruffyduck.co.uk) any examples of the AFX bgl files that cause these problems? I will then see what is going on.

As Jim says AFX uses its own compiler and that can give us problems. Having said that we should be able to deal with them


Thanks

 

[gregloones]

Thanks guys. I thought it had something to do with AFX' own compiler but wanted to let you know anyway.

I presume that a lot of our users will try to open and alter previously released MAIW AFX files with ADE9, as they could not do so in the past with AFCAD. I wanted to know if that gave any problems before people start asking us questions

Jon, I will send you a couple AFX files with and without excludes for an upcoming package so you can have a look.

Greg

 

[scruffyduck]

Thanks guys. I thought it had something to do with AFX' own compiler but wanted to let you know anyway.

I presume that a lot of our users will try to open and alter previously released MAIW AFX files with ADE9, as they could not do so in the past with AFCAD. I wanted to know if that gave any problems before people start asking us questions

Jon, I will send you a couple AFX files with and without excludes for an upcoming package so you can have a look.

Greg

For sure they will and that is just the kind of testing we need to sort any issues out now

 

[scruffyduck]

I have found it and it is a problem in ADE which I have now fixed. As Greg suggests it is the presence of Exclusion Rectangles in the file before the airport data which triggered the problem.