2,732
edits
FlightGear Newsletter April 2016: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Red Leader (talk | contribs) (More cleanup) |
Red Leader (talk | contribs) No edit summary |
||
| Line 38: | Line 38: | ||
Previously, the LOD ranges of random objects, trees, buildings and STG objects were set variously by <tt>''materials.xml''</tt> and fixed values. This was very inconsistent and wasn't controlled by the user. They have now been made consistent to use the <code>/sim/rendering/static-lod/rough</code> property which can be set from the LOD GUI dialog. The impact of this is twofold: | Previously, the LOD ranges of random objects, trees, buildings and STG objects were set variously by <tt>''materials.xml''</tt> and fixed values. This was very inconsistent and wasn't controlled by the user. They have now been made consistent to use the <code>/sim/rendering/static-lod/rough</code> property which can be set from the LOD GUI dialog. The impact of this is twofold: | ||
* Scenery developers, and particularly those doing regional materials should not set the "tree-range-m" for random vegetation or the "range-m" property for random objects. | * Scenery developers, and particularly those doing regional materials should not set the "tree-range-m" for random vegetation or the "range-m" property for random objects. | ||
* Scenery models should not use the | * Scenery models should not use the [[Howto:Animate models#Range|range]] animation to control when the entire model becomes visible. This is now set appropriately by the simulation itself. However, it may still be a good idea to use the range animation to hide small details. | ||
== In the hangar == | == In the hangar == | ||