OFPEC Forum

Editors Depot - Mission Editing and Scripting => Arma2 - Editing/Scripting General => Topic started by: johnnyboy on 15 Aug 2009, 03:07:53

Title: where are scripting errors in arma2? -- SOLVED
Post by: johnnyboy on 15 Aug 2009, 03:07:53

I have a script that is obviously not working, but I am getting no errors on the screen.

Where do scripting errors display?

I read about a arma2.rpt file, but I can't find that on my disk either...

Please advise.

Title: Re: where are scripting errors in arma2
Post by: Worldeater on 15 Aug 2009, 05:36:33

Errors are logged to the RPT (http://community.bistudio.com/wiki/arma.rpt) by default. You can also turn on the old behaviour of displaying them in-game by using the showScriptErrors command line option (http://community.bistudio.com/wiki/Arma2:_Startup_Parameters).

Logging errors to the RPT might seem strange but it has a great advantage: the error messages don't vanish and if you have multiple error they don't overwrite each other. Using a log viewer like Log Expert (http://www.log-expert.de/) eases the task of keeping track of new RPT entries.

Title: Re: where are scripting errors in arma2
Post by: johnnyboy on 15 Aug 2009, 07:42:47

Thanks Worldeater, but how do I view the errors in the RPT.

Is there a file written to a particular directory?

 I searched my disk for arma2.rpt, but it came up empty..

Edit:  OK, I now see the link to the RPT you provided.  silly me.  Thanks!

Title: Re: where are scripting errors in arma2
Post by: Worldeater on 15 Aug 2009, 07:49:30

Quote

WINDOWS XP:
C:\Documents and Settings\username\Local Settings\Application Data\ArmA

WINDOWS VISTA AND 7 (BETA/RC):
C:\Users\username\AppData\Local\ArmA

Have you looked in these directories?


Edit: And I'm a numbnut who just posted the A1 directories...  :whistle:

Title: Re: where are scripting errors in arma2? -- SOLVED
Post by: johnnyboy on 15 Aug 2009, 21:12:21

Thanks worldeater.  The link you provided in your first post to RPT in the wiki explains it all.

It is quite useful.  I just keep the .rpt file up in Notepad++, and its appended to every time I preview a mission.  While debugging scripts, I clear the arma.rpt file and save it first, so I only see the new errors on the next preview test.

Solved!