Atomic Systems

Is the "lod killer tool" available?
I think it might improve the memory load and performance of MSTS.
As an example here is what Route-Riter reports about JP2IndusBuild,
it has 100m 173 polys / 200m 157 polys / 400m 134 polys / 800m 108 polys / 1200m 87 polys / 1500m 65 ppolys / 2000m 30 polys.

And a farm truck DFerguson6290-1 has 100m 772 polys / 200m 756 polys / 300m 562 polys / 1000m 180 polys. Looking closely at the 100m picture I can see front and tail lights, but apart from that the 772 or 756 poly picture has no real advantage over the 562 poly picture. What does if matter if the truck is in the field and you pass in a train with 120 kmh ?

Wim

Wim

PM me your email address and I'll send you a copy...



Doug

Hello Wim

I did some testing and after minimizing the LOD's (down to 1 or 2), I found MSTS did behave itself much better.

This was done before MSTSbin was being used by me so I'm not sure if the above is still a benefit.

I used Shape Viewer to see the quantity of lOD's and also to view them; Archibald was my tool of preference for any actual edits.

I did start a discussion at Train-Sim.com about this subject; search for the topic "Something for the brave (or foolhardy)" using the advanced search with the 'and' option in the "Microsoft Train Simulator" forum.

GaryG

I very rarely use LODs other than 2000m for locos. I haven't noticed any disadvantages in doing so. Depending on their complexity, I might use two or three LODs for scenery objects.

My preference for creating LODs is to remove parts off objects in the heirarachy rather than to remodel. A lot of small details cannot be seen once you get out to 200M or less.

Past debate on the subject has mostly centered around whether having the sim load successive LODs is more wasteful of sim resources in return for a marginally improved FPS. MSTSBin has improved memory management, so that might remove the need for multiple LOD models, except in areas of high poly scenery object density.

Cheers Bazza

Anyway I think that LodOptimiser has a clear advantage. Taking the Ferguson farm truck which had according SViewer 100m 772 polys / 200m 756 polys / 300m 562 polys / 1000m 180 polys, it is now reported as 1000m 772 polys.
The size of the s file is reduced from 64.452 bytes to 30.683 bytes.
I have not made any tests yet to take a train over a tile with over 1500 objects and see if the frame rate is improved.
Wim

Doug,

I've sent you a PM.

Thanks