Troubleshooting - RaynorD/cav_ranges GitHub Wiki

A lot of error checking has been built into the framework to gracefully alert the administrator via the server rpt file to exactly what has gone wrong. By default the rpt is located here:

%userprofile%\AppData\Local\Arma 3

Paste that into a file explorer window and it should open directly. Sort by date modified and the rpt for the current or most recent session should be at the top.

I use LogFusion for monitoring live output of logs, but notepad++ for searching through past logs.

This file will be quite large, but any output generated by the framework itself will be prefixed with (CAV) [RANGES] like so:

So searching "ranges" should show you all the output from the framework. If you see any followed by "ERROR", then a part of the framework code has entirely halted after detecting a problem. What follows it should tell you exactly what is wrong. Take for example:

15:41:30 (CAV) [RANGES] ERROR: Shooting pos (gr_shootingPos_l1) is null: ...

This is saying that it couldn't find that object and you should check that the shooting pos on gr lane 1 is named correctly.

LOG and INFO are harmless output for troubleshooting later errors, and WARNING means something is wrong but function can continue for the most part.

If you can't find any errors mentioned by debug output, a script error may have occured. I did my best to handle as many errors as possible within the framework but some are bound to slip through, especially if the configuration has an issue.

Searching the log for "expression" will take you to any script errors. They will have a similar structure to this:

15:15:08 Error in expression <uping == 0) then { 
{
_target = nil;
if(_target > ((count _laneTargets) - 1)) th>
15:15:08   Error position: <_target > ((count _laneTargets) - 1)) th>
15:15:08   Error Undefined variable in expression: _target
15:15:08 File cav_ranges\fnc\fn_startRange.sqf [cav_ranges_fnc_startRange], line 311

If you see any script errors mentioning cav_ranges, it would be extremely helpful to copy them into a bug report issue on github, especially the last line mentioning the file and line where the error occurred. Try to find the earliest possible script error - they often cascade, and the earliest error is the root cause.

If you end up submitted a bug report, please provide the entire rpt file, as well as your entire createRange call.