Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Silent Warrior on September 24, 2004, 03:37:18 pm

Title: Calamity! Wherein lies the problem?
Post by: Silent Warrior on September 24, 2004, 03:37:18 pm

As the crew in WCS knows, I have a bit of an issue with CTDs in recent exes. Since they occur in specific points in a mission, I'm tempted to think it's a problem with the .fs2, but everyone else appears to be able to run the missions with no problem whatsoever...
Cases in hand: My assigned work for WCS and the second mission in Just Another Day (just after a message along the lines of "Can we close the iris now?").

Specs:
ASUS P4T-E
P4 2GHz @ 2133 MHz (I, uh, password-locked the BIOS and forgot the password, so I can't change it. :o :o :o )
512 Mb RDRAM (Turbo and some other thing set to their default settings)
ATI Radeon 9700 Pro 128 Mb, Catalyst 4.9 (CTD also in 4.4)
Cordless Logitech iTouch
WinXP Home SP2 (CTD occurred in SP1 as well, for that matter)
SoundBlaster Live! Platinum 5.1

Anything else? Latest drivers all around even where it isn't noted.

Title: Calamity! Wherein lies the problem?
Post by: karajorma on September 24, 2004, 04:24:22 pm

Could it be that your tables are slightly screwed up and the mission itself is fine?

What happens when you run them through a debug build of FRED?

Title: Calamity! Wherein lies the problem?
Post by: Silent Warrior on September 25, 2004, 03:15:16 am

No problem at all in FRED. Well, no problem outside the already known issues with recent FRED2_Open releases, that is.

Title: Calamity! Wherein lies the problem?
Post by: karajorma on September 25, 2004, 03:48:31 am

Yeah but were you trying an actual debug build? I remember that MG worked fine in the normal FRED build but when I ran the tables though the debug build it took me an hour to correct all the little mistakes.

Title: Calamity! Wherein lies the problem?
Post by: Bobboau on September 25, 2004, 03:46:45 pm

and I know from Kazan WCS has a bunch of debug errors in it that you have refused to fix. this would be the sort of problem that would show up from this

Title: Calamity! Wherein lies the problem?
Post by: redmenace on September 25, 2004, 10:13:06 pm

Lol I think we need to incorporate the compiling rules into a table editor.

Title: Calamity! Wherein lies the problem?
Post by: Deepblue on September 25, 2004, 10:33:25 pm

I have this same CTD problem. For me it happens whenever a ship in my custom mission hits 0 hull integrity. This bug has been mentioned in Taylors release thread.

Title: Calamity! Wherein lies the problem?
Post by: redmenace on September 25, 2004, 10:56:01 pm

wrong thread.

Title: Calamity! Wherein lies the problem?
Post by: Silent Warrior on October 03, 2004, 04:01:55 am

Sorry for the delay - as I've said here and there, I'm not at home all that much these days. I'll run the missions through a debug-FRED ASAP.

Title: Calamity! Wherein lies the problem?
Post by: SadisticSid on October 04, 2004, 04:31:37 am

It's probably not the missions that are screwed, but the tables - Inferno had some pretty random issues with the SCP that Woo fixed by running them continuously through the debug FRED until there were no errors.

Title: Calamity! Wherein lies the problem?
Post by: Trivial Psychic on October 04, 2004, 01:06:58 pm

If you're talking about Inferno R1, then that was me and not Woo.  Check the readme with the patch.  R2 is all Inferno team though.

Title: Calamity! Wherein lies the problem?
Post by: SadisticSid on October 06, 2004, 04:34:05 am

No I was talking about R2 heh. No doubt R1 had loads of little problems as well though...