View Issue Details

IDProjectCategoryView StatusLast Update
0002585FSSCPgraphicspublic2012-01-25 09:41
ReporterYarn Assigned ToValathil  
PriorityurgentSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.6.14 RC3 
Summary0002585: 3D shockwaves cause crash
DescriptionWhenever a larger vessel explodes, FSO crashes if all three of these criteria are met:

1. The player is in the shockwave.
2. The exploding ship is not in view.
3. 3D shockwaves are used.
Additional InformationThe attached mission has everything set up for testing this bug. Once the mission starts, don't move. When the GTSC Shockwave explodes, the game will likely crash if 3D shockwaves are used.

This seems to have started in the October 22, 2010 Windows Nightly build.
TagsNo tags attached.

Activities

Yarn

2012-01-24 21:48

developer  

shockwavetest.fs2 (5,289 bytes)

The_E

2012-01-24 23:22

administrator   ~0013149

Please provide an fs2_open.log from one of those crashes. Attempts to reproduce it have not been successful so far.

Yarn

2012-01-24 23:37

developer  

fs2_open.log (38,321 bytes)

Yarn

2012-01-24 23:37

developer   ~0013150

OK, I have uploaded my log. Just in case this is OS-specific, I am running Windows 7 x64 Home Premium SP1.

Remember, when testing for this, you MUST have 3D shockwaves enabled, and you MUST use a mod that provides 3D shockwaves, like the MediaVPs.

chief1983

2012-01-25 05:33

administrator   ~0013153

Could the crash be due to the corruption fixed in 0002575? If so then this will be fixed in RC4.

Yarn

2012-01-25 06:10

developer   ~0013154

Last edited: 2012-01-25 06:11

I don't get graphical corruption from this, but these bugs could be related (or even the same bug).

To clarify criterion 2 above, the exploding ship must not be on or near the screen for the bug to trigger. If I am moving away but looking back at it, the game doesn't crash for me.

If this isn't fixed in RC4, then we may need to get user input from the forums.

Zacam

2012-01-25 09:41

administrator   ~0013156

This is resolved in Trunk (and has been backported to RC4) in revision 8294.

I made a local checkout of the RC Branch to the Build Stage Commit for RC3 and then I applied the Trunk revision change from 8294 and exhibited no issue.

Issue History

Date Modified Username Field Change
2012-01-24 21:48 Yarn New Issue
2012-01-24 21:48 Yarn File Added: shockwavetest.fs2
2012-01-24 23:22 The_E Note Added: 0013149
2012-01-24 23:37 Yarn File Added: fs2_open.log
2012-01-24 23:37 Yarn Note Added: 0013150
2012-01-25 05:33 chief1983 Note Added: 0013153
2012-01-25 06:10 Yarn Note Added: 0013154
2012-01-25 06:10 Yarn Note Edited: 0013154
2012-01-25 06:11 Yarn Note Edited: 0013154
2012-01-25 09:41 Zacam Note Added: 0013156
2012-01-25 09:41 Zacam Status new => resolved
2012-01-25 09:41 Zacam Resolution open => fixed
2012-01-25 09:41 Zacam Assigned To => Valathil