 |
Trying to decide whether having both kind of entities on the same visportal is an error or not: https://forums.thedarkmod.com/index.php?/topic/20226-dropped-visportal-diagnostic/&do=findComment&comment=486268 |
|
|
This is how it works right now. 1) Portal settings (mainly sound_loss) are applied in PostSpawn function of portal entities (both info_locationSeparator and info_portalSettings are portal entities). 2) The function overrides previous values, so if several entities apply different settings to the same visportal, the last values win. But this is not certain, of course =) I won't be surprised if some information from previous calls might persist... 3) Both types of portal entities schedule PostSpawn in their own code, and do that after 18 ms of spawning. And since spawn happens on map start, I assume that it happens in order entities are listed in .map file. So the bottom line is: if one visportal is contacted by several entities of types info_locationSeparator / info_portalSettings, then settings are taken from the latest entity in .map file. Which comes last is pretty undefined of course =) the type does not matter for sure Moreover, notice that the location-blocking capability works differently. The visportal blocks locations if there is at least one location separator which contacts it. |
|
|
So the actual change is here: r10401 Take info_portalsettings entities into account when checking location separators in dmap. Also I changed DR-visible description of these two entity types (which has not been done in ages): r16812 Improved editor_usage of info_locationSeparator and info_portalSettings. Minor stuff: r10400 Deleted references of light_loss spawnarg on portal entities. r16810 Deleted references of light_loss spawnarg on portal entities. r16811 Added bad info_portalsettings to portal diagnostics test map. |
- Anonymous
