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

FSX ADE suddenly stops compiling

C

Craig

Messages
27
Country
us-florida
I suddenly started getting this error, but any change I would make would compile correctly and would show up in my airport, so I didn't pay too close attention to it. Now, I get this error and nothing compiles and ADE crashes. I have done a complete uninstall/reinstall and cleared the registry with no luck. The only recent change has been I am using a trial version of the ProKey. This seems to be when my problems started, but I couldn't be sure. Any ideas would be appreciated!

ADE 1.70.6029

System.ArgumentException: Illegal characters in path.
at System.IO.Path.CheckInvalidPathChars(String path)
at System.IO.Path.GetFileName(String path)
at ADE_GroundPolys.Generate_ASM.btnGo_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
You are using an obsolete version of both ADE and ADE-GP. My "guess" is that ADE-GP can't find the required compiler.

Please update to ADE 1.71 and install ADE-GP 2.2.09 (released just a few days ago to address a problem when compiling for FSX - available from several recent posts in this forum and from http://stuff4fs.com).

In the unlikely event the problem persists after that, let me know and I'll investigate further.

Don
 
Updated to ADE 1.75 and updated to GP 2.2.09. Now ADE freezes after compiling. I can't even take a screen shot. I was just starting to get the hang of this....
 
Craig, others are not having such difficulty, suggesting a local configuration issue. Try ADE 1.75 by itself. (It includes ADE-GP 2.2.06, which has been in general use for a couple of months.) Your GPs may not display in FSX, but if you are unable to compile, then you've definitely got a local issue to find and resolve.

Don
 
Craig, others are not having such difficulty, suggesting a local configuration issue. Try ADE 1.75 by itself. (It includes ADE-GP 2.2.06, which has been in general use for a couple of months.) Your GPs may not display in FSX, but if you are unable to compile, then you've definitely got a local issue to find and resolve.

Don
 
This is what I end up with. Like I said, everything was going great, then this. Is there an issue with using the same paths to FSX even though all of the prompts are looking for P3D during the initial installation? Thanks for your quick replies!

upload_2017-11-13_17-14-47.png
 

Attachments

  • upload_2017-11-13_17-13-14.png
    upload_2017-11-13_17-13-14.png
    332 KB · Views: 404
If you are compiling for FSX, you must start ADE in FSX mode. If for P3D, then ADE must be started in P3D mode. You cannot use FSX compilers, etc for P3D (other than P3Dv1) or vice versa.

It looks like ADE is in P3D mode, since ADE_GP error message has to do with missing .mdl files - which would not be created in FSX mode.

Don
 
How do I select my mode?
Click to expand...
It's the first "question" ADE asks when you start it.

I've got to go our shortly. I don't think this problem is due to an ADE-GP issue, so I suggest someone very familiar with ADE jump in.

Don
 
Thanks Don for your help. I guess I don't have a clue. I don't get a question when ADE starts. I get a quick loading splash screen and the program starts in P4 mode.
 
the program starts in P4 mode.
Click to expand...
which explains the error message.

When you first start ADE you get a small dialog with a single combobox that allows you to select the target FS version. When that shows up, select FSX.

Don
 
OK. I found my solution. The link is below. I had to make a Global.ini file in order to see what versions I could select.

You can force ADE to display a list of FS Versions.

If you want to try forcing ADE to display missing versions then go to the ADE main installation folder and look for Global.ini Open it in a text editor you will see something like this:

[TARGET]
Version=P33
[IMPORT]
GpTextures=True
ListerSettings=True

If you can't find it - which is possible if there are no FS installations to find then you will need to create it

[TARGET]
ShowAll=True

Now save global.ini and try to run ADE. If it works then you will see a version selector that shows all the versions:

upload_2016-12-3_6-57-36-png.31814


http://www.fsdeveloper.com/forum/th...ter-without-fsx-installed.438858/#post-759489

Thanks again, Don
 
ADE searches for installed versions of FS when it starts. If no selector is displayed then ADE is only finding one version. Either you have a registry problem with. FSX or it is not installed. In any case the fix you are issuing is a sticking plaster covering up the real problem. You should try and fix the underlying issue.
 
Figured out my registry problem, and now ADE recognizes FSX when loading. Also realized I didn't have all of the GP updates, and now that has been rectified as well. If you need to delete this thread, please do, as I do not want to mislead anyone. Thanks again for all of your patience and fast responses!
 
We don't delete threads since there is always something to be learned from then. :)
 
You must log in or register to reply here.
Back
Top