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

LODs.. Do you recommend them?

If that guy is thinking of putting in the chickens as well, then draw call hatching is definitely the way to go:).
 
This isn't LOD related but is an interesting examination of the effect of drawcalls versus polygons.

My T-28D aircraft comes in three versions:

The dual version has both the front and rear cockpits fully modelled.

The solo version has only the front cockpit modelled (the rear cockpit is largely not animated).

The attack version is the same as the solo version but with weapons.

Here are some stats from MCX:

DUAL has 675 drawcalls, 302406 polygons and averages 93.2 fps in FSX

SOLO has 580 drawcalls, 294209 polygons and averages 103.0 fps in FSX

ATTACK has 632 drawcalls, 354239 polygons and averages 97.7 fps in FSX

The interesting thing is that while the ATTACK version has around 17% more polygons it is still faster, framerate wise, than the DUAL version which is hampered by having 43 more drawcalls.

And while the DUAL and SOLO versions have only a 2% difference in polygons the 95 less drawcalls in the SOLO version yield faster framerates.

This kind of tells me that I should be more worried about reducing drawcalls as much as possible rather than worrying too much about the number of polygons (although I should worry about that too I guess).
 
Please read this thread http://www.fsdeveloper.com/forum/threads/drawcall-batching-in-fsx-sp2.16317/
The cars have single texture and drawcall batching improves a lot of performance.
But if you have complex thing place only once, LOD is the way to go.

Before ModelConverter for drawcall batching.
VTSMbeforeConverter.jpg


After ModelConverter
VTSMafterConverter.jpg


However, don't think that LOD is always the bad guy.
Drawcall batching has its limit too. When you hit the limit your model will disappear.
If that happens, I will come back to see what is the most complex thing that I need to do LOD. That way I can pull out some polygons from that limitation and put LOD to it. Usually better fps will come up.

Drawcall batching first, if hit the limit....go to do LOD for the most complex model that you have.

Moreover, you should not do drawcall batching for anything that use volume shadow. It will cause flickering shadow.
 
Last edited:
One texture → many objects → place many times should go for draw call batching.
One texture →single complex (ten thousand of polygons) object →place once shold go for LOD
 
Silly question maybe, but is it really useful to include LODs in an aircraft model?
I'm using LODs now for my Fokker, partly as a test for Felix' Blender2FSX, but I thought it might be useful to exclude that 9-cil radial from the model at LOD100. It consumes a relatively high number of tris now.

Anyone ideas on this?
 
Silly question maybe, but is it really useful to include LODs in an aircraft model?

Indeed it is. For example: I have noticed that shadows in FSX are derived from LODs, so, even if the sim displays LOD400, at altitude, its shadow on the ground is derived from a lower LOD. So, I think it is a good idea to include at least a rudimentary LOD5 model in the aircraft exterior for ground shadows at altitude. That should ease the load performance-wise. As for intermediate LODs, I don't think they are that necessary if you only fly single user. If you have a lot of AI aircraft using your model, then it is a good idea to model intermediate LODs. IIRC, there was a study by someone showing the effect of LODs on a multiplayer formation flying scenario, basically concluding that LODs where really effective in that scenario.
 
Thanks for that! I think only in fact 400, 100, and 5 are relevant. 100 remains visible for a long distance if I remember well.

Good to know about the shadow thing.
 
Back
Top