LOD - Revision history

Duzenko at 08:47, 7 August 2021

2021-08-07T08:47:34Z

← Older revision		Revision as of 08:47, 7 August 2021
Line 14:		Line 14:

	Note: The '''dist_check_period''' spawnarg needs to be combined with one of "hide_distance" or "lod_X_distance" and "model_lod_X", "skin_lod_X" or "noshadows_lod_X" to have any effect!		Note: The '''dist_check_period''' spawnarg needs to be combined with one of "hide_distance" or "lod_X_distance" and "model_lod_X", "skin_lod_X" or "noshadows_lod_X" to have any effect!

			2.10: Requirement have been relaxed. E.g. for shadow LOD you will now only need two spawnarg's: lod_1_distance and noshadows_lod_1.

	See also '''[[LOD Bias]]''' for how to hide individual entities depending on the menu setting.		See also '''[[LOD Bias]]''' for how to hide individual entities depending on the menu setting.

SteveL: /* Customizing AI models */

2015-02-08T10:46:06Z

Customizing AI models

← Older revision		Revision as of 10:46, 8 February 2015
Line 137:		Line 137:

	== Customizing AI models ==		== Customizing AI models ==
	From TDM 2.03, many of the common AI models use LOD. This is automatic. They are much more detailed ~~that~~ in 2.02 when seen close up, and are lower-poly when seen in the distance.		From TDM 2.03, many of the common AI models use LOD. This is automatic. They are much more detailed than in 2.02 when seen close up, and are lower-poly when seen in the distance.

	If you want to switch an AI's model, for example to make a Builder archer from a citywatch archer by changing the model def and the vocal set and team, then you have a choice: you can change all the different model_lod_* stages to match the ones used by your target Builder; or you can change only the "model" spawnarg, which will work ok but note that LOD will be switched off for that AI. That's because you won't your Builder archer to revert to a citywatch model when distant.		If you want to switch an AI's model, for example to make a Builder archer from a citywatch archer by changing the model def and the vocal set and team, then you have a choice: you can change all the different model_lod_* stages to match the ones used by your target Builder; or you can change only the "model" spawnarg, which will work ok but note that LOD will be switched off for that AI. That's because you won't your Builder archer to revert to a citywatch model when distant.

	This rule was applied so that existing maps with custom models on AI woudn't get broken by the new AI LOD feature. The rules are: if the mapper overrides the "model" spawnarg but doesn't override any "model_lod" spawnargs, LOD is disabled on the entity. If the mapper overrides at least one "model_lod" spawnarg too, that shows they have it in hand so LOD remains enabled on the entity.		This rule was applied so that existing maps with custom models on AI woudn't get broken by the new AI LOD feature. The rules are: if the mapper overrides the "model" spawnarg but doesn't override any "model_lod" spawnargs, LOD is disabled on the entity. If the mapper overrides at least one "model_lod" spawnarg too, that shows they have it in hand so LOD remains enabled on the entity.


	== History ==		== History ==

SteveL: + Customizing AI models

2015-02-08T10:45:44Z

+ Customizing AI models

← Older revision		Revision as of 10:45, 8 February 2015
Line 134:		Line 134:
	* '''lod_2_distance 200''' -- (optional further step)		* '''lod_2_distance 200''' -- (optional further step)
	* '''model_lod_2 ''LowerDetailModelName''''' -- even lower detail model (optional further step)		* '''model_lod_2 ''LowerDetailModelName''''' -- even lower detail model (optional further step)


			== Customizing AI models ==
			From TDM 2.03, many of the common AI models use LOD. This is automatic. They are much more detailed that in 2.02 when seen close up, and are lower-poly when seen in the distance.

			If you want to switch an AI's model, for example to make a Builder archer from a citywatch archer by changing the model def and the vocal set and team, then you have a choice: you can change all the different model_lod_* stages to match the ones used by your target Builder; or you can change only the "model" spawnarg, which will work ok but note that LOD will be switched off for that AI. That's because you won't your Builder archer to revert to a citywatch model when distant.

			This rule was applied so that existing maps with custom models on AI woudn't get broken by the new AI LOD feature. The rules are: if the mapper overrides the "model" spawnarg but doesn't override any "model_lod" spawnargs, LOD is disabled on the entity. If the mapper overrides at least one "model_lod" spawnarg too, that shows they have it in hand so LOD remains enabled on the entity.


	== History ==		== History ==

