
Above 1% size on screen, the statistic follows the described curve, which goes through a size on screen of 1, where the maximum number for a given statistic is hardcoded:.At 1% size on screen (y = 0) the maximum number for a given statistic is hardcoded:.Below 1% size on screen (y The y-axis is the resulting minimum for a given statistic.The x-axis represents the model's current size on screen (where 1 = 100%).The following graph gives a more visual representation of what's happening: Limits scale up with the "minSize" above 100%: at 150%, "maxVertices" is approximately 480k.The second-to-last LOD's "maxVertices" starts at 300, scaling up with the "minSize".

#Zmodeler 3 lod not enabled how to
You can find an example of how to set this up here: LOD files are stored as separate glTF files (one for each LOD) in the Models folder for the package.

In that case, multiple (or even all) LODs may be loaded and displayed at the same time, thus exist in memory at the same time, making optimising everything of paramount importance. Note though that the sum of the LODs in memory can still be relevant if an object is instantiated multiple times all around the player. To make sure this actually functions as designed by optimising performance, it is important that lower resolution LODs use less memory. This is because levels of detail will be loaded into memory only when necessary, ie: only the data necessary to display a model will be loaded into memory at any time.
#Zmodeler 3 lod not enabled series
In order to ensure optimal performance in Microsoft Flight Simulator for the models created for your add-ons (scenery, airports, aircraft, etc.) it is important to have a series of LODs created for each model.
