Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Lightspeed on January 17, 2004, 03:05:32 pm

Title: Weird Crashes
Post by: Lightspeed on January 17, 2004, 03:05:32 pm: I've been playing this campaign (http://www.geocities.com/noiseball2000/itdoh.html) (chapter 1, no MODs) and experienced an unusual lot of crashes in some missions, untill mission OFF.fs2 - which crashes every single time I try it. It opens fine in FRED though and doesnt seem to have any obvious bug.

The crashes happen randomly in the game, most of the times 30 secs - 2 mins from mission start.

So I was getting annoyed and tried the debug build and I got this error:

Code: [Select]
Assert: pm->n_paths > path_num File: E:\Languages\Visual Studio Projects\Visual C++\fs2_open\code\Ship\AiCode.cpp Line: 3785 Call stack: ------------------------------------------------------------------ ai_big_maybe_follow_subsys_path() ai_big_strafe_attack() ai_big_strafe() ai_execute_behavior() ai_frame() ai_process() ship_process_post() obj_move_all_post() obj_move_all() game_simulation_frame() game_frame() game_do_frame() game_do_state() gameseq_process_events() WinMainSub() ------------------------------------------------------------------

When I tried again the whole debug build crashed and I found this in my errorlog:

Code: [Select]
12_05_2003_FS2_OPEN_D caused an Access Violation in module 12_05_2003_FS2_OPEN_D.EXE at 0177:00444dae. Exception handler called in Freespace 2 Main Thread. Error occurred at 1/17/2004 21:57:44. C:\GAMES\FREESPACE2\12_05_2003_FS2_OPEN_D.EXE, run by Lightspeed. 1 processor(s), type 586. 511 MBytes physical memory. Read from location 4077f090 caused an access violation.

Anyone got a clue what this is, or why it happens?

I've never had any similar problems before :(
Title: Weird Crashes
Post by: Lightspeed on January 17, 2004, 07:27:37 pm: I've tested some more and it doesnt seem to happen with any other MODs or the standard campaign.
Title: Weird Crashes
Post by: karajorma on January 18, 2004, 05:24:24 am: That first error looks like an assertion problem being caused by something to do with the pathing on a model.

Looks like one of the ships has a dodgy path to me but until I actually learn C I'll have to leave it to the experts to puzzle this one out.

EDIT : Which chapter are you playing? Maybe I can look at the ships in question and see if I can spot a problem there. Take a look in FRED and see if any of the new ships are being disarmed, docked or disabled as that can cause crashes in ships that haven't been properly pathed.
Title: Weird Crashes
Post by: Lightspeed on January 18, 2004, 05:58:46 am: there are no new ships. It's using no mods.

Quote

... I've been playing this campaign (chapter 1, no MODs) and experienced ...
Title: Weird Crashes
Post by: WMCoolmon on January 18, 2004, 01:23:23 pm: Is the level designer trying to dock more than one ship to something, or dock a ship to something without a dockpath? I'm not really an expert but that's what it looks like the error could be caused by.
Title: Weird Crashes
Post by: Lightspeed on January 18, 2004, 02:12:13 pm: no idea, but I can have a look in FRED.
Title: Weird Crashes
Post by: Noise on January 18, 2004, 05:41:36 pm: As the author of this campaign the only problem I can see it being is that there are simply too many ships for the computer to handle, or too much going on. The mission in question is very heavy in detail, quite possibly the largest mission I've ever made. If anything, I guess the problem is with the size of the mission, that's my guess at any rate. But I have run it countless times on my computer and it runs fine and from what I've been told, others have played it as well without errors. Confusing indeed.
Title: Weird Crashes
Post by: Lightspeed on January 19, 2004, 06:51:49 am: I've had missions with at least 3 times the ships working fine before.