SEED

Introduction

The new and improved LOD System for TDM v1.03 lets you place entities in your map that reduce their own complexity when being far away from the player. However, there are still some huge drawbacks to this technique:

manually placing thousands of entities is very tedious and error prone
3000 entities "thinking" (deciding what LOD they have) takes about 7% of performance, even when they are not visible
The overall entity limit of 8192 entities - even if only ever 100 entities are visible to the player, you would not be able to create a forest with 10000 objects (trees, treestumps, flower patches and rocks etc.)

So there needs to be a way to dynamically only create the needed entities - and remove any no longer needed entities temporarily (but completely) from the gameworld. Of course, if nec., the formerly existing entities need to be recreated. In addition, we want some way to randomly place entities without having to specify their position/rotation for each entity.

The new LODE system provides exactly this.

How to use it

In DarkRadiant, create a brush the size of the area you want to cover
With that brush still selected, and select Create entity and select Darkmod/Info/atdm:lode

Note:
If you want to resize the LODE entity after creating it, select it with SHIFT +

and press TAB to select the brush, then resize it normally.

Now create the entities that you want to appear. Entities that use the LOD system should be prefered.
Link each entity from the LODE entity by selecting first the LODE, then the entity, and then press CTRL+K.
Put the entities at the hight you want them to appear. Alternatively, use the spawnarg "lode_floor" on the entity (see below for more spawnargs).
Remember to dmap whenever you add, delete or change the position/size of a LODE!

Area shape and blocking areas

At the moment the area covered by the entity is always treated as a (possible rotated) box. That means you cannot get f.i. triangle shaped areas (yet). However, it is possible to block some areas inside the covered area from getting any entities via Darkmod/Info/atdm:no_lode entities. With this "boolean subtract" you can create "holes" or even more complex shapes.

To get this to work, place atdm::no_lode entities and then link them from the LODE. If you want to have one LODE inhibitor to block more than one intersecting LODE, simply link it from both. See screenshot at right for an example.

Spawnargs on the LODE

These spawnargs can be set on the LODE itself and set defaults or influence overall strategies:

seed

Default: 0. The random seed. If not set or set to 0, a random value will be used (this is the recommended way, as it generates different results every time you start the map anew, but still keeps the entities when you f.i. save and then load a game).

If set to > 0, the random number generator will always generate the same sequence, so you get still randomly distributed results, but they are always the same.

spacing

Default: 0. Defines a minimum distance between placed entities. If set to > 0, implies collision check at creation time between all entities.

cull_range

Default: 150 units. Entities further away from the player than hide_distance (as defined on each LOD entity) + cull_range will be removed from the game world. When they come closer to hide_distance + (cull_range / 2), they will respawn automatically.

max_entities

Default: 0. The maximum number of entities generated. If 0 (the default), then the number will be computed from the aprox. area the LODE covers, taking into account the density spawnarg.

density

Default: 1.0. A factor multiplied with the number of entities generated if max_entities is 0.

Spawnargs on Targets

These spawnargs can be set on the entities that the LODE targets:

lode_floor

Default: 0 (Off). If set to 1, all entities of this class will be floored, that is their position will be adjusted so that they touch whatever is under them. This works with dynamically created terrain or terrain consisting of irregular heights like when it was made from patches. See also lode_collide and lode_stack.

lode_score

Sets the score for this entity class. All scores will be summed together, and the score for each class will be the percentage of entities of this class to create. Some examples:

Entity A: 4, Entity B: 5: Sum: 9, 4/9 of all entities will be of class A, and 5/9 will be class B
Entity A: 1, Entity B: 2: Entity C: 7, Sum: 10, 1/9 of all entities will be of class A, 2/10 will be class B and 7/10 will be of class C

lode_spacing

Defines a minimum distance between placed entities of this class. Overrides the default setting from "spacing" on the LODE. If set to > 0, implies collision check at creation time between all entities of this class.

lode_stack

Section not done yet.

lode_collide

Section not done yet.

Other LOD spawnargs

You can of course use other LOD spawnargs on the entities that the LODE creates. See LOD for a list.

Script events

There exist a few script events that can be used either from scripts, or by setting up a trigger that links to an atdm:target_callobjectfunction with the spawnarg call set to one of the script functions below:

Deactivate()

Deactivates the thinking of this LODE. Spawned entities stay where they are.

Activate()

Activates the LODE (e.g. it starts to think) again. If nec., the LODE will also spawn and unhide any entities that it needs.

CullAll()

Removes all entities under control of this LODE from the game. Only useful if either the player is very far away, or if you have called Deactivate() before - otherwise the entities might be spawned again in the next frame.

Ideas

Not implemented yet, but worth considering:

lode_strategy

How the entities will be placed. Default: "random", but can be "grid" (needs a way to specifiy grid-size, grid spacing, and random-offset from grid position).

lode_bunching

Default: "0" (Off). Number from 0.0 to 1.0, giving the probability that a randomly created entities "bunches" up with an already existing entity. Other related settings: "lode_max_bunched" (limit number of entities per bunch), and "lode_bunch_spacing_min" and "lode_bunch_spacing_max" (how much space leave between bunched-up entities).

Implementation details: For each entity created, track the "bunchmaster". If "where we bunch to" has no bunchmaster, it becomes the new bunchmaster - second entity uses first as bunchmaster- This allows us to query "how many entities bunch up together at this spot"-