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

Gp 083

Messages
100
Country
unitedkingdom
Just tried the latest upgrade, the good news is that I can now compile the AFD file, the bad news is that there are no GP polys. When I then try to edit the polys and lines I get this a list of errors as long as your arm. I'll send the log separately



Uploaded with ImageShack.us

Norman
 
That's my fault, Norman. It's a change I made while investigating the "missing poly" issue in another post. I'll send Jon a new release with that fixed shortly.

BTW, it only affects compile.

Don
 
We are only able to update once per day ;)
 
While the compiler error Norman discovered earlier was related to the change I made yesterday while investigating another issue, that change was not at fault. (That change had, in fact, been removed.)

While a great deal of attention has been paid to the assignment of line patterns, somewhat less attention has been paid to removal of them. And, it turns out, should a line pattern have been removed - even temporarily - it left the line in a state that would "upset" the compiler. (It appears to have been such a line that caused Norman's issue.) While you could have detected something was wrong on subsequent edits of the line, you would have had to look hard to see it.

Tomorrow's release of ADE_GP will contain not only a fix for that problem, it will also include some code in the GP Editor that will automatically detect and rectify the issue on lines where it exists. Unfortunately, I was not able to apply the latter to the "silent edit" that precedes the compile (so that all such errors would have been corrected automatically), but the compiler will now tolerate the situation.

So, should your compiled GP Lines not be properly textured, all you need do (with or following tomorrow's release) is re-edit the line, close the GP editor with OK and recompile.
 
The error in the post above plus two was after adding a completely new GP line.
 
The error in the post above plus two was after adding a completely new GP line
Since the error is in line 84 of the .asm file, apparently, there's other data in the file. So, the error may have nothing to do with the new line you added. (A file that compiled with versions previous to 0.0.83 will not necessarily compile with 0.0.83.) Please either wait for tomorrow's release or send my your AD3 file so I can confirm that there's not another issue lurking.

This issue is data dependent. The error message you see is generated by BGLC9 ("parroted" by ADE_GP) and isn't much help.

Don
 
Back
Top