-
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 Version 0.0.97
- Thread starter gadgets
- Start date
- Messages
- 12,244
- Country
Hi Don,
I have a problem with this version.
The ground polygon seems to be distorted on entry to the GP editor and the result in FSX has kinks in the cross-hatching.
Further, on compile, it insists that three polylines need to be edited when no changes have been made.
Problem solved, one needs to use "Reset" after moving the vertices of a polygon.
I have a problem with this version.
The ground polygon seems to be distorted on entry to the GP editor and the result in FSX has kinks in the cross-hatching.
Further, on compile, it insists that three polylines need to be edited when no changes have been made.
Problem solved, one needs to use "Reset" after moving the vertices of a polygon.
Last edited:
Glad you found the solution, George.
On a crosshatched poly, Reset is a good idea when any vertex has moved (other then as part of the entire poly). Otherwise, ADE_GP will stretch the texture. Such changes would likely not be noticeable with a uniform texture.
Incidentally, ADE_GP only "demands" a poly or line be edited prior to compile if it detects something has changed - a vertex has been added/deleted/moved in such a manner that the editor is unable to handle the matter securely on its own. (Perhaps you inadvertently moved something.) It will continue to "demand" until the problem object is submitted to the editor if you don't accept the offer to edit immediately.
Don
On a crosshatched poly, Reset is a good idea when any vertex has moved (other then as part of the entire poly). Otherwise, ADE_GP will stretch the texture. Such changes would likely not be noticeable with a uniform texture.
Incidentally, ADE_GP only "demands" a poly or line be edited prior to compile if it detects something has changed - a vertex has been added/deleted/moved in such a manner that the editor is unable to handle the matter securely on its own. (Perhaps you inadvertently moved something.) It will continue to "demand" until the problem object is submitted to the editor if you don't accept the offer to edit immediately.
Don
- Messages
- 12,244
- Country
I think the "un-reset" polygon caused the demand to re-edit the lines. Having reset the poly, it no longer insists on editing the lines.
The "demand" that the object be edited doesn't mean you must change something. Just opening the object in the editor is often enough. (Certain operations require the editor be opened.) If you are happy with the displayed object, simply close the editor.
"Reset" counts as an edit; hence ADE_GP is "happy".
Don
"Reset" counts as an edit; hence ADE_GP is "happy".
Don
- Messages
- 12,244
- Country
I don't that applies in this instance.
This is the "demand" pop-up:
This is the "demanded" line and the lines which have just been edited:
I had not touched the "demanded" line since yesterday.
That area of code is very complex, George. Without repeatable symptoms, my chances of finding what's causing this - if it's in ADE_GP - is less than nil.
There is only one thing that can cause this message - a vertex that has not been handled texture-wise - normally because it has been added or because it has been moved relative to other vertices in the object and ADE_GP can't automatically adjust UVs Once the object is opened in the editor, the issue should go away.
If you do manage to find repeatable symptoms. I'll investigate.
Don
There is only one thing that can cause this message - a vertex that has not been handled texture-wise - normally because it has been added or because it has been moved relative to other vertices in the object and ADE_GP can't automatically adjust UVs Once the object is opened in the editor, the issue should go away.
If you do manage to find repeatable symptoms. I'll investigate.
Don
