Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
I have been able to confirm this issue. I have been able to reproduce it in singleplayer as well.
The cause for this bug has been found, but I'm unable to say when it will be fixed.
To explain the bug in simple terms, the activation delay ("First Horde Delay") is actually the delay that occurs after the spawner is created before it starts working.
If you used the editor to place down a spawner module, this means that this delay is basically the delay since mission start (+3 secs for internal reasons).
Essentially, "First Horde Delay" does not take activation into account, which is of course a bit misleading.
I'm surprised we haven't discovered this problem earlier.
To workaround it, you would have to create a spawner module on the fly using scripts, though this requires some skill in scripting and that you dePBO the Z&D file to get the right module variable names.
This may be a bit much, so my advice to anyone would be to avoid this module for now if you want zombies to spawn on specific activation + a noticeable delay.
Use triggers and BIS_fnc_spawnGroup-alike functions instead.