I've minimized the game, then maximized it but all I got was black screen. I minimized again and saw crash report with submit/cancel options. I pressed cancel, maximized and... I could continue playing!
Here's tech support generated file. It happened somewhere after biodome loaded (or maybe after first match), I accidentally alt tabbed, trying to speak and watch scoreboard >_<
If I recall correctly, error window title said 'spark engine error' or something close to that.
I didn't notice any issues after that.
Is mesh cooking ok in the middle of the game? EDIT: I was alien that time, crash happened before that.
Degriz(муж Makzo killed Demozor with Bite
Chat All - Stas: shaman gawiw eto nexorosho
Chat All - Stas: u ty gluki))
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 16 faces, 10 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 16 faces, 10 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Cooked mesh with 4 faces, 4 vertices
Kano killed HentaiKO with Rifle
Degriz(муж Makzo killed Extractor with Bite
ArcKi killed Stas with Bite
Pichenka killed Extractor with Bite
DC_DarklingJoin Date: 2003-07-10Member: 18068Members, Constellation, Squad Five Blue, Squad Five Silver
You playing in windowed mode? if not I strongly advice against alt/tab.
When a program is to busy to give UI feedback it 'freezes'. It can either truly crash (rare) or be very very busy.
If you start clicking when the program is to busy to accept the ui clicks then windows will assume it crashed, not busy.
If windows thinks it crashes it calls upon the standard crashdump mechanic. (I am unsure if the mechanic for ns2 specificly counts)
If for some reason it gets response windows will again be happy.
I assume your crash was something similar. Im unsure though because in my experience it calls upon dr watson. (windows crash dump mechanic). But perhaps it checks first if the program itself has a crash dump mechanic.
Lotta assumtion here. I guess the info we need is in the dump itself
Comments
Anything weird happen post "crash"
If I recall correctly, error window title said 'spark engine error' or something close to that.
I didn't notice any issues after that.
When a program is to busy to give UI feedback it 'freezes'. It can either truly crash (rare) or be very very busy.
If you start clicking when the program is to busy to accept the ui clicks then windows will assume it crashed, not busy.
If windows thinks it crashes it calls upon the standard crashdump mechanic. (I am unsure if the mechanic for ns2 specificly counts)
If for some reason it gets response windows will again be happy.
I assume your crash was something similar. Im unsure though because in my experience it calls upon dr watson. (windows crash dump mechanic). But perhaps it checks first if the program itself has a crash dump mechanic.
Lotta assumtion here. I guess the info we need is in the dump itself