Found .RPT and getting strange bugs

[vincentz 1]

Before I found it, I was trying to speed read. :butbut: (feeling stupid)...

Anyway to get rid of these bugs :

None of this is in my scripts :(

Error in expression <;
_recompile = (count _this) > 0;


if (BIS_fnc_init && !_recompile) exitwith {t>
 Error position: <BIS_fnc_init && !_recompile) exitwith {t>
 Error Undefined variable in expression: bis_fnc_init
File ca\Modules\Functions\init.sqf, line 28
Error in expression <] spawn BIS_ARTY_F_playerMonitor;


if (BIS_ARTY_SHELLTRACK_DEBUG==1 && !isNull(>
 Error position: <BIS_ARTY_SHELLTRACK_DEBUG==1 && !isNull(>
 Error Undefined variable in expression: bis_arty_shelltrack_debug
File ca\modules\arty\data\scripts\init.sqf, line 87
Old style material 205 used in ReportStack not available
Out of path-planning region for O 1-1-M:4 at 6198.8,6372.5, node type
Error in expression <onsLBSetFocus;
};
default {

};
};


if _doFilter then {
(_filterSets select IGU>
 Error position: <_doFilter then {
(_filterSets select IGU>
 Error Undefined variable in expression: _dofilter
File ca\ui\scripts\handleGear.sqf, line 521
Error in expression <onsLBSetFocus;
};
default {

};
};

[xxanimusxx 2]

These errors stem from BIS-Functions which sometimes contain bugs or will produce errors in conjunction with user made scripts.

The only way I got rid of these errors is to install the last "stable" beta update (afaik build 108074 is the culprit here, dunno if installing 112555 would help...)

[opusfmspol 282]

The errors stemming from modules can be resolved by recreating the ca folder path in your mission file, placing the problem script there and fixing the problem line. i.e., for functions you would create file path ca\Modules\Functions in your mission and place the functions init.sqf script in the Functions folder, and fix the error line.

http://forums.bistudio.com/showthread.php?168767-ARMA-2-OA-beta-build-112555-(1-63-build-release-not-backward-compatible)&p=2564086&viewfull=1#post2564086

It will handle a number of errors thrown from the modules files; the functions error, silvie error, alice error... but for some errors it doesn't work. I know it doesn't resolve the _handleGear error, that one comes from UI rather than Modules. I think the post mentioned a work-around for that by icomrade.

Edited August 22, 2014 by OpusFmSPol

[vincentz 1]

Fantastic! Thanks guys, it was driving me crazy.