Tels: remove outdated note

2014-10-03T11:27:15Z

remove outdated note

← Older revision		Revision as of 11:27, 3 October 2014
Line 157:		Line 157:
	* Can hide only a fraction of all entities of the same class (''thinning out'')		* Can hide only a fraction of all entities of the same class (''thinning out'')
	* Allows the player (via the settings menu) to control the quality vs. speed		* Allows the player (via the settings menu) to control the quality vs. speed

	~~Note: The new system still works only for '''func_static''' (e.g. not for lights, AI etc)!~~

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

SteveL: /* History */ for version 2.03

2014-09-22T17:36:34Z

History: for version 2.03

← Older revision		Revision as of 17:36, 22 September 2014
Line 138:		Line 138:

	Doom3 did not have any LOD system at all. The first steps of such a system were added in TDM by supporting a '''hide_distance''' spawnarg, which made entities hide or portals close once they were further away than this distance. The LOD system in TDM was totally rewritten for v1.04.		Doom3 did not have any LOD system at all. The first steps of such a system were added in TDM by supporting a '''hide_distance''' spawnarg, which made entities hide or portals close once they were further away than this distance. The LOD system in TDM was totally rewritten for v1.04.

			Support for animated models and AI was added in TDM version 2.03. More details are available on the [http://bugs.thedarkmod.com/view.php?id=3770 bugtracker].

	=== Comparison ===		=== Comparison ===

SteveL: /* model_lod_X */ documenting "be_still" for 2.03

2014-09-22T17:32:51Z

model_lod_X: documenting "be_still" for 2.03

← Older revision		Revision as of 17:32, 22 September 2014
Line 82:		Line 82:

	Set the model the entity displays inside this LOD. If not set, uses the model from LOD 0 e.g. the one from the "model" spawnarg.		Set the model the entity displays inside this LOD. If not set, uses the model from LOD 0 e.g. the one from the "model" spawnarg.

			''From TDM version 2.03:''

			A special value "be_still" is supported for animated models. Setting model_lod_X to "be_still" for a LOD level means: stop the animation but don't switch model.

	==== skin_lod_X ====		==== skin_lod_X ====

SteveL: /* The new LOD System - Overview */ Removing mention of "after doom3 goes open source"

2014-09-22T17:30:19Z

The new LOD System - Overview: Removing mention of "after doom3 goes open source"

← Older revision		Revision as of 17:30, 22 September 2014
Line 7:		Line 7:
	SVG version of the above graphic [http://bloodgate.com/mirrors/tdm/TheDarkMod_LOD_System.svg here].		SVG version of the above graphic [http://bloodgate.com/mirrors/tdm/TheDarkMod_LOD_System.svg here].

	{{infobox\|Note: Fade in and fade out do '''only''' work ~~on entities~~ via ''[[alpha-fading]]'' ~~(e.g. with alphatest~~ materials ~~and~~ an alpha~~-channel in the texture that contains a range from 0..1.0). This is due~~ to ~~a deficit in the D3 engine and can only be fixed after D3 has gone open source~~.\|bg=#f09090\|fg=yellow}}		{{infobox\|Note: Fade in and fade out '''only''' work via ''[[alpha-fading]]'', so on materials that use an alpha blend and don't respond to lighting.\|bg=#f09090\|fg=yellow}}

	== How to use LOD in your TDM map ==		== How to use LOD in your TDM map ==

SteveL: /* Entities */ Adding mention of animated entities for 2.03

2014-09-22T17:28:22Z

Entities: Adding mention of animated entities for 2.03

← Older revision		Revision as of 17:28, 22 September 2014
Line 25:		Line 25:
	== Entities ==		== Entities ==

	Example entities:		Supported entity types:
			* Models that don't move (i.e. func static models)

			''From TDM version 2.03:''
			* Animated models like waving flags and laundry (i.e. anything with spawnclass idAnimated)
			* AI
			* Animated attachments to AI

			=== Example entities ===

	* atdm:nature_pine_skeleton (just the tree trunk)		* atdm:nature_pine_skeleton (just the tree trunk)

SteveL: /* Spawnargs */ adding offset_lod_X

2014-07-27T01:03:27Z

Spawnargs: adding offset_lod_X

← Older revision		Revision as of 01:03, 27 July 2014
Line 82:		Line 82:

	Boolean. If set, the entity casts no shadows while in this LOD zone.		Boolean. If set, the entity casts no shadows while in this LOD zone.

			==== offset_lod_X ====
			Vector. Origin offset that can be applied to the replacement model if it doesn't naturally line up with the original.

	==== lod_fadein_range ====		==== lod_fadein_range ====

	{{infobox\|Note: Fade in and fade out do only ~~qwork~~ via ''[[alpha-fading]]''~~. This can only be fixed after D3 has gone open source~~.\|bg=#f09090\|fg=yellow}}		{{infobox\|Note: Fade in and fade out only work via ''[[alpha-fading]]'', so on materials that use an alpha blend and don't respond to lighting.\|bg=#f09090\|fg=yellow}}

	In D3 units. If set to non-zero, then the object will start hidden and begin to fade in at '''lod_1_distance''' - '''lod_fadein_range''' and be completely (100% opacity) visible at '''lod_1_distance'''. This can be used to create entities that only appear in some distance but not close up.		In D3 units. If set to non-zero, then the object will start hidden and begin to fade in at '''lod_1_distance''' - '''lod_fadein_range''' and be completely (100% opacity) visible at '''lod_1_distance'''. This can be used to create entities that only appear in some distance but not close up.
Line 91:		Line 94:
	==== lod_fadeout_range ====		==== lod_fadeout_range ====

	{{infobox\|Note: Fade in and fade out do only ~~qwork~~ via ''[[alpha-fading]]''~~. This can only be fixed after D3 has gone open source~~.\|bg=#f09090\|fg=yellow}}		{{infobox\|Note: Fade in and fade out only work via ''[[alpha-fading]]'', so on materials that use an alpha blend and don't respond to lighting.\|bg=#f09090\|fg=yellow}}

	In D3 units. If set to non-zero, then the object will not vanish suddenly at '''hide_distance''', but start to fade out and be completely invisible at '''hide_distance''' + '''lod_fadeoutrange'''. Defaults to 0.		In D3 units. If set to non-zero, then the object will not vanish suddenly at '''hide_distance''', but start to fade out and be completely invisible at '''hide_distance''' + '''lod_fadeoutrange'''. Defaults to 0.

SteveL: /* Spawnargs */ Adding no_lod for 2.03+

2014-07-25T18:48:47Z

Spawnargs: Adding no_lod for 2.03+

← Older revision		Revision as of 18:48, 25 July 2014
Line 94:		Line 94:

	In D3 units. If set to non-zero, then the object will not vanish suddenly at '''hide_distance''', but start to fade out and be completely invisible at '''hide_distance''' + '''lod_fadeoutrange'''. Defaults to 0.		In D3 units. If set to non-zero, then the object will not vanish suddenly at '''hide_distance''', but start to fade out and be completely invisible at '''hide_distance''' + '''lod_fadeoutrange'''. Defaults to 0.

			=== no_lod ===
			:''This spawnarg will be available in TDM version 2.03''
			Set "no_lod" "1" to disable LOD completely on an entity. Useful if you want to make use of a LOD entity but use a custom setup.

	== Increasing the LOD steps ==		== Increasing the LOD steps ==