Trainz/When to use lod
|
|||
|
| Glossary |
| HKeys-CM |
| HKeys-DVR |
| HKeys-SUR |
| HKeys-WIN |
| Mouse use |
| Notations |
Level of Detail
[edit | edit source]Chris Bergmann, Auran chief programmer:
"A decent rule of thumb might be that each lod should shave off at least 50% of the polygon detail, and that LODs below ~500 polys are not worthwhile unless you expect the item to be static and present numerous times in the same scene. (For example, a tree or generic house.)
More LODs means more memory usage and more CPU/GPU time in order to swap the LODs in and out as appropriate. You want to make sure that the time and memory lost in LOD swapping is more than compensated for in the polygon savings. Small polygon gains just don't make sense in this light."
This forums.Auran.com thread contains a lot of useful information about the different methods of lod and when it should be used: Level of Detail, how useful is it?
  |
Be advised this new Trainz Wikibooks topic page is rough and incomplete. It was last edited on 26 September 2019, and is still under heavy construction. This Page UNDERCONSTRUCTION: Content here is likely to be changed significantly in a short amount of time. All Trainzer's and Wikibookians with knowledge in this subject are welcome to help out. You can remove this tag and replace it with {{Trainz-stub}} or with section stub templates ({{Trainz-sect-stub}}) on unfinished sections when the 'page' has become more mature. |
 |