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

Objects Rendering Distance Problem

M

mailman

Messages
9
Country
germany
Hey guys!

I am having some problems with the rendering distance of objects. No matter if I change the bounding spheres to big or small, the last LOD disappears quite too early in my opinion.
I also tested with different grafics-settings "low-end" and "ultra" no difference.
Interestingly the LOD debugger shows that they are "there" but they are not visible anymore.
Does anbody has a clue how to force these objects to render in a farther distnace?

These white Runway Markings on the left and right side are my point
1648126310878.jpeg


Here with small bounding spheres
1648126345608.jpeg


And here with huge bounding spheres... unfortunately no difference, I see only 5-6 in the distance (per side of course)
1648126401323.jpeg
 
LOD translates to "level of detail" and it directly corresponds to screen pixel occupied real estate, with no relation to bounding box. You could however, as a workaround, add polygons of whatever dimension is necessary to delay LOD switching, to the model and located underground, making them effectively invisible.
 
=rk= said:
LOD translates to "level of detail" and it directly corresponds to screen pixel occupied real estate, with no relation to bounding box. You could however, as a workaround, add polygons of whatever dimension is necessary to delay LOD switching, to the model and located underground, making them effectively invisible.
Click to expand...

I don't think that's correct. According to the SDK Documentation, the MSFS engine calculates accoring to screen space size a bounding sphere, which is then the main factor for switching LODs.
Here are some references from the SDK.
The "minSize" is the minimum size on screen of the bounding sphere of the object within the camera view - as a percentage - before a LOD model is considered for display.
Click to expand...
It should be noted that in order to calculate the LOD used, the engine will use the bounding sphere...
Click to expand...

Display Bounding Spheres​

When this option is enabled, "bounding spheres" will be shown for all the models. These spheres are used as part of the screen size calculations as well as other internal calculations, and are a good way to visualise the approximate size and position of objects.
Click to expand...

My sceenshots in the previous post actually confirm this behaviour.
If you look at the middle picture, the left sidemarking has a screenspace size of 6.38% (small bounding sphere) and LOD1/1 is switched on.
On the lowest picture the screenspace size of sidemarking is at 1000% (and higher) so LOD0/1 is switched on.
As you see, the VISIBLE object size stays the same all the time. So this confirms, that LOD switching uses bounding sphere sizes.

The workaround you described is similiar to what you normaly do to influence the boundingsphere and therefore LOD switching. You create an object (box or sphere preferably) in the lowest LOD and apply the "invisible" material. Therefore the "engine rendered" boundingsphere is bigger and the clipping out of the view of the "visual object" is later... and vice-versa. So with your description of "creating a plane and move it down that it's hidden below the ground" is the same result.

1648199199592.png



Interesting is this... does anybody know what exactly has been done and when? Did something brake again?
1648200304133.png

1648200372380.png
 
mailman said:
I don't think that's correct. According to the SDK Documentation, the MSFS engine calculates accoring to screen space size a bounding sphere, which is then the main factor for switching LODs.
Here are some references from the SDK.
Click to expand...
Thanks for your feedback, but, did you try it? Because what you are already doing, according to the SDK, brought you here.

You might want to look into the LOD switching code within the model .XML, maybe reduce the minSize of a previous LOD, to increase the drawing distance of a problem LOD.
 
mailman said:
I don't think that's correct. According to the SDK Documentation, the MSFS engine calculates accoring to screen space size a bounding sphere, which is then the main factor for switching LODs.
Here are some references from the SDK.




My sceenshots in the previous post actually confirm this behaviour.
If you look at the middle picture, the left sidemarking has a screenspace size of 6.38% (small bounding sphere) and LOD1/1 is switched on.
On the lowest picture the screenspace size of sidemarking is at 1000% (and higher) so LOD0/1 is switched on.
As you see, the VISIBLE object size stays the same all the time. So this confirms, that LOD switching uses bounding sphere sizes.

The workaround you described is similiar to what you normaly do to influence the boundingsphere and therefore LOD switching. You create an object (box or sphere preferably) in the lowest LOD and apply the "invisible" material. Therefore the "engine rendered" boundingsphere is bigger and the clipping out of the view of the "visual object" is later... and vice-versa. So with your description of "creating a plane and move it down that it's hidden below the ground" is the same result.

View attachment 81052


Interesting is this... does anybody know what exactly has been done and when? Did something brake again?
View attachment 81053
View attachment 81054
Click to expand...


Whatever method this guy uses works: https://flightsim.to/file/16007/msf...anging-from-towers-hangers-terminals-to-cones

He states the following in the description: "Final long distance models have a large triangle added below ground to stop them disappearing in the distance.". I have used these objects in one of my sceneries specifically for the white runway cones, and there's no question that his method makes a massive difference. I can see those tiny white cones when I'm flying patterns.
 
@mailman
I Hope that my suggestion worked for you

For everyone else, the the big invisible stuff should be part of the mesh, OP had 2 mesh (marker and box), they should be joined as a single mesh

Inviato dal mio Mi 9 Lite utilizzando Tapatalk
 
You must log in or register to reply here.
Back
Top