View Issue Details

IDProjectCategoryView StatusLast Update
0000391FSSCPgameplaypublic2005-05-12 09:03
ReporterWMCoolmon Assigned ToGoober5000  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Summary0000391: Crash resulting from GTT Fox docking with a station in Inferno
DescriptionIn the mission where the Soyuz defects, the GTT Fox is supposed to dock with an EA station and then detonate. However, it appears that once the Fox begins to start docking procedures, the game CTDs. I posted about this before, IIRC it's an indexing error and just requires playing through the mission with Microsoft Visual C++'s debugger to get the exact circumstances.
I have not tried destroying the transport (You're not supposed to). However, the mission (and thus, Inferno) isn't able to be completed if this bug is experienced.
TagsNo tags attached.

Activities

phreak

2005-05-01 19:57

developer   ~0002297

information: The offending function is ai_return_path_num_from_dockbay() it fails right away since dockee_index is set to -1. The current submode is AIS_UNDOCK_0, so something may be going awry in dock_find_dockpoint_used_by_object(goal_objp, Pl_objp);

Call stack:

debug_int3() line 889
ai_return_path_num_from_dockbay(object * 0x01504058 struct object * Objects, int -1) line 15728
ai_dock() line 11214 + 13 bytes
ai_execute_behavior(ai_info * 0x0325b4c8) line 13290
ai_frame(int 23) line 14428 + 9 bytes
ai_process(object * 0x01506f6c, int 23, float 0.0166473) line 14507 + 22 bytes
ship_process_post(object * 0x01506f6c, float 0.0166473) line 6687 + 29 bytes
obj_move_all_post(object * 0x01506f6c, float 0.0166473) line 1803 + 13 bytes
obj_move_all(float 0.0166473) line 2015 + 13 bytes
game_simulation_frame() line 5227 + 12 bytes
game_frame(int 0) line 5621
game_do_frame() line 6091 + 7 bytes
game_do_state(int 20) line 8026
gameseq_process_events() line 657 + 21 bytes
WinMainSub(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x00141f05, int 1) line 8561 + 5 bytes
WinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x00141f05, int 1) line 8610 + 21 bytes
WinMainCRTStartup() line 198 + 54 bytes
KERNEL32! 7c816d4f()

phreak

2005-05-01 20:07

developer   ~0002299

additionally the error occurs when the fox docks with Outpost 13

StratComm

2005-05-01 22:46

reporter   ~0002305

Last edited: 2005-05-01 22:49

Can someone attach the models in question (sounds like the Fox, not the stations)? This sounds like a model problem, and I'd be happy to look for anything amiss about the docks. Even if it doesn't solve the root bug, it might give you a better idea as to where to look.

edited on: 05-01-05 18:49

WMCoolmon

2005-05-03 07:24

developer   ~0002325

The Fox is an argo, the station is included in the Inferno R1 release, an EA outpost...one of the things that looks like a big silver coke can with a radar dish on top.

StratComm

2005-05-03 23:02

reporter   ~0002330

Last edited: 2005-05-03 23:03

Ok, I'll pull up the station then. I think Inferno is still around here somewhere...

And have you tried this without my multidock argo?

edited on: 05-03-05 19:03

Goober5000

2005-05-11 08:37

administrator   ~0002346

This may be the same as http://mgo.maxgaming.net/mantis/bug_view_page.php?bug_id=0000095. It's hitting an Int3() in the same place.

There may be some sort of carryover from previous dockings, as Trivial Psychic hypothesized.

Goober5000

2005-05-11 10:35

administrator   ~0002352

Okay, I'm virtually certain that fixing Trivial Psychic's bug (http://mgo.maxgaming.net/mantis/bug_view_page.php?bug_id=0000095) fixed this one too. Can someone download the latest CVS and confirm this?

Goober5000

2005-05-12 02:56

administrator   ~0002355

Assigning to Phreak to test this.

phreak

2005-05-12 04:02

developer   ~0002359

alrighty then i'll take a peek at this.

phreak

2005-05-12 04:17

developer   ~0002360

nope still getting a CTD in debug versions only.

Goober5000

2005-05-12 05:59

administrator   ~0002361

Latest CVS? Same place?

Goober5000

2005-05-12 09:03

administrator   ~0002363

You must not have the latest CVS. I just tested it and it ran perfectly fine. I hit some assertions where the AI tried to shoot down weapons that weren't bombs, but that's a different bug. I'm calling this fixed.

Issue History

Date Modified Username Field Change
2005-04-27 08:33 WMCoolmon New Issue
2005-05-01 19:57 phreak Note Added: 0002297
2005-05-01 20:07 phreak Note Added: 0002299
2005-05-01 22:46 StratComm Note Added: 0002305
2005-05-01 22:49 StratComm Note Edited: 0002305
2005-05-03 07:24 WMCoolmon Note Added: 0002325
2005-05-03 23:02 StratComm Note Added: 0002330
2005-05-03 23:03 StratComm Note Edited: 0002330
2005-05-03 23:03 StratComm Note Edited: 0002330
2005-05-03 23:03 StratComm Note Edited: 0002330
2005-05-11 08:37 Goober5000 Note Added: 0002346
2005-05-11 10:32 Goober5000 Status new => resolved
2005-05-11 10:32 Goober5000 Resolution open => fixed
2005-05-11 10:32 Goober5000 Assigned To => Goober5000
2005-05-11 10:32 Goober5000 Status resolved => feedback
2005-05-11 10:32 Goober5000 Resolution fixed => reopened
2005-05-11 10:35 Goober5000 Note Added: 0002352
2005-05-11 10:35 Goober5000 Status feedback => assigned
2005-05-11 10:37 Goober5000 Status assigned => confirmed
2005-05-12 02:56 Goober5000 Note Added: 0002355
2005-05-12 02:56 Goober5000 Assigned To Goober5000 => phreak
2005-05-12 02:56 Goober5000 Status confirmed => assigned
2005-05-12 04:02 phreak Note Added: 0002359
2005-05-12 04:17 phreak Note Added: 0002360
2005-05-12 05:59 Goober5000 Note Added: 0002361
2005-05-12 09:03 Goober5000 Status assigned => resolved
2005-05-12 09:03 Goober5000 Resolution reopened => fixed
2005-05-12 09:03 Goober5000 Assigned To phreak => Goober5000
2005-05-12 09:03 Goober5000 Note Added: 0002363