View Issue Details

IDProjectCategoryView StatusLast Update
0002599FSSCPgameplaypublic2012-04-03 13:16
Reporterjon118 Assigned ToEchelon9  
PriorityhighSeveritycrashReproducibilitysometimes
Status closedResolutionfixed 
PlatformIntel-based MacOSOSXOS Version10.6.8
Product Version3.6.14 RC4 
Summary0002599: Game often permanently freezes during combat, possibly because of targeting code
Description
Game often freezes solid and won't unfreeze during combat in stock FS2 missions.

This is basically a crash, but the game will not exit on its own (even if you wait 30 minutes for it to exit) and the sounds will continue playing until you force it to exit.

This can (and will) happen in any mission as far as I can tell.

The frequency of freezes is about once every three to five missions played--whether the same mission is played more than once, or several different missions are played, doesn't seem to matter.

I've recorded detailed logs in the debug build and taken a screenshot during each freeze at the *exact* moment of the freeze.

The only common feature of each freeze that I've noticed appears to be that in each case I am just bringing the targeting retical onto another ship at the exact moment of the freeze. And in each case this has been after several minutes of battle.

The freeze is somewhat random, but will almost always happen before I've completed more than 6 missions.

Nothing that unusual seems to be recorded in the logfile at the moment of the freeze.

I never experienced this freeze in 3.6.12 builds, and could always play all 30-some missions without the game ever crashing or freezing.

I've ruled-out overheating issues, as the graphic card is not getting much over 110 degrees Fahrenheit (43 c).

I've tested this on the 3.6.14 RC4 build, as well as the 3.6.14 SVN 8436 trunk build from two days ago.


Steps To Reproduce
The only way I know to reproduce this bug is to simply play stock combat missions until it happens. But it happens very often, and is therefore not that hard to reproduce. less than 30 minutes of play should be sufficient in most cases.

The only common feature of each freeze that I've noticed appears to be that in each case I am just bringing the **TARGETING RETICAL ONTO ANOTHER SHIP** at the exact moment of the freeze. And in each case this has been after several minutes of battle.

The freeze is somewhat random, but will almost always happen before I've completed more than 6 missions.

In many cases, I was using "Harpoon" missiles in dual fire, and "Subach HL-7" lasers in dual fire. But I don't think that is related, as I wasn't always firing at anything.
Tagscombat, crash, freeze, retical, target, targeting

Activities

jon118

2012-02-07 16:01

reporter  

freeze1.zip (847,656 bytes)

jon118

2012-02-07 16:01

reporter  

freeze2.zip (699,764 bytes)

jon118

2012-02-07 16:01

reporter  

freeze3.zip (656,040 bytes)

jon118

2012-02-07 16:05

reporter   ~0013243

Note, in the attached file "freeze3.zip" I recorded an in-depth debug log during the freeze/crash using the "debug_filter.cfg" file with all options turned on except for "-Parse".

Yarn

2012-02-07 19:30

developer   ~0013244

Try playing in a window (use the -window flag and a lower resolution), and play until you get this crash again (with the debug build, of course). When the game crashes, look for any error messages (you might have to minimize the window to see them). Post them here if you see any.

Zacam

2012-02-07 20:12

administrator   ~0013245

I doubt there will be any error messages per-se as those would already be logged regardless of if windowed or not.

I know that the 320M is not a beefy video chip. Try removing MV_Advanced and MV_AnimGlows (additionally, -height doesn't currently do anything)

jon118

2012-02-08 15:14

reporter   ~0013257

Last edited: 2012-02-08 15:21

I'll try that, though, as I mentioned, I have been able to play through all missions with all graphics maxed-out without a single problem on 3.6.12 with all the same textures loaded. (It never slows down below 25 fps on my 320m, even with everything maxed) So I am doubtful that the graphics settings or textures are the cause--unless 3.6.14 handles those (glows etc.) very differently.

Could anyone with a Mac and a more beefy graphics card care to play a few stock missions (at least for 30 minutes)? If it doesn't permanently freeze solid for you also, I'd be very surprised.

MjnMixael

2012-02-08 15:44

manager   ~0013258

I.. am actually fairly certain I encounter the same issue. I'll have to pay more attention though.

Echelon9

2012-03-04 13:23

developer   ~0013386

I've played a considerable amount (>30mins) this weekend, on Mac, and haven't encountered this bug yet.

Echelon9

2012-04-03 13:15

developer   ~0013445

Unable to reproduce.

Issue History

Date Modified Username Field Change
2012-02-07 15:52 jon118 New Issue
2012-02-07 16:01 jon118 File Added: freeze1.zip
2012-02-07 16:01 jon118 File Added: freeze2.zip
2012-02-07 16:01 jon118 File Added: freeze3.zip
2012-02-07 16:02 jon118 Tag Attached: crash
2012-02-07 16:02 jon118 Tag Attached: combat
2012-02-07 16:02 jon118 Tag Attached: freeze
2012-02-07 16:02 jon118 Tag Attached: retical
2012-02-07 16:02 jon118 Tag Attached: target
2012-02-07 16:02 jon118 Tag Attached: targeting
2012-02-07 16:05 jon118 Note Added: 0013243
2012-02-07 19:30 Yarn Note Added: 0013244
2012-02-07 20:12 Zacam Note Added: 0013245
2012-02-08 15:14 jon118 Note Added: 0013257
2012-02-08 15:16 jon118 Note Edited: 0013257
2012-02-08 15:21 jon118 Note Edited: 0013257
2012-02-08 15:44 MjnMixael Note Added: 0013258
2012-02-24 09:15 Echelon9 Assigned To => Echelon9
2012-02-24 09:15 Echelon9 Status new => assigned
2012-03-04 13:23 Echelon9 Note Added: 0013386
2012-03-04 13:23 Echelon9 Status assigned => feedback
2012-04-03 13:15 Echelon9 Note Added: 0013445
2012-04-03 13:15 Echelon9 Status feedback => closed
2012-04-03 13:16 Echelon9 Resolution open => fixed