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

FSXA Render polys above vectors

"Bumped" for an interesting CAVEAT which I ran across today by Holger that is related to a topic under consideration by the OP in this thread:

"vector autogen can indeed have a major impact on resources. I assume that's because this type of autogen isn't batched as the generic autogen objects are"

http://www.fsdeveloper.com/forum/showpost.php?p=85254&postcount=9


Hope this helps ! :)

GaryGB
 
Last edited:
Vector autogen indeed has some unexpected hits on the performance, but unlike Holger assumed, it is in fact batched. You can use a big number of vector autogen objects with less impact than the same number of unbatched library objects.
This has nothing to do with the original discussion though, that was about render priority.
I can conclude that discussion with the confirmation that vectors are indeed always rendered above polys, no matter how much you try to hide them under the polys. The only way around this issue is to clip your vectors so they don't overlap with polys - or live with the fact that they are rendered above them of course.
 
Vector autogen indeed has some unexpected hits on the performance, but unlike Holger assumed, it is in fact batched. You can use a big number of vector autogen objects with less impact than the same number of unbatched library objects

Many Thanks for that up-to-date clarification, Thorsten ! :)

GaryGB
 
Back
Top