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

Adex 4932

ADE calculates the number of vertices in an arc with the formula:

Vertex Count * Swept Arc / 360

Where vertex count is the value you set. The calculation is not exact of course because it is converting a decimal to an integer and then ensuring there is a vertex at each end of the arc.
 
Norman, I deleted the 200-vertex objects leaving the 40-vertex ones - which compile without error. Except when the object fills the entire screen (in FSX), my eye cannot discern the segmented edges. And even then, I've got to look very critically.

200 vertices in a larger object will be OK. But, for an 8' circle, the resultant triangles have at least one side only 1.5 inches long. The other two sides could be up to 8' long with a subtended angle of only a fraction of a degree - in some cases only a tiny fraction of a degree. (Triangulation takes place between vertices, not from the center). With these length/angles, even the curvature of the earth plays a role.

To avoid other issues, distances/differences of less than 1mm are ignored. From my tests on your airport, I know it is the first triangle that causes the grief. What this tells me is that the width of that triangle (due to the subtended angle) is less than 1 mm., i.e., effectively 0. That's a straight line, not a triangle, so the process fails.

I'll leave it to you to determine just how many vertices you can use before the ADE_GP compiler "gives up", but 200 is definitely "on the wrong side" for an 8' circle.

Don
 
Norman, for the moment, don't bother to change the 200.

I have (perhaps only temporarily) tightened the tolerance for triangulation from 1 mm to 0.1 mm. The original 1mm was an arbitrary value which solved the earlier problems.

I have test-compiled the airports with which there were earlier triangulation-based issues and all still seem to be OK with the revised tolerance. It also now triangulates your 200-vertex circles without difficulty and they now display perfectly.

So, for the time being (next release), at least, your current design will work. But, if this creates other triangulation issues, I'll be reverting to 1mm.

Also, you need to keep an eye on overhead. 200 triangles at a time soon adds up.

Don
 
You must log in or register to reply here.
Back
Top