Debugging Techniques: Difference between revisions
firefly2442 (talk | contribs) (Added tips about showscripterrors parameter as well as checking .rpt log files.) |
m (Added internal link) |
||
| Line 30: | Line 30: | ||
==Show Script Errors== | ==Show Script Errors== | ||
Start the game with the parameter "-showscripterrors" and this will show syntax issues and other problems right away in-game. | Start the game with the [[Arma2:_Startup_Parameters|parameter]] "-showscripterrors" and this will show syntax issues and other problems right away in-game. | ||
In addition, you can check the .rpt log files that get generated to see past errors and problems in detail. | In addition, you can check the .rpt log files that get generated to see past errors and problems in detail. | ||
Revision as of 08:17, 7 July 2010
Introduction
These are a few techniques which should help you to find bugs more efficiently when you're scripting. It should be noted that any techniques unless otherwise specified will work in each of the BI game titles.
Feel free to add any tips that you may feel will benefit other Operation Flashpoint/Armed Assault fans.
Hints
If something is not working, check which variables could be wrong, check the output of the variables using hints.
- In Armed Assault the arma.RPT is your first and foremost thing to check when you have problems with custom addon configs or mission scripts!
- Vektorboson released a debugging console for advanced users that is very helpful at debugging your scripting in real time. Please note, that this is for OFP only.
Armed Assault debug consoles:
- Debug console made by Str. It's in form of addon and it's available in all singleplayer missions, intros and outros. Easy and simple to use (Escape-Enter execute).
- TroopMon V 0.7 *Mission debugger - Complex debugging system providing lot of informations for mission-makers, escpecially about AI.
ARMA 2 debug consoles
- Debug console by Str
- TroopMon2 by Charon Productions
If you're at an advanced stage of a project, you can save the game when the bug appears and check the variable and script states with Chain of Command's Binary gamefile viewer.
Keep it simple
If you're having great difficulty solving a problem, simplify the problem, take the part of the mission which does not work, paste it into a new test mission so that you don't have to watch the effect of the rest of the script(s).
Show Script Errors
Start the game with the parameter "-showscripterrors" and this will show syntax issues and other problems right away in-game.
In addition, you can check the .rpt log files that get generated to see past errors and problems in detail.
Addon Tips
If you're scripting for an addon, don't pack the scripts in the PBO, as you have to restart after every change. Rather, make a test mission with the script included there.