LOD's need list for each scenario in the SDK

See post below, See post below, See post below, See post below

Update. I wish the SDK would have suggested to create some invisible mesh that can be placed near the end of the wings and tail to force the interior bounding box to match the exterior. This was one of my issues and why my LOD’s were cycling so fast in Xbox and faster than the exterior.

I still think the devs should be able to override the ‘limits’ or enable an option to use the minSize=“value”.

Update:

I have been working with the FS Think Tank and we came up with this list to help anyone having trouble understanding how the LOD’s work. I hope Asobo can confirm this is accurate.

PC USER… Exterior LOD will always use LOD 0
PC USER… Interior LOD is based on minSize=“value” from the XML
PC MULTIPLAYER… Exterior LOD is based on minSize=“value” from the XML
PC MULTIPLAYER… Interior LOD is based on minSize=“value” from the XML

Xbox USER… Exterior LOD will always use LOD 0
Xbox USER… Interior LOD is based on minSize=“value” from the XML (but will keep the last LOD active)
Xbox MULTIPLAYER… Exterior LOD is based on sim limits
Xbox MULTIPLAYER… Interior LOD is based on sim limits

NOTE: Smaller objects for exterior only will auto hide prior to that LOD ending. It seems to use a different algorithm limit that is always active.

Be great if Asobo can create a list like this for the SDK…