SEXP Debugging - Revision history

TopAce: +category

2021-07-02T07:28:45Z

+category

← Older revision		Revision as of 07:28, 2 July 2021
Line 23:		Line 23:

	This should be able to be set for the event using FRED.		This should be able to be set for the event using FRED.

			[[Category:FRED Tips]]

Niffiwan at 06:28, 30 May 2014

2014-05-30T06:28:39Z

← Older revision		Revision as of 06:28, 30 May 2014
Line 1:		Line 1:
	This is a quick intro to SEXP debugging, based on the [http://www.hard-light.net/forums/index.php?topic=85174.0 event log feature] added by karajorma (and the linked post).		This is a quick intro to SEXP debugging, based on the [http://www.hard-light.net/forums/index.php?topic=85174.0 event log feature] added by karajorma (and the linked post).

	{{Note: requires FSO 3.7.0 or later }}		{{Note\|requires FSO 3.7.0 or later}}

	== Option 1: Snapshot all events ==		== Option 1: Snapshot all events ==

Niffiwan at 06:27, 30 May 2014

2014-05-30T06:27:45Z

← Older revision		Revision as of 06:27, 30 May 2014
Line 1:		Line 1:
	This is a quick intro to SEXP debugging, based on the [http://www.hard-light.net/forums/index.php?topic=85174.0 event log feature] added by karajorma (and the linked post).		This is a quick intro to SEXP debugging, based on the [http://www.hard-light.net/forums/index.php?topic=85174.0 event log feature] added by karajorma (and the linked post).

			{{Note: requires FSO 3.7.0 or later }}

	== Option 1: Snapshot all events ==		== Option 1: Snapshot all events ==

Niffiwan: /* Option 2: Watch specific events */ update based on MageKing17's use in HFH test mission

2014-05-30T06:25:46Z

Option 2: Watch specific events: update based on MageKing17's use in HFH test mission

← Older revision		Revision as of 06:25, 30 May 2014
Line 17:		Line 17:
	This needs to be configured ahead of time. It gives the FREDder another option to write a state change. If you tell FS2 to log whenever an event comes true, the event log will also write out the state of the event in the previous frame.		This needs to be configured ahead of time. It gives the FREDder another option to write a state change. If you tell FS2 to log whenever an event comes true, the event log will also write out the state of the event in the previous frame.

	~~Yeah~~, ~~I'm not actually sure how to~~ add this to ~~sexp's. Maybe this~~:		To configure this, add this to the end of a given event:

	~~<nowiki>MjnMixael~~: ~~but basically in the event viewer~~, ~~you can mark events to be logged.</nowiki>~~		'''+Event Log Flags: ( "true" )''' (or "false", or both)

	~~Anyway, more details from someone with more knowledge on this than me would~~ be ~~superuseful! :)~~		This should be able to be set for the event using FRED.

Niffiwan: quick data dump about the event.log - mostly based on the linked forum post

2014-05-30T04:26:22Z

quick data dump about the event.log - mostly based on the linked forum post

New page

This is a quick intro to SEXP debugging, based on the [http://www.hard-light.net/forums/index.php?topic=85174.0 event log feature] added by karajorma (and the linked post).

== Option 1: Snapshot all events ==

How to take a snapshot of the events in the game.

If you are having problems with a mission, rather than asking for a debug log, you may be asked for a snapshotted event log. You can get hold of it like this.

# If you are running a debug copy of FS2_Open, you can skip this step. Otherwise, enter the FS2_Open cheat code www.freespace2.com to activate cheat mode.
# Wait until the problem occurs and then press ~ (Above space on most keyboards) and Q at the same time.
# When you exit the game look in your Freespace2/Data folder for a file called event.log. If you are running a mod, you will find the file in Freespace2/Mod Name/Data instead. If you are running a game other than Freespace2 (Diaspora, TBP, etc) you will find the file in that game's data folder (e.g Diaspora/Data).
# Post here on HLP and attach the log to your post.

== Option 2: Watch specific events ==

This needs to be configured ahead of time. It gives the FREDder another option to write a state change. If you tell FS2 to log whenever an event comes true, the event log will also write out the state of the event in the previous frame.

Yeah, I'm not actually sure how to add this to sexp's. Maybe this:

<nowiki>MjnMixael: but basically in the event viewer, you can mark events to be logged.</nowiki>

Anyway, more details from someone with more knowledge on this than me would be superuseful! :)