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
Thanks!
0:34:45 Error in expression <true];
for "_i" from 0 to 5 do {_flamer setObjectMaterialGlobal [_i,_flamer setO>
0:34:45 Error position: <setObjectMaterialGlobal [_i,_flamer setO>
0:34:45 Error Type Any, expected String
0:34:45 File Root_Anomalies\Root_Flamer\AL_flamer\flamer_main.sqf..., line 22
However, I will add in an additional switch, that, when enabled, will override the minimum 200 meter distance in the next update.
Thanks for taking time to solve it
If I can make a suggestion I would allow to have a smaller (minimum slider) area for the anomalies (50-100 metres instead of 200) if it doesn't create issues or is difficult to do
A common issue I've found so far is that when updating this mod using a MSP (Managed Service Provider, like webconsole and custom webpage), the mod often fails to get updated properly. I would suggest uninstalling my mods and reinstalling them again and forcing a repair if possible (on both Server and Client) and boot the server. This seems to fix the issue for most people.