SEED - Combining entities - Revision history

Springheel at 00:49, 9 June 2017

2017-06-09T00:49:45Z

← Older revision		Revision as of 00:49, 9 June 2017
Line 29:		Line 29:
	# If the "combine" spawnarg is set to 0 on the SEED entity, it will not combine entities. Warning: Using this can bring the system to its knees by spawning a couple thousand entities!		# If the "combine" spawnarg is set to 0 on the SEED entity, it will not combine entities. Warning: Using this can bring the system to its knees by spawning a couple thousand entities!
	# The maximum distance for entities to be combined is 2048 units, but can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity. Raising this distance can reduce the entity count, but be warned that very large entities might take a long time to be updated, which can lead to stuttering when the player walks around.		# The maximum distance for entities to be combined is 2048 units, but can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity. Raising this distance can reduce the entity count, but be warned that very large entities might take a long time to be updated, which can lead to stuttering when the player walks around.

			Apparently when all your entities are combined into one, they all of them hide at once when using hide_distance.


	{{seed}}		{{seed}}

Grayman: /* Parameters */

2011-06-22T00:37:48Z

Parameters

← Older revision		Revision as of 00:37, 22 June 2011
Line 21:		Line 21:
	# Merged entities will not cross visportals.		# Merged entities will not cross visportals.
	# Moveable entities, AI, func_smoke and other special entities will not be combined. Mostly only func_statics will be combined together.		# Moveable entities, AI, func_smoke and other special entities will not be combined. Mostly only func_statics will be combined together.
	# Entities can be solid or non-solid, both cases work. Solid models will also get a collision model that consists of multiple parts.		# Entities can be solid or non-solid; both cases work. Solid models will also get a collision model that consists of multiple parts.
	# ~~Wether~~ entities ~~these~~ use a real model (something.lwo) or are made from map geometry (brushes/patches) does not make a difference, the SEED system can work with both by using some clever tricks behind the scenes to recover the map geometry of brushes/patches. This means you can have '''one''' copy of a brush in your map, and at runtime it gets duplicated into multiple render models.		# Whether entities use a real model (something.lwo) or are made from map geometry (brushes/patches) does not make a difference, the SEED system can work with both by using some clever tricks behind the scenes to recover the map geometry of brushes/patches. This means you can have '''one''' copy of a brush in your map, and at runtime it gets duplicated into multiple render models.
	# The number of maximal tris/indexes per combined entity is hardcoded into the source code and cannot be changed. (The limit was found empirically by raising it until the system crashed, then lowering it again one step.)		# The number of maximal tris/indexes per combined entity is hardcoded into the source code and cannot be changed. (The limit was found empirically by raising it until the system crashed, then lowering it again one step.)

	These parameters can be changed:		These parameters can be changed:

	# If the "combine" spawnarg is set to 0 on the SEED entity, it will not combine entities. Warning: Using this can bring the system to its ~~kneeds~~ by spawning a couple of thousand entities!		# If the "combine" spawnarg is set to 0 on the SEED entity, it will not combine entities. Warning: Using this can bring the system to its knees by spawning a couple thousand entities!
	# The maximum distance of entities to be combined is 2048 units, but can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity. Raising this distance can reduce the entity count, but be warned that very large entities might take a long time to be updated, which can lead to stuttering when the player walks around.		# The maximum distance for entities to be combined is 2048 units, but can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity. Raising this distance can reduce the entity count, but be warned that very large entities might take a long time to be updated, which can lead to stuttering when the player walks around.

	{{seed}}		{{seed}}

Tels: typos

2011-04-11T18:05:25Z

typos

← Older revision		Revision as of 18:05, 11 April 2011
Line 13:		Line 13:
	== Combining manually placed entities ==		== Combining manually placed entities ==

	If you placed a few dozend or even more models of the same type in your map (f.i. a lot of ivy pieces), then it makes sense to combine these into one entity to save on drawcalls. This technique is called "watching over entities" and is described in detail in the [[SEED_-_Watching_entities]] article.		If you placed a few dozend or even more models of the same type in your map (f.i. a lot of ivy pieces), then it makes sense to combine these into one entity to save on drawcalls. This technique is called "watching over entities" and is described in detail in the '''[[SEED_-_Watching_entities]]''' article.

	== Parameters ==		== Parameters ==
