Advanced LOD Techniques - Revision history

Windwalkr at 05:08, 19 October 2017

2017-10-19T05:08:05Z

← Older revision		Revision as of 05:08, 19 October 2017
Line 8:		Line 8:

	=Use of mesh-table LOD with LM.txt=		=Use of mesh-table LOD with LM.txt=
	Mesh-table LOD is an entirely separate concept from the self-contained LOD present in [[LM.txt file]]s. You should not attempt to configure the LM.txt transition distances using the "mesh-table-lod-transition-distances" tag. It is, however, possible to combine the effects.		[[Mesh-table LOD]] is an entirely separate concept from the self-contained LOD present in [[LM.txt file]]s. You should not attempt to configure the LM.txt transition distances using the "mesh-table-lod-transition-distances" tag. It is, however, possible to combine the effects.

	Consider the following LOD structure:		Consider the following LOD structure:

Windwalkr at 05:07, 19 October 2017

2017-10-19T05:07:29Z

← Older revision		Revision as of 05:07, 19 October 2017
Line 28:		Line 28:


	[[File:lodandlm.jpg]]		[[File:lodandlm.jpg\|border\|middle\|x400px]]

N3vpolsen: /* Use of mesh-table LOD with LM.txt */

2017-10-17T06:25:18Z

Use of mesh-table LOD with LM.txt

