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

FSX SP2 Scenery batching process - Warning

decapod

decapod

Messages
132
Country
england
To improve efficency, FSX SP2 can combine the draw calls of scenery objects that use identical materials.
(Which sometimes stops LOD's from working)

I did a small project for someone who wanted hundreds of different small bombing targets, so I tried to make sure they were all batched.

It does appear that there is a limit of 64K vertices that can be batched (which I sort of expected) - adding more objects to the BGL after this does not display the extra models.

This only affects batched scenery models - animated models and gMax models with empty animation blocks are not batched (and their LODs do work)
 
Not quite the same problem - Adrian was referring to a single model there.

My problem came about because in SP2 they implemented an "optimisation" to batch similar groups of scenery objects into a single draw call.

This situation is probably quite rare - people will use different texture files and materials for separate models whereas I used a single file for 16 different meshes.

The solution I used was to adjust the materials on a couple of the objects so it now takes two draw calls to render the 350+ objects.
 
Yes, although the problem wasn't the same, the solution is.

So how did we solve the problem? Well, once we animated some parts, that broke up the draw calls. Also, once we applied some different materials with different parameters, that also broke up the draw calls.
Click to expand...
 
You must log in or register to reply here.
Back
Top