HowTo:Add LODs - Revision history

Klauss: Clarify LOD size parameter

2012-01-26T16:43:22Z

Clarify LOD size parameter

Pyramid at 14:08, 28 February 2011

2011-02-28T14:08:34Z

Pyramid at 13:50, 28 February 2011

2011-02-28T13:50:24Z

AzureSky: Added category

2008-09-09T16:20:37Z

Added category

Halleck: correcting false info but still unsure

2007-08-16T10:26:07Z

correcting false info but still unsure

Halleck: linked Terminology:LODs in first sentence

2007-07-07T11:48:11Z

linked Terminology:LODs in first sentence

Halleck: /* See also */ +l Terminology:LODs

2007-07-07T11:47:00Z

‎See also: +l Terminology:LODs

Halleck: check 0_1 name

2006-05-15T18:51:30Z

check 0_1 name

Halleck: new article with LOD instructions and VSNav

2006-05-15T18:49:37Z

new article with LOD instructions and VSNav

New page

{{NAV_Manual |
| previous=[[HowTo:Edit XMESH files|Editing XMESH]]
| up=[[HowTos]]
| next=[[HowTo:Add Engine Glow|Adding Engine Glow]]
}}
----
'''Levels of Detail''', or '''LODs''', are used to help cut down strain on the engine. An LOD mesh is a simplified version of the high-detail (top-level) mesh. When an object is far away from the player, the engine switches to the low-poly LOD so it is easier to render.

It's easy to reference LODs from within the xmesh file of the top-level mesh.
All you need to do is place an <LOD> tag somewhere betweeen the <mesh> and </mesh> tags. For example:

<LOD meshfile="1_1.xmesh" size="1600" />

Would reference a LOD to replace the current xmesh when the mesh occupies 40x40 pixels on the screen. (Size is the product of the pixel dimensions.)

Here is an example of the standard naming scheme for xmeshes:
*name.xmesh = the main mesh
*1_0.xmesh = submesh #1
**1_1.xmesh = the 1st LOD of submesh #1
*2_0.xmesh = submesh #2
**2_1.xmesh = the 1st LOD of submesh #2
**2_2.xmesh = the 2nd LOD of submesh #2

and so on.

Note that when creating a BFXM file, '''only''' the top level xmeshes need to be appened. For instance, if you are compiling the mesh above, all you need to do is:
mesher.exe name.xmesh name.bfxm xbc
mesher.exe 1_0.xmesh name.bfxm xba
mesher.exe 2_0.xmesh name.bfxm xba
Mesher will automatically append all LODs.

==See also==
*See [[Development:Model Guidelines#Polygon/Vertex Count]] for guidelines on LOD polycounts.
----
{{NAV_Manual |
| previous=[[HowTo:Edit XMESH files|Editing XMESH]]
| up=[[HowTos]]
| next=[[HowTo:Add Engine Glow|Adding Engine Glow]]
}}

@@ Line 12: / Line 12: @@
   <LOD size="275" meshfile="1_1.xmesh" />
-Would reference a LOD to replace the current xmesh when the mesh occupies ? pixels on the screen. Size is the perimiter of the pixel dimensions, multiplied by a figure based on the player's detail setting? {{Fixme}} - This is really confusing. Also, LODs don't work anymore.
+Would reference a LOD to replace the current xmesh when the mesh occupies less than 275 pixels on the screen. Size is the area of the bounding circle, multiplied by a figure based on the player's detail setting to offset the detail level. Figures on xmesh LOD entries should correspond to medium detail: the LOD switch is visible, but not too much.
 Here is an example of the standard naming scheme for xmeshes:

← Older revision		Revision as of 14:08, 28 February 2011
Line 32:		Line 32:

	For LODs to work, the entries must be sorted by decreasing size.		For LODs to work, the entries must be sorted by decreasing size.
		+	Basically, "10" means the mesh will be used when it will be drawn in an area 20 pixels wide (10 pixel radius).
		+	The numbers must be conservative, meaning they should be a safe transition point where the different between the meshes is barely noticeable, because user detail levels will take care of the rest.

	==See also==		==See also==

← Older revision		Revision as of 16:20, 9 September 2008
Line 41:		Line 41:
	\| next=[[HowTo:Add Engine Glow\|Adding Engine Glow]]		\| next=[[HowTo:Add Engine Glow\|Adding Engine Glow]]
	}}		}}
		+
		+	[[Category:HowTos\|LODs]]
		+	[[Category:Modeling\|LODs]]

@@ Line 30: / Line 30: @@
   mesher.exe 2_0.xmesh name.bfxm xba
 Mesher will automatically append all LODs.
 ==See also==

@@ Line 10: / Line 10: @@
 All you need to do is place an <LOD> tag somewhere betweeen the <mesh> and </mesh> tags. For example:
-  <LOD meshfile="1_1.xmesh" size="1600" />
+  <LOD size="275" meshfile="1_1.xmesh" />
-Would reference a LOD to replace the current xmesh when the mesh occupies 40x40 pixels on the screen. (Size is the product of the pixel dimensions.)
+Would reference a LOD to replace the current xmesh when the mesh occupies ? pixels on the screen. Size is the perimiter of the pixel dimensions, multiplied by a figure based on the player's detail setting? {{Fixme}} - This is really confusing. Also, LODs don't work anymore.
 Here is an example of the standard naming scheme for xmeshes:
 *name.xmesh = the main mesh
-**0_1.xmesh = 1st LOD of main mesh ?? {{Fixme}} - check facts
+**0_1.xmesh = 1st LOD of main mesh
 *1_0.xmesh = submesh #1
 **1_1.xmesh = the 1st LOD of submesh #1

@@ Line 5: / Line 5: @@
 }}
 ----
-'''Levels of Detail''', or '''LODs''', are used to help cut down strain on the engine. An LOD mesh is a simplified version of the high-detail (top-level) mesh. When an object is far away from the player, the engine switches to the low-poly LOD so it is easier to render.
+'''Levels of Detail''', or '''[[Terminology:LODs|LODs]]''', are used to help cut down strain on the engine. An LOD mesh is a simplified version of the high-detail (top-level) mesh. When an object is far away from the player, the engine switches to the low-poly LOD so it is easier to render.
 It's easy to reference LODs from within the xmesh file of the top-level mesh.
@@ Line 34: / Line 34: @@
 *See [[Development:Model Guidelines#Polygon/Vertex Count]] for guidelines on LOD polycounts.
 *See [[Terminology:LODs]] for a general explanation of LODs.
 ----
 {{NAV_Manual |