Originally Posted by yaan98
Thanks for that info.

My final modifications to scenerybudgets which worked very good on my system (so far):

<Ring PatchWorldDim="1024" RingDim="21" LOD="17" MajorDensity="0.00046"/>
<Ring PatchWorldDim="512" RingDim="45" LOD="50" MajorDensity="0.00046"/>
<Ring PatchWorldDim="256" RingDim="45" LOD="70" MajorDensity="0.00046"/>
<Ring PatchWorldDim="128" RingDim="45" LOD="100" MajorDensity="0.00046"/>

Interestingly, the first ringdim makes a huge impact to the point it crashes cfs3.exe if I wander into the 30s or 40s. However, I can raise any of the other ones besides the first without crashes. Also, I see no difference in view distance if I reverse those numbers and put the first ringdim at 45 while the rest at 20s. I noticed that density setting at 46 is just as good as 50s and 60s. Between ~36 - 44, there is slightly lower density of trees/buildings, but better FPS (~5 FPS) and less hanging.

Overall, I'm pleased with these results.



The diameter of the ring is calculated as the PatchDim x RingDim / 3.14 ( derived from Pi x Diam = Circumference) where the Patch Dim is the dimension of the patch in meters, and the RingDim is the number of patches around the edge.
The way you show it above the 1024 ring (6844m diam) is a smaller diameter than the 512 ring (7333m diam). I'm not sure what the rendering engine is going to do with the overlap, but that's why the view distance didn't change.

Post #4421049 now includes some comments about the effect of the landclass.xml dimension values that has an influence on this as well.



Service To The Line,
On The Line,
On Time

US Army Ordnance Corps.