Line 21:		Line 21:
	# Merged entities will not cross visportals.		# Merged entities will not cross visportals.
	# Moveable entities, AI, func_smoke and other special entities will not be combined. Mostly only func_statics will be combined together.		# Moveable entities, AI, func_smoke and other special entities will not be combined. Mostly only func_statics will be combined together.
	* Entities can be solid or non-solid, both cases work. Solid models will also get a collision model that consists of multiple parts.		# Entities can be solid or non-solid, both cases work. Solid models will also get a collision model that consists of multiple parts.
	# Wether entities these use a real model (something.lwo) or are made from map geometry (brushes/patches) does not make a difference, the SEED system can work with both by using some clever tricks behind the scenes to recover the map geometry of brushes/patches. This means you can have '''one''' copy of a brush in your map, and at runtime it gets duplicated into multiple render models.		# Wether entities these use a real model (something.lwo) or are made from map geometry (brushes/patches) does not make a difference, the SEED system can work with both by using some clever tricks behind the scenes to recover the map geometry of brushes/patches. This means you can have '''one''' copy of a brush in your map, and at runtime it gets duplicated into multiple render models.
	# The number of maximal tris/indexes per combined entity is hardcoded into the source code and cannot be changed. (The limit was found empirically by raising it until the system crashed, then lowering it again one step.)		# The number of maximal tris/indexes per combined entity is hardcoded into the source code and cannot be changed. (The limit was found empirically by raising it until the system crashed, then lowering it again one step.)

Tels: fill in

2011-04-11T18:04:54Z

fill in

← Older revision		Revision as of 18:04, 11 April 2011
Line 5:		Line 5:
	In both cases there are usually a lot of entities placed in a map. To improve the performance, the system can also combine entities and this page describes how that works.		In both cases there are usually a lot of entities placed in a map. To improve the performance, the system can also combine entities and this page describes how that works.

	== ~~How it works~~ ==		== Combining created entities ==

	~~{{red\|TODO}}~~		Whenever the SEED places entities in your map, it can also attempt to ''merge'' these entities into larger entities. This can achieve higher performance, because instead of drawing 1000 single grass-entities, only 1 entity needs to be drawn.

	~~=== Parameters ===~~		This system works entirely automatic, and you usually do not need to think about it.

	# The number of maximal tris/indexes is hardcoded into the source code and cannot be changed.		== Combining manually placed entities ==
	# The maximum distance of entities to be combined can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity.
			If you placed a few dozend or even more models of the same type in your map (f.i. a lot of ivy pieces), then it makes sense to combine these into one entity to save on drawcalls. This technique is called "watching over entities" and is described in detail in the [[SEED_-_Watching_entities]] article.

			== Parameters ==

			There are a few rules and parameters which influence which entities are combined/merged. The following rules are always automatically in effect and cannot be changed:

			# Merged entities will not cross visportals.
			# Moveable entities, AI, func_smoke and other special entities will not be combined. Mostly only func_statics will be combined together.
			* Entities can be solid or non-solid, both cases work. Solid models will also get a collision model that consists of multiple parts.
			# Wether entities these use a real model (something.lwo) or are made from map geometry (brushes/patches) does not make a difference, the SEED system can work with both by using some clever tricks behind the scenes to recover the map geometry of brushes/patches. This means you can have '''one''' copy of a brush in your map, and at runtime it gets duplicated into multiple render models.
			# The number of maximal tris/indexes per combined entity is hardcoded into the source code and cannot be changed. (The limit was found empirically by raising it until the system crashed, then lowering it again one step.)

			These parameters can be changed:

			# If the "combine" spawnarg is set to 0 on the SEED entity, it will not combine entities. Warning: Using this can bring the system to its kneeds by spawning a couple of thousand entities!
			# The maximum distance of entities to be combined is 2048 units, but can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity. Raising this distance can reduce the entity count, but be warned that very large entities might take a long time to be updated, which can lead to stuttering when the player walks around.

	{{seed}}		{{seed}}

Tels: add link

2011-02-08T18:10:36Z

add link

← Older revision		Revision as of 18:10, 8 February 2011
Line 1:		Line 1:
	== Introduction ==		== Introduction ==

	~~{{red\|TODO}}~~		The '''SEED''' (System for Environmental Entity Distribution) was created by Tels in Summer 2010 and can either create entities at random places (depending on underground, height, distribution patterns and so on), or manage manually placed entities.

			In both cases there are usually a lot of entities placed in a map. To improve the performance, the system can also combine entities and this page describes how that works.

	== How it works ==		== How it works ==
Line 10:		Line 12:

	# The number of maximal tris/indexes is hardcoded into the source code and cannot be changed.		# The number of maximal tris/indexes is hardcoded into the source code and cannot be changed.
	# The maximum distance of entities to be combined can be changed with the spawnarg '''combine_distance'''		# The maximum distance of entities to be combined can be changed with the spawnarg [[SEED - Spawnargs#combine_distance\|'''combine_distance''']] on the SEED entity.

	{{seed}}		{{seed}}

Tels: add

2011-02-08T18:04:17Z

add

New page

== Introduction ==

{{red|TODO}}

== How it works ==

{{red|TODO}}

=== Parameters ===

# The number of maximal tris/indexes is hardcoded into the source code and cannot be changed.
# The maximum distance of entities to be combined can be changed with the spawnarg '''combine_distance'''

{{seed}}