This topic might get closed by a moderator, (well okay no, I see that everyone is responding supportively, but at least the title might need 'trimming'?) ...but I can totally, totally, TOTALLY sympathize, Mashek. I know exactly how you feel. A game that crashes is the most ruinous thing that can happen to a designer...
The first order of business is to delete all gates on your map and delete all the triggers on your map, save it as a "bugfix" version, and test. If it doesn't crash, you've narrowed it down a bit. Next put your gates back. No crash? Put half the triggers back. No crash? You're getting the idea, right?
By the way, what I mean by "put the gates back" and "put the triggers back" does not mean you have to re-do them all! Just go back to the crashing version of your game with all the triggers and gates, and only delete half the triggers.
And concerning the gates, I only suggest deleting the gates because in my experience if you have a SCX that you've been working on for a long time, gates start to "double up" and you get 10+ of them right on top of each other in the same location, and the only way to tell is that their shadow gets darker and darker. If you delete the gate once and it remains there, you've got a case of what I just described. If so, delete ALL the [stacked] gates and then put back just one.It's a looonnng, slow process to figure out what trigger is causing the crash, but it's what you gotta do if you're dedicated to this campaign.
Trust me I've done this on a giant map with over 1000 triggers, and I got to the bottom of it.
Good luck!
-Crasher-
[This message has been edited by crasher (edited 08-10-2006 @ 10:04 AM).]