Differences

This shows you the differences between two versions of the page.

--- ofp:modeling:lod [2007/07/12 23:01] – more details to LODs snakeman
+++ ofp:modeling:lod [2024/07/31 16:07] (current) – links added. snakeman
@@ Line 1: / Line 1: @@
-====== Level of Detail (LOD) ======
+====== OFP Level of Detail (LOD) ======
+[[https://www.pmctactical.org/forum/viewforum.php?f=43|OFP Forum]], [[:ofp|OFP Home]], [[ofp:file_formats|OFP File Formats]], [[ofp:tools|OFP Tools]], [[ofp:missions|OFP Missions]], [[ofp:modeling|OFP 3D Modeling]], [[ofp:terrain|OFP Terrain]]
+**Operation Flashpoint (OFP)** aka ArmA: Cold War Assault (CWA)
 What's a LOD?
-{{ http://tactical.nekromantix.com/images/wiki/LODs.gif}}
+{{https://pmc.editing.wiki/images/LODs.gif}}
 LOD means Level of Detail, and is a method of defining, via different variations of a model, how high or low the viewable quality of the model should be, and how it should interact with the environment.
@@ Line 8: / Line 14: @@
 ====== <resolution> ======
-{{ http://tactical.nekromantix.com/images/wiki/Truck-ResLOD.jpg}}
+{{ https://pmc.editing.wiki/images/Truck-ResLOD.jpg}}
 Defines which model to use, depending on several, interdependent in-game conditions (view-distance, number of objects, video quality, CPU utilization, etc).
 This LOD shouldn't contain any empty Named Selections which are used in animations or by the game engine (wheels, etc), as that might cause the game to crash once the LOD becomes active.
-To demonstrate the complexity of the LOD selection, and the effect the resolution name has on LOD switching, a series of tests have been documented here: Resolution LOD Samples
+To demonstrate the complexity of the LOD selection, and the effect the resolution name has on LOD switching, a series of tests have been documented here: Resolution LOD Samples.
+If all your LODs (or if you only have one) are high polygon count, then your model will cause CPU slowdowns.
 ===== Details =====
@@ Line 39: / Line 47: @@
 </code>
 BIS M2A2 model has the following resolution LODs:
 <code>
 LOD A (0.750): ~3400
 LOD B (1.5): ~1900
 LOD C (3): ~1100
 LOD D (5): ~560
 LOD E (7): ~375
 LOD F (9): ~175
 </code>
@@ Line 72: / Line 80: @@
 Notice how the resolution values double for all values lower than 3. When the resolution value reaches 3, it is increased by steps of 2. Generally speaking, this means that the model detail halves whenever CPU load doubles. For lower details, declination in detail (and thus CPU load) decreases exponentially.
 If you have a vertex count that is very different from the BIS values, you can try to estimate a fitting resolution value for that LOD. Remember that more vertices = lower resolution value.
 For resolution values under 3, you should halve the resolution value each time you double the number of vertices. For resolution values over 3, subtract 2 each time you double the number of vertices. Performance-wise, lower resolution values increase system performance.
@@ Line 87: / Line 95: @@
 JeepMG : 0.750, 1.5, 3, 5 and 7.
 </code>
 ====== Geometry ======
-{{ http://tactical.nekromantix.com/images/wiki/Truck-GeoLOD.gif}}
+{{https://pmc.editing.wiki/images/Truck-GeoLOD.gif}}
-Defines where the model will collide with other objects.\\
-Should be //very// simple, and has to fulfil the following criteria in order to work:\\
+Defines where the model will collide with other objects. Should be //very// simple, and has to fulfil the following criteria in order to work:
-* Object must be Named Selection ComponentXX (where XX is a consecutive number between 01 and 99).\\
+  * Object must be Named Selection ComponentXX (where XX is a consecutive number between 01 and 99).
-* Must have 'Mass' (Alt-M).\\
+  * Must have 'Mass' (**ALT-M**).
-* Must be closed and convex (Validating Geometries).\\
+  * Must be closed and convex (Validating Geometries).
 Geometry objects should have a thickness of at least .5 meters in order to work properly.
 ====== Fire Geometry ======
-Defines where the model will collide with bullets & rockets.\\
+Defines where the model will collide with bullets & rockets. If this LOD is not present the Geometry LOD will be used instead.
-If this LOD is not present the Geometry LOD will be used instead.\\
-* Must be closed and convex (Validating Geometries).\\
 Proxies for the driver & passenger must be present into this LOD as well (they can be copied from the Resolution LOD). Otherwise the units will be invincible. One should also do any geometry validation ''before'' adding the proxies, otherwise they will not be functional.
+  * Must be closed and convex (Validating Geometries).
+  * The fire geometry and geometry LODs are to be made in very low polygon count.
+  * There is a limit of 128 (127?) Components.
 ====== Hit-points ======
@@ Line 135: / Line 149: @@
 ====== View - Cargo ======
-{{ http://tactical.nekromantix.com/images/wiki/Truck-View-Cargo.jpg}}
+{{ https://pmc.editing.wiki/images/Truck-View-Cargo.jpg}}
 What a cargo passenger can see of the model.
 In vehicles of the class "Car", the player will ''always'' see this view, whether he's the driver, co-driver or cargo. (Unless the "View - Pilot" is defined. Then ''that'' view is taken for any position inside the vehicle.)
@@ Line 194: / Line 208: @@
 ArmA/OFPE only: Visible shadow resolution lod for model. Typically named ShadowVolume 0.000 (Few features) and ShadowVolume 0.100 (same ammount of features as the main visual model (i.e. equipment, weapon systems, etc). Structure within it **must** be Triangulated and have Sharp edges. (Also see Creating Shadow LODs)