View Issue Details

IDProjectCategoryView StatusLast Update
0001862FSSCP---------public2009-02-06 19:23
ReporterFUBAR-BDHR Assigned ToWanderer  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.6.9 
Summary0001862: Int3(): From e:\storage\fso\fs2_open\code\ai\aicode.cpp at line 5100
DescriptionI've run into the crash testing the Inferno build for TBP. I switched back to the latest Knightly build since the particular mission doesn't require Inferno and the crash still happens. It's one of those ones that doesn't seem to affect game play but I've seen them come back to haunt you later in a mission. It's happening in mission 13 of Drums of War. That's the second mission in DOW 3.

The mission is a red-alert mission but that doesn't seem to be the cause of it. I changed it to a standard mission with a briefing and it still crashes as soon as I hit commit. I spent all of last night trying to narrow it down starting with the obvious stuff but clear to removing entire events and wings of ships and it still happens. I've even gone through the mission in notepad looking for any corruption of the file. It's driving me nuts.

I'm going to continue to try to narrow it down.
Additional InformationRunning 3.6.10 both Inferno and the most recent Knightly builds.
TagsNo tags attached.

Activities

2009-01-02 23:57

 

fs2_open.log (26,562 bytes)

2009-01-03 01:01

 

DoW_13_pw.fs2 (57,254 bytes)

FUBAR-BDHR

2009-01-04 00:38

developer   ~0010503

I've spent all afternoon tearing apart that mission piece by piece. Of course it was the very last thing I could remove except for the player ship. Still absolutely no reason why it's happening but one ship is causing it. It's object #0 N'Dak 1 in the original mission. In the new mission I'm uploading it's NR Frazi 0. Set it's arrival to false and the mission runs. Set it to true and the mission crashes. I've compared it to other ships and even the same ship in other missions and don't see anything that should cause a problem.

2009-01-04 00:39

 

DoW_13.fs2 (3,582 bytes)

portej05

2009-01-04 12:04

reporter   ~0010505

Having a very quick spelunk - I can't for the life of me figure out how to get the mission to actually run!
Hopefully this saves someone else some time

ai_safety() function is finding aip->submode not being initialised to something that it expects (AISS_1, AISS_2, AISS_3) - safety mode

Without being able to run the mission, I can't track this down any further

2009-02-01 04:39

 

1862.fs2 (4,630 bytes)

FUBAR-BDHR

2009-02-01 04:40

developer   ~0010629

Attached mission compatible with FS2 data.

Wanderer

2009-02-03 09:53

developer   ~0010643

Last edited: 2009-02-03 10:05

Reason for the crash is indeed the ai_safety() function which in turn is caused by having $AI Behavior: Safety in the NR Frazi 0 ship. Basically game set the proper ai mode but it lacked proper (and seemingly mandatory) ai submode.

EDIT: It might be possible for this to happen with other mission file defined ai properties as well as it seems the missionparse only checks for 'behaviour' (later referred as 'mode') but the 'submode' is left untouched.

Wanderer

2009-02-03 13:43

developer   ~0010644

I committed a fix for this one... please try r5063 or later build.

FUBAR-BDHR

2009-02-05 02:23

developer   ~0010648

Just tried it with r5063 in both FS2 and TBP. No crash. Looks like another one for the resolved column.

Issue History

Date Modified Username Field Change
2009-01-02 23:57 FUBAR-BDHR New Issue
2009-01-02 23:57 FUBAR-BDHR File Added: fs2_open.log
2009-01-03 01:01 FUBAR-BDHR File Added: DoW_13_pw.fs2
2009-01-04 00:38 FUBAR-BDHR Note Added: 0010503
2009-01-04 00:39 FUBAR-BDHR File Added: DoW_13.fs2
2009-01-04 12:04 portej05 Note Added: 0010505
2009-02-01 04:39 FUBAR-BDHR File Added: 1862.fs2
2009-02-01 04:40 FUBAR-BDHR Note Added: 0010629
2009-02-03 09:53 Wanderer Note Added: 0010643
2009-02-03 10:05 Wanderer Note Edited: 0010643
2009-02-03 13:40 Wanderer Status new => assigned
2009-02-03 13:40 Wanderer Assigned To => Wanderer
2009-02-03 13:43 Wanderer Note Added: 0010644
2009-02-05 02:23 FUBAR-BDHR Note Added: 0010648
2009-02-06 19:23 Wanderer Status assigned => resolved
2009-02-06 19:23 Wanderer Resolution open => fixed