← Older revision		Revision as of 06:25, 17 October 2017
Line 31:		Line 31:


	To explain the above image even further. The [http://online.ts2009.com/mediaWiki/index.php/KIND_Mesh#mesh-table-lod-transition-distances mesh-table-lod-transition-distances] ~~are~~ set to the following lod transitions:		To explain the above image even further. The [http://online.ts2009.com/mediaWiki/index.php/KIND_Mesh#mesh-table-lod-transition-distances mesh-table-lod-transition-distances] tag is set to the following lod transitions:
	Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:		Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:

N3vpolsen: /* Use of mesh-table LOD with LM.txt */

2017-10-17T06:24:31Z

Use of mesh-table LOD with LM.txt

← Older revision		Revision as of 06:24, 17 October 2017
Line 31:		Line 31:


	To explain the above image even further. The [http://online.ts2009.com/mediaWiki/index.php/KIND_Mesh#mesh-table-lod-transition-distances ~~link~~ mesh-table-lod-transition-distances] are set to the following lod transitions:		To explain the above image even further. The [http://online.ts2009.com/mediaWiki/index.php/KIND_Mesh#mesh-table-lod-transition-distances mesh-table-lod-transition-distances] are set to the following lod transitions:
	Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:		Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:

N3vpolsen at 06:23, 17 October 2017

2017-10-17T06:23:54Z

← Older revision		Revision as of 06:23, 17 October 2017
Line 31:		Line 31:


	To explain the above image even further. The [[mesh-table-lod-transition-distances ~~file]~~] are set to the following lod transitions:		To explain the above image even further. The [http://online.ts2009.com/mediaWiki/index.php/KIND_Mesh#mesh-table-lod-transition-distances link mesh-table-lod-transition-distances] are set to the following lod transitions:
	Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:		Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:

N3vpolsen at 06:21, 17 October 2017

2017-10-17T06:21:42Z

← Older revision		Revision as of 06:21, 17 October 2017
Line 26:		Line 26:

	Since the mesh-table LOD is independent of and takes precedence over the [[LM.txt file]] LOD, you must ensure that the LOD distances between the two systems are appropriately configured to show each of the [[LM.txt file]] LOD meshes before switching to the next mesh-table LOD. If you get this wrong, you may find that the next mesh-table LOD kicks in before the LM mesh has reached low detail.		Since the mesh-table LOD is independent of and takes precedence over the [[LM.txt file]] LOD, you must ensure that the LOD distances between the two systems are appropriately configured to show each of the [[LM.txt file]] LOD meshes before switching to the next mesh-table LOD. If you get this wrong, you may find that the next mesh-table LOD kicks in before the LM mesh has reached low detail.


	[[File:lodandlm.jpg]]		[[File:lodandlm.jpg]]

	To explain the above image even further. The ~~“mesh~~-table-lod-transition-~~distances”~~ are set to the following lod transitions:
	Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the ~~.lm~~.txt lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:		To explain the above image even further. The [[mesh-table-lod-transition-distances file]] are set to the following lod transitions:
	mesh("0.15")		Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the [[LM.txt file]] lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:
	{
	name="body_lod4.trainzmesh";		mesh("0.15")
	}		{
	mesh("0.4")		name="body_lod4.trainzmesh";
	{		}
	name="body_lod3.trainzmesh";		mesh("0.4")
	}		{
	mesh("0.95")		name="body_lod3.trainzmesh";
	{		}
	name="body_lod2.trainzmesh";		mesh("0.95")
	}		{
	mesh("1.0")		name="body_lod2.trainzmesh";
	{		}
	name="body.trainzmesh";		mesh("1.0")
	}		{
			name="body.trainzmesh";
			}

	Mesh-table container “lod1” will show from 1500 meters to 2000 meters.		Mesh-table container “lod1” will show from 1500 meters to 2000 meters.

	From 2000 meters and beyond no meshes will be rendered.		From 2000 meters and beyond no meshes will be rendered.

N3vpolsen: /* Use of mesh-table LOD with LM.txt */

2017-10-17T06:18:13Z

Use of mesh-table LOD with LM.txt

← Older revision		Revision as of 06:18, 17 October 2017
Line 28:		Line 28:

	[[File:lodandlm.jpg]]		[[File:lodandlm.jpg]]

			To explain the above image even further. The “mesh-table-lod-transition-distances” are set to the following lod transitions:
			Mesh-table container “lod0-lm” will show from 0 – 1500 meters and the .lm.txt lod transitions will automatically swap in and out automatically between that range based on how the .LM lod functionality works:
			mesh("0.15")
			{
			name="body_lod4.trainzmesh";
			}
			mesh("0.4")
			{
			name="body_lod3.trainzmesh";
			}
			mesh("0.95")
			{
			name="body_lod2.trainzmesh";
			}
			mesh("1.0")
			{
			name="body.trainzmesh";
			}
			Mesh-table container “lod1” will show from 1500 meters to 2000 meters.
			From 2000 meters and beyond no meshes will be rendered.

N3vpolsen at 06:04, 17 October 2017

2017-10-17T06:04:17Z

← Older revision		Revision as of 06:04, 17 October 2017
Line 26:		Line 26:

	Since the mesh-table LOD is independent of and takes precedence over the [[LM.txt file]] LOD, you must ensure that the LOD distances between the two systems are appropriately configured to show each of the [[LM.txt file]] LOD meshes before switching to the next mesh-table LOD. If you get this wrong, you may find that the next mesh-table LOD kicks in before the LM mesh has reached low detail.		Since the mesh-table LOD is independent of and takes precedence over the [[LM.txt file]] LOD, you must ensure that the LOD distances between the two systems are appropriately configured to show each of the [[LM.txt file]] LOD meshes before switching to the next mesh-table LOD. If you get this wrong, you may find that the next mesh-table LOD kicks in before the LM mesh has reached low detail.

			[[File:lodandlm.jpg]]

Windwalkr at 02:06, 16 October 2017

2017-10-16T02:06:52Z

← Older revision		Revision as of 02:06, 16 October 2017
Line 2:		Line 2:

	=Texture Atlas at low LOD=		=Texture Atlas at low LOD=
			Using a [[texture atlas]] can be a great way to make a scene more efficient. Many related (ie. frequently used together) assets can be combined into a [[mesh library]] and use [[material sharing]] to qualify for [[mesh stitching]]. For some assets, this approach might seem unworkable at first because the object requires too much detail (either texture detail or mesh detail) up close. With too much texture detail, it would be impossible to fit a large number of assets into the texture atlas. With too much mesh detail, [[mesh stitching]] would be disabled.

			Such assets can still participate in the benefits of a texture atlas by using mesh-table LOD with their higher LODs using unique materials and high-detail meshes, with the lower LODs using the texture atlas and low-detail meshes. The high-detail meshes won't participate in mesh stitching, but there won't be many of them on the screen anyway. The low-detail meshes, of which there are likely to be quite a lot in the scene, will benefit from the more efficient approach.

Windwalkr: Created page with "This page details a number of LOD techniques which are not in themselves new capabilities, but rather which make inventive use of existing capabilities. =Texture Atlas at low..."

2017-10-16T01:51:12Z

Created page with "This page details a number of LOD techniques which are not in themselves new capabilities, but rather which make inventive use of existing capabilities. =Texture Atlas at low..."

New page

This page details a number of LOD techniques which are not in themselves new capabilities, but rather which make inventive use of existing capabilities.

=Texture Atlas at low LOD=

=Use of mesh-table LOD with LM.txt=
Mesh-table LOD is an entirely separate concept from the self-contained LOD present in [[LM.txt file]]s. You should not attempt to configure the LM.txt transition distances using the "mesh-table-lod-transition-distances" tag. It is, however, possible to combine the effects.

Consider the following LOD structure:

* Mesh-table LOD 0
** LM.txt LOD 0
** LM.txt LOD 1
** LM.txt LOD 2
* Mesh-table LOD 1
** IM
* Mesh-table LOD 2
** IM

In this scenario, you effectively offer 5 LOD levels. There are 3 mesh-table LOD entries, but the top LOD is itself an LM.txt file with additional "sub-LODs".

Using this approach allows you to use features that are exclusive to the [[LM.txt file]] format, such as [[attachment point]] LOD control and animation shared across LOD levels, while benefiting from the efficiencies of mesh-table LOD (such as fully-disabled animation and suitability for [[mesh stitching]]) at lower detail levels.

Since the mesh-table LOD is independent of and takes precedence over the [[LM.txt file]] LOD, you must ensure that the LOD distances between the two systems are appropriately configured to show each of the [[LM.txt file]] LOD meshes before switching to the next mesh-table LOD. If you get this wrong, you may find that the next mesh-table LOD kicks in before the LM mesh has reached low detail.