Easy Debug of Missions?

Rob86TA · 10-09-05, 11:14 PM

Is there an easy way to debug missions? A view or command line toggle that can give me a bit more of a description of what's actually happening?

There's got to be a trick... there's no way Sonalysts does things my way. Which is to put a tonne of triggers in and watch their output. It works... but setting up the debug of a mission takes longer than actually designing it!

MaHuJa · 10-12-05, 01:26 AM

The only thing I can think of is the -debugoutput switch, which has doctrines output some text.

This is probably only useful for detections and ai behaviour, though.

SCS' (single) missions have been pretty simple so far, so I believe they haven't used that many debugging techniques in the first place. I haven't examined the campaign missions yet though, but I believe Jamie spent considerable time on it - perhaps getting his attention

Myself, I'd like to see a C-like (heck, python?) scripting language, with the ability to output debug information - perhaps to the multiplayer chat window.

Though that may be delirious dreaming as far as SCS is concerned... That's not a small amount of work implementing that.

Doing it nwnx style isprobably be considered out of the question, for several (lots! lots!) reasons.

10-09-05, 11:14 PM	#1
Rob86TA Watch Join Date: Sep 2005 Posts: 21 Downloads: 3 Uploads: 0	Easy Debug of Missions? Is there an easy way to debug missions? A view or command line toggle that can give me a bit more of a description of what's actually happening? There's got to be a trick... there's no way Sonalysts does things my way. Which is to put a tonne of triggers in and watch their output. It works... but setting up the debug of a mission takes longer than actually designing it!

10-12-05, 01:26 AM	#2
MaHuJa Sonar Guy Join Date: Jan 2002 Location: 59.96156N 11.02255E Posts: 385 Downloads: 3 Uploads: 0	The only thing I can think of is the -debugoutput switch, which has doctrines output some text. This is probably only useful for detections and ai behaviour, though. SCS' (single) missions have been pretty simple so far, so I believe they haven't used that many debugging techniques in the first place. I haven't examined the campaign missions yet though, but I believe Jamie spent considerable time on it - perhaps getting his attention Myself, I'd like to see a C-like (heck, python?) scripting language, with the ability to output debug information - perhaps to the multiplayer chat window. Though that may be delirious dreaming as far as SCS is concerned... That's not a small amount of work implementing that. Doing it nwnx style isprobably be considered out of the question, for several (lots! lots!) reasons.