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

ADE9X feedback

Ok, thanks. Clear to me, but...
How do I revert to the last no bug version if this beta version gives trouble?
Can I just use one of the 1.40 update version zip files to restore to an earlier state?
 
robystar said:
Ok, thanks. Clear to me, but...
How do I revert to the last no bug version if this beta version gives trouble?
Can I just use one of the 1.40 update version zip files to restore to an earlier state?
Click to expand...

We do not like to go backwards after a update. Continue to use your ADE version until ADE9X is made public. ADE9X has been tested by over 20 beta team members. We are not a one man show like other utility's and the beta teams have spent several months working with both FS9 and FSX airports.

There are some airports that have already been made with ADE9X for both FS9 and FSX that are ready for upload when the beta goes public. Some of these airports are even highend 3rd party payware since we stress ADE to the extreme for testing purposes.
 
I know that the program is not a one man show, Jim (although you do your best :)).
I'll stick to my present version for the time being.

Thanks
 
hgschnell said:
its me again

I tried to change settings (altitudes from meter to ft), but I get this error message:

Der Wert 30 ist für Value ungültig. Value sollte zwischen 'Minimum' und 'Maximum' liegen.
Parametername: Value

bei System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
bei ScruffyDuck.AirportDesignEditor.ProgramOptions..ctor(Ini settings)
bei ScruffyDuck.AirportDesignEditor.MainForm.optionsMenuItem_Click(Object sender, EventArgs e)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

and ADE shuts down ...
Click to expand...

Can you please email me the file called log_200907.log that will be in either the FS9 or FSX sub-folder depending on which version you are using? jon AT fsdeveloper.com
 
robystar said:
Ok, thanks. Clear to me, but...
How do I revert to the last no bug version if this beta version gives trouble?
Can I just use one of the 1.40 update version zip files to restore to an earlier state?
Click to expand...

Not sure what you mean. ADE 1.42 should not be installed over any existing versions as per the readme. If you have done this then you will need to installed 1.40 again. You can't down-date a version by using files from a previous version.

Also you need to be aware that project files created in 1.42 cannot be read in 1.40 which is why the readme says don't use ADE 1.40 project files in 1.42.
 
Jon,

I thought it was clear to me, but now you have me confused.
I have not yet downloaded the FSX/FS9 version as I was wondering whether it was useful to download it if you do not use FS9 anymore.
But if you say that all my 1.40 version 'work' files will become unreadable (or is it the other way around?) what do I do with all the experimental files that I kept in the 'work' folder but never compiled because they are not finsihed yet?
And, of course, because your program keeps evolving and getting better still, I want to keep update but am at a loss whether to install this new FSX/FS9 version yes or no!
 
Jon:

In a beta version (option FS9) I load a FSX project called SAZB_ADE_VM.ade.
When I tray to compile ocurrs a error:

Referencia a objeto no establecida como instancia de un objeto.

en ScruffyDuck.Flightsim.Scenery.SceneryObject.Waypoint.Code(FSVersion compileVersion, FileType fileType)
en ScruffyDuck.Flightsim.Scenery.SceneryObject.Airport.Code(FSVersion compileVersion, FileType fileType)
en ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.FullCode(FSVersion compileVersion, FileType fileType)
en ScruffyDuck.AirportDesignEditor.MainForm.compileFS9()
en ScruffyDuck.AirportDesignEditor.MainForm.transferAirportMenuItem_Click(Object sender, EventArgs e)
en System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
en System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
en System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
en System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
en System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
en System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
en System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
en System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
en System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
en System.Windows.Forms.Control.WndProc(Message& m)
en System.Windows.Forms.ScrollableControl.WndProc(Message& m)
en System.Windows.Forms.ToolStrip.WndProc(Message& m)
en System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Best Regards

carlos
 

Attachments

robystar said:
Jon,

I thought it was clear to me, but now you have me confused.
I have not yet downloaded the FSX/FS9 version as I was wondering whether it was useful to download it if you do not use FS9 anymore.
But if you say that all my 1.40 version 'work' files will become unreadable (or is it the other way around?) what do I do with all the experimental files that I kept in the 'work' folder but never compiled because they are not finsihed yet?
And, of course, because your program keeps evolving and getting better still, I want to keep update but am at a loss whether to install this new FSX/FS9 version yes or no!
Click to expand...


OK we are confusing each other. To answer your question - don't install the beta :)
 
carlos maida said:
Jon:

In a beta version (option FS9) I load a FSX project called SAZB_ADE_VM.ade.
When I tray to compile ocurrs a error:

Referencia a objeto no establecida como instancia de un objeto.

en ScruffyDuck.Flightsim.Scenery.SceneryObject.Waypoint.Code(FSVersion compileVersion, FileType fileType)
en ScruffyDuck.Flightsim.Scenery.SceneryObject.Airport.Code(FSVersion compileVersion, FileType fileType)
en ScruffyDuck.Flightsim.Scenery.SceneryFile.SceneryFile.FullCode(FSVersion compileVersion, FileType fileType)
en ScruffyDuck.AirportDesignEditor.MainForm.compileFS9()
en ScruffyDuck.AirportDesignEditor.MainForm.transferAirportMenuItem_Click(Object sender, EventArgs e)
en System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
en System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
en System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
en System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
en System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
en System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
en System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
en System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
en System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
en System.Windows.Forms.Control.WndProc(Message& m)
en System.Windows.Forms.ScrollableControl.WndProc(Message& m)
en System.Windows.Forms.ToolStrip.WndProc(Message& m)
en System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Best Regards

carlos
Click to expand...

Hi Carlos

Thank you for the report. Please make a zip of your project file and email it to me - jon AT fsdeveloper.com
 
scruffyduck said:
Please change your settings to the UK or US. Then run ADE for each version of FS that you have. Once complete you can close ADE and change your country settings back. It should then work fine.
Click to expand...
Hey Jon, it don't works.
First I changed country settings to UK, all works fine. Then I closed ADE, changed country settings to German, started ADE - and it hangs.
It's hanging while frmsplash shows "Stock Airports".

Regards

Horst

PS: The older version 1.40.09 still works fine with German country settings.
 
scruffyduck said:
Can you please email me the file called log_200907.log that will be in either the FS9 or FSX sub-folder depending on which version you are using? jon AT fsdeveloper.com
Click to expand...

when I installed ADE9x I had the wrong country settings. So I got "3,0" instead of "3.0" as value for message display time. After editing settings all works fine till now ...
 

Attachments

Just verifying...an ADE file created with the beta will NOT work or load in the production version of ADE?

I ask because in my testing phase of the beta, using a backup copy of my NKL project of course, I have put in about 13 hours of work. IE.... 13 hours of NEW and changed/updated stuff to my NKL.. The thought of it being lost if I have to go back to the production version for some reason would really suck!!!! hehe

As of yet, I have had NO problems with the beta version and my fsx NKL project. Hopefully, I can just keep using it and when it becomes production, all will be well.

- Greg
 
SpectroPro said:
Just verifying...an ADE file created with the beta will NOT work or load in the production version of ADE?

I ask because in my testing phase of the beta, using a backup copy of my NKL project of course, I have put in about 13 hours of work. IE.... 13 hours of NEW and changed/updated stuff to my NKL.. The thought of it being lost if I have to go back to the production version for some reason would really suck!!!! hehe

As of yet, I have had NO problems with the beta version and my fsx NKL project. Hopefully, I can just keep using it and when it becomes production, all will be well.

- Greg
Click to expand...

No - you can't go back. ADE project files are generally not backwards compatible.
 
Ok...well, as long as the beta files will be forward compatible...I am happy. :) I like the beta so far...yes, I am using the FSX part, thus, not testing the new goodies, but really like the colored taxiway change...that is nice.

I still have the other version should I have to use it...but I hope that won't be the case..as I will lose a days work at minimum.

- Greg
 
SpectroPro said:
Ok...well, as long as the beta files will be forward compatible...I am happy. :) I like the beta so far...yes, I am using the FSX part, thus, not testing the new goodies, but really like the colored taxiway change...that is nice.

I still have the other version should I have to use it...but I hope that won't be the case..as I will lose a days work at minimum.

- Greg
Click to expand...

Project files are expected to be forward compatible
 
German settings

Hey Jon,

I have changed the country settings to UK, then started ADEX. The scan was good, ADEX started, I ended.

Then I rechanged the country settings to German, started ADEX and it hangs.

I've added the logfile.

Regards

Horst

PS.: I've read the sticky. I'm waiting until an update.
 

Attachments

Last edited:
FlyEF said:
Hey Jon,

I have changed the country settings to UK, then started ADEX. The scan was good, ADEX started, I ended.

Then I rechanged the country settings to German, started ADEX and it hangs.

I've added the logfile.

Regards

Horst

PS.: I've read the sticky. I'm waiting until an update.
Click to expand...



Did you delete the ADE9X installation, then change the country settings and then install ADE9X again and run it? If you don't do this some files can get left in an unstable state.

Also looking at the log the last time you opened ADE you loaded a file and then closed ADE without an error so please can you tell me a bit more about what happened.
 
Last edited:
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
 
You must log in or register to reply here.
Back
Top