• 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:SE Two small issues with 1.75

Don
I've downloaded 2.2.0.7 (even if the GP editor window still reports 2.2.0.6) and still no joy.
The LICA ad4 file I've sent to you compiles with no errors, but no GPs are visible.
 
It seems the file I uploaded last evening did not include the updated .dll.

I have just uploaded a new fileset. Please download and try it. Both the GP Editor and the Windows Properties function should report 2.2.07.

I have confirmed that I see all you GPs under FSX on my system.,

Don
 
Don, no luck.
Compiles without errors, but I don't see the gps created with 1.70, nor the new one I created from scratch in 1.75.
I use the FSX boxed SDK, maybe it has something to do with this problem?

Edit: maybe a clue. The _GP.bgl created with 1.75 is more than 1MB (and no GPs are visible). The one created with 1.70 is about 320KB.
 
Given the file size, it appears that ADE is asking for compile in P3D v3/4 mode. The files generated on my system are attached.

Don
 

Attachments

So everything should lead to a faulty ADE install?
I select "FSX" each time I start ADE.
Maybe I should try to reinstall.
 
Reinstalled and now I'm getting this error. This kind of error generally occurs when I edit GPs with both ADE versions. I see 1.75 adds a *|default extension to the texture name, which does not occur in 1.70.
Maybe now 1.75 can't compile 1.70 GPs.

System.ArgumentOutOfRangeException: Index non compreso nell'intervallo. Richiesto valore non negativo e minore della dimensione dell'insieme.
Nome parametro: index
in System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
in System.ThrowHelper.ThrowArgumentOutOfRangeException()
in System.Collections.Generic.List`1.get_Item(Int32 index)
in ADE_GroundPolys.Generate_BGL.CopyTextures(String sPath)
in ADE_GroundPolys.Generate_BGL.btnGo_Click(Object sender, EventArgs e)
in System.Windows.Forms.Control.OnClick(EventArgs e)
in System.Windows.Forms.Button.OnClick(EventArgs e)
in System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
in System.Windows.Forms.Control.WndProc(Message& m)
in System.Windows.Forms.ButtonBase.WndProc(Message& m)
in System.Windows.Forms.Button.WndProc(Message& m)
in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
There's no such thing as 1.70 or 1.75 GPs within ADE (but, it's possible there's some corruption).

I see 1.75 adds a *|default extension to the texture name, which does not occur in 1.70.
Click to expand...
It's not clear to what you are referring.

Curiously, no one else is reporting such an error, nor am I experiencing it. Rather than me having to investigate a "generally occurs" type of error, perhaps you could give me precise instructions regarding how to reliably duplicate the situation and send me whatever files are involved.

Don
 
Don
Sorry for some difficulty to explain the previous issue, english is not my mother tongue.
Anyway, if you look at the pic below:



The first GP has been created from scratch in ADE 1.75 and has the *|default extension in the texture name.
The other GPs in the list come from ADE 1.70.
 
I have no idea where that "\Default" suffix comes from. I very much doubt it was added by ADE-GP, nor does it appear in the .ad4 file you sent me earlier.

I can only conclude that your .ad4 database - at least the ADE-GP part of it - has somehow been corrupted in one of the transitions. The compilation of GPs for FSX is identical in both versions of ADE-GP. (The error I fixed yesterday is the result of a change made in one of my "standard" files to accommodate anther application.)

As for the exception, since I'm not experiencing it and no one else is reporting it, there seems little point in me taking "stabs in the dark" trying to find it. What I need from you in order to address it are the files you are using when the error occurs and a reliable way to force that error - and it seems to me your English is plenty good enough to do that. Without files and instructions, I'd be wasting my time.

Back to the "\Default" suffix, I suggest you delete that GP (in 1.75), re-enter it and try again.

Don
 
Yes, I'm monitoring that thread. But, there is no indication where the suffix came from.

I have just done a complete scan of the ADE-GP source code. The character string "\Default" does not appear anywhere, suggesting the texture names are not being modified by ADE-GP.

Don
 
There is another user currently experiencing this problem, i.e., the "|Default" suffix. He is moving up from 1.70.

This seems to have become an issue suddenly. I wonder if there's something in the update process that could be contributing. Jon do you have your ears on?

Don
 
I just realized the "|Default" suffix is Jon's way of displaying both texture and material in one column. I have no problem compiling it in any mode. It does, however, seem to cause an issue with FSX. I'll investigate.

Don
 
Updated and getting this error. Should I get some up-to-date runtime libraries?

System.BadImageFormatException: Impossibile caricare il file o l'assembly 'ASToFra.Coordinates, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' o una delle relative dipendenze. L'assembly non può essere caricato perché è stato creato da un runtime più recente di quello attualmente caricato.
Nome file: 'ASToFra.Coordinates, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
in ADE_GroundPolys.Generate_BGL..ctor()
in ADE_GroundPolys.Generate_BGL.Open(String[]& data_)
in ADE_GroundPolys.ADE_GroundPolys.GP_Compile(DataObject data_)
in ScruffyDuck.AirportDesignEditor.Helpers.CompilerServices.CompileCustomGroundObjects(String fileName)
in ScruffyDuck.AirportDesignEditor.MainForm.CompileCustomGroupPolys()
in ScruffyDuck.AirportDesignEditor.MainForm.CompileProject()
in ScruffyDuck.AirportDesignEditor.MainForm.OnCompileOptionsStatusChanged(Boolean compile, Boolean statusChanged)
in ScruffyDuck.AirportDesignEditor.Helpers.ProjectPropertiesCompileOptions.OnCompileClick(Object sender, EventArgs e)
in System.Windows.Forms.Control.OnClick(EventArgs e)
in System.Windows.Forms.Button.OnClick(EventArgs e)
in System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
in System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
in System.Windows.Forms.Control.WndProc(Message& m)
in System.Windows.Forms.ButtonBase.WndProc(Message& m)
in System.Windows.Forms.Button.WndProc(Message& m)
in System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
in System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
in System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
 
You must log in or register to reply here.
Back
Top