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

MSFS24 Object disappearing before LOD limits, am I doing something wrong?

B

Bikuafuro

Messages
10
Country
portugal
Hi everyone, I started msfs2024 development quite recently and came across some strange things happening.

I’ve been doing some tests with objects LODs and I’m experiencing an odd behavior in sim. When I export an object with it’s associated LOD’s and minsize values I have to cycle a setting in the object properties, in sim, so that the values I entered for minsize works as expected, otherwise the transition of LODs occurs much sooner or even jumps LOD levels altogether. All this with an object that doesn’t go over hardcoded vertex limits.

Another thing that I’ve noticed is that when I’m far away from an object, it disappears before the minsize is reached with an object that respects the hardcoded vertex limits. In the statistics profiler it shows the last LOD with a red warning regarding bitmap count, should that be the issue why that LOD is disappearing even thought is within vertex limits? Also I’ve made sure to not have any texture associated to that last LOD, so I’m not sure why this warning is showing.

I would appreciate very much if someone can guide me in the right direction for a solution to these problems, mainly the second one.

Thanks in advance!
 

Attachments

  • LOD0.jpg
    LOD0.jpg
    558.1 KB · Views: 76
  • LOD1.jpg
    LOD1.jpg
    770.3 KB · Views: 78
  • LOD2.jpg
    LOD2.jpg
    498 KB · Views: 81
  • LOD2_Disappeared_WithinVertexLimits.jpg
    LOD2_Disappeared_WithinVertexLimits.jpg
    534.9 KB · Views: 73
You could zip a .blend file and attach it, or zip a .gltf and it's .bin You could include textures and the XML . You could upload it to a cloud service also. Then no one is guessing the solution. One thing to remember is the sim sets the LODs... not your minsize in the XML. I don't even know why they include it for 2024. You should have LODs, but the minsize is ignored. Also, objects can have an invisible large box added to them... then the sim's LODs will trigger from the size of that box, and not the original object.
 
Last edited:
At less 0.5 every object is removed at ULTRA (OLOD200)
if you lower OLOD, the cut is higher
And for 2024 leave those minSize at 0.0, the game will handle them for you
(Unless you want to switch the lod BEFORE the limits)
 
Thanks everyone for the quick answer and the help.

I made some tests with the invisible cube and with an increased OLOD setting, with more or less the same result, the asset disappears far too soon.

I'll do more tests with the information provided above to see if I can get a better result. Either way I'll attach the files here if someone wants to check and see if there's anything else that's causing this to happen.

Thanks again, and please let me know if there's anything I can change on blender or in the actual project to solve this issue.
 

Attachments

Last edited:
You must log in or register to reply here.
Back
Top