[Goober5000]

There's nothing wrong with the mission - it plays perfectly fine on my computer and on other people's computers.  But some people have reported crashes like this.

Maybe different versions of FS1 have different sexp limits? What happens if you use this EXE?

[Goober5000]

AUGH!  I figured out what the problem is. Karajorma's going to love this.

Simple fix for the bug: Drop the attached campaign file in the missions folder and play it via the campaign room instead of the tech room.  (I'll upload a revised VP to the website shortly.)

Simple explanation of the bug: The game was running out of sexp nodes.

More complicated explanation: As with most ugly bugs, the symptom looked rather different than the root cause.  And the worst thing is that it happened to some people but not others.  The reason is that sexp nodes are shared between campaigns and missions.  If you have a complicated campaign in memory, it may not leave enough sexp nodes for the mission.  Playing the mission via a campaign ensures that the mission starts with a known number of free sexp nodes.

If I didn't have the source code on hand, I would have never figured this out.

[karajorma]

That's a rather interesting bug.

I might have problems with it but the one who's really going to get screwed by this one is ShadowWolf's Mercs campaign.

[JoeLo]

Hmmm now I get this error
Error: Couldn't open mission 'Ross128.fsm'

File:D:\PROJECTS\FREESPACE\Mission\MissionParse.cpp
Line: 3440

Call stack:
------------------------------------------------------------------
------------------------------------------------------------------
Could it be that I am running the Euro version Conflict Freespace?

[Goober5000]

Hrm.  Open the campaign file and rename "Ross128.fsm" to "FOW-Ross128.fsm".