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
missionNamespace setVariable ["CHR_DisableDarkness",true,false];
to the init.sqf of your mission for the mod to work. Reason being the CHR_DisableDarkness uses the setaperture command and wants to keep it all for itself.
Take all my 7.7x58mm, sir.
This is just what the game needs for making the nights a touch more realistic instead of perpetually pitch black. Still works without an issue!
There is not a single word about AI in the description, the author did not bother to describe it, Maybe he didn't understand it. I had to do many tests disabling each of my mods in order to find the reason why my AI is sees at night without NVG like a real terminator.
The my personal result is this mod will break detection ranges in LAMBS AI mod, probably in other AI mods as well, will break any scenario, where there are soldiers without NVG in deep night.
CBA_fnc_waitUntilAndExecute instead - or CBA_fnc_addPerFrameHandler if you want to check the condition constantly (I doubt it is needed, until you want to change it on-fly).