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

ADE-gp 0.0.63

robystar

robystar

Messages
5,214
Morning Don,

Re: v 62 and 63: I had not checked anymore whether the editor worked OK for polygons in these last two versions because I was busy with the lines. But now I tried (with both versions) to make a polygon and I get the following error upon compiling:

63gpeditorerror.jpg


Haven't the faintest what it means and maybe I screwed up something although I only added a polygon textured with dark asphalt.
Would somebody else please check this as well and confirm (or not)?

Re: v 63: Don, you said the background color could be changed with a new button and the size of textures could be doubled or halved. But is that implemented already because I can find nothing.

Roby
 
Works for me

I have a project I've been working on as I've followed the threads. Just added a new dark asphalt poly with 0.0.63 and it compiles normally.

I believe I've attached the files currently edited as well as a screenshot of the ADE editing page with an arrow showing the new dark asphalt gp poly.

It displays appropriately in FSX

win7 64

Gary
 

Attachments

Hi,

And thanks.
Funny though. In the meantime i have tried it again several times and always with the same result.
Moreover, I now have still more problems:

- Tried to change a gp_line with a backwidth of 25.0 to 0.25: program hangs when the pop up window "maximum zoom exceeded" appears:

63maxzoomexceeded.jpg


- Tried it again after having closed ADE with the program manager: clicking OK after having been able to change the backing width, but no response and the program hangs.

63oknotclosinghangs.jpg


- One more try to get ADE and the GP-editor going again clicking various times on 'close program': ADE crashes (hope Jon received error report).

- Open ADE again but see this crazy entry in the recent files list. Click on it and NSTU opens:

unintelligible.jpg


Wish I knew what is going on.
 
Last edited:
Wish I knew what is going on.
Click to expand...

So do I.

That file name is the file created when ADE crashes. I will check to see if this is a bug in ADE since it should not treat this file as a recently saved file.

As to the other issues I posted a separate thread with an exception report that you sent me
 
Hi Jon,

I think I can now add some extra info that may shed more light on the issues.
- the first few times I tried changing the gp line ADE was connected to FSX!
- I managed to 'unfreeze' the editor the way Parkinson patients would do it and I disconnected ADE from FSX and tried again. This time I could delete the line, make a new one and it compiled and showed as it should.
- I repeated the operation while ADE was connected to FSX and I had the same problem again. Disconnecting solved the problem.
- Polygons still give me the error I showed earlier on. Deleting the polygon and compile is done without errors.

PS: the first time I changed the gp line and ADE /GP-editor crashed I had inadvertently set the backing width to 0.05 instead of 0.25. Do not know if that makes a difference?

Update: I found out that when I resize the polygon so that the texture is bigger than the standard 6.10 x 6.10 (for instance for the dark asphalt) I no longer receive the error message. ADE compiles fine and the textured polygon shows up in FSX.

Another update: it does not matter if you resize to make the texture bigger or smaller, as long as you resize, it works.
 
Last edited:
So, Roby, are you reporting a link between crashes and ADE being connected to FSX?

On first impressions I cannot think of any way that being connected to FSX would affect the GP Editor. However I think you are saying that you cannot change the line in ADE when connected to FSX?
 
Roby, the error mesage you first reported below is generated by BGLC_9. It "didn't like" something in the data. The message tells me where in the file the error is and the general nature of the error but, to know the specifics, I need the ADE_GP.asm file that generated the error or your ADE file to compile.

As for the new features, they will be in the next release. I was simply advising you that I had been able to implement them.

I'll investigate the max zoom crash. However, even if it is a result of a problem in ADE_GP (it's really an out-of-memory message), a 25m backing for a 0.15m-wide line seems unusual. And, with the segment lengths involved, it would make the line much wider than either of its segments.

I have a project I've been working on as I've followed the threads. Just added a new dark asphalt poly with 0.0.63 and it compiles normally.
Click to expand...
Gary, just to be sure I understand, are you being supportive or am I supposed to find sometime in those files. In either case, thanks.

Don
 
I am not sure Jon. It is erratic behavior (not crashing but 'hanging'). Sometimes the gp-editor hangs when ADE is connected to FSX and sometimes it does not but takes a long while before the OK button executes the command. When ADE is not connected the editor does not show that behavior.

I can confirm what George experiences as well.
 
So sorry but here is another update that may help.
I managed to make a new polygon without the GP-editor creating the error message when setting the layer to 45 instead of the standard 40.
 

Attachments

robystar said:
I am not sure Jon. It is erratic behavior (not crashing but 'hanging'). Sometimes the gp-editor hangs when ADE is connected to FSX and sometimes it does not but takes a long while before the OK button executes the command. When ADE is not connected the editor does not show that behavior.

I can confirm what George experiences as well.
Click to expand...

Can I confirm whether this is caused when FSX is running at the same time as ADE or just when ADE is connected. I can understand perhaps the former as being a resources issue.
 
So sorry but here is another update that may help.
I managed to make a new polygon without the GP-editor creating the error message when setting the layer to 45 instead of the standard 40.
Click to expand...
Roby, does this file cause a crash for you? It doesn't for me.

What I need is either a ADE_GP.asm file that causes the error message or a ADE file which, when compiled, causes the error.

Don
 
Jon, the hanging or freezing (or whatever you call it) of the editor occurs when both ADE and FSX are running but does not occur when both are not connected through UIPC. If it were a matter of lack of resources or memory, it would have occurred in previous versions of ADE and ADE-GP as well, don't you think?
 
robystar said:
Jon, the hanging or freezing (or whatever you call it) of the editor occurs when both ADE and FSX are running. If it were a matter of lack of resources or memory, it would have occurred in previous versions of ADE and ADE-GP as well, don't you think?
Click to expand...

Well that would depend on whether any changes made by Don are affecting the reources needed by the editor.
 
Sorry Don, I sent you the asm file when the editor did not throw an exception.
In the other thread I sent one when it did.
 
As the one in the other thread was for segmented lines as per George's issue, here is the one which caused an error message when adding a polygon textured with dark asphalt.
 

Attachments

Roby, time to "reset".

You have reported two errors today:
  • a compiler error (first report above) and
  • an editor error (Maximum zoom exceeded).
The .asm file I was asking for was the one that caused the COMPILER error. For the EDITOR error, I need the ADE file with instructions.

Now, the .asm file you sent does, if fact, cause the compiler error (though I don't know why, yet). But, I still need your ADE file to investigate the editor maximum zoom exceeded issue.

Don
 
Hi Don,

Yes, I know it is time for resetting but just wanted to let you know that both George's patterned lines as well as my polygon problem are gone when setting their layers at 45!
 
just wanted to let you know that both George's patterned lines as well as my polygon problem are gone when setting their layers at 45!
Click to expand...
It's not clear how George's patterned line problem could be related to the .asm file. But, in any case, the mystery about your compiler crash is now solved.

It appears there are internal limits to the size of each section in the .asm file - even though 32-bit addressing is used - and your .asm exceed that limit. By changing the layer specification, you re-adjusted the file back within limits.

This is something I'll have to fix in the compiler. In the meantime, if you delete the "smiling face" (which includes a very large number of GP objects), you should be able to compile without this error.

Regarding the ADE file you sent, which line is it that caused the maximum zoom exceeded issue?

Don
 
It is not a line, Don, it is a polygon.
It is the gp poly the ILS glideslope of rwy 05 points to.
Lost my face:). See what that brings.
Oops, sorry you wanted to know which line brought on the maximum zoom exceed. It was the orange colored one inside the red hold short circle on the apron ->

63maxzoomexceeded2.jpg
 
Last edited:
You must log in or register to reply here.
Back
Top