Crash On Map Change
HostileTarget
Join Date: 2003-09-20 Member: 21057Members, Constellation
Join Date: 2003-09-20 Member: 21057Members, Constellation
<div class="IPBDescription">Seems more stable but why does it crash?</div> <span style='color:red'>okay I found some info in another thread about it (search for nvidia) but it still doesn't say what is causing the crash. Looking for a technical answer.</span>
Now I know this is old news but I just want get the straight dope on this.
I'm talking about Natural Selection locking up on map change. Sounds start repeating, then windows will terminate the app. Horrible issue that I think has really hurt NS as a mod. Very few people are willing to play something that crashes on them every map change.
Now, I know everyone says it's because of Nvidia cards. And I mostly believe them since the Window's Application Error Log says this...
Description:
Faulting application hl.exe, version 1.1.1.1, faulting module nvoglnt.dll, version 6.14.10.5216, fault address 0x0016df41.
Now its possible that the error isn't actually in the nvoglnt module. I don't trust window's event log and I can't log NS into my Visual Studio debugger... But, assuming it is nvoglnt.dll, the question I'm asking is what went wrong? What is the operation that occurs that NVidia cards suddenly can't handle (where there was no issue prior to Steam).
Secondly, what hasn't a patch been released to fix 2.0? I've heard it works fine in 3.0 whats so hard about fixing 2.0? Hell I'd pay good money for a fix for 2.0 in the near future (cause I despise ATI and love NVidia).
On a side note, has anyone noticed that NS is slightly less crash prone now that the latest HL version was pushed out through steam? I mean I can almost go 3 maps without crashing now.
ps - If someone can give a more robust answer than "its nvidia cards" please web the answer for the rest of the world (err nvidia card owners).
Now I know this is old news but I just want get the straight dope on this.
I'm talking about Natural Selection locking up on map change. Sounds start repeating, then windows will terminate the app. Horrible issue that I think has really hurt NS as a mod. Very few people are willing to play something that crashes on them every map change.
Now, I know everyone says it's because of Nvidia cards. And I mostly believe them since the Window's Application Error Log says this...
Description:
Faulting application hl.exe, version 1.1.1.1, faulting module nvoglnt.dll, version 6.14.10.5216, fault address 0x0016df41.
Now its possible that the error isn't actually in the nvoglnt module. I don't trust window's event log and I can't log NS into my Visual Studio debugger... But, assuming it is nvoglnt.dll, the question I'm asking is what went wrong? What is the operation that occurs that NVidia cards suddenly can't handle (where there was no issue prior to Steam).
Secondly, what hasn't a patch been released to fix 2.0? I've heard it works fine in 3.0 whats so hard about fixing 2.0? Hell I'd pay good money for a fix for 2.0 in the near future (cause I despise ATI and love NVidia).
On a side note, has anyone noticed that NS is slightly less crash prone now that the latest HL version was pushed out through steam? I mean I can almost go 3 maps without crashing now.
ps - If someone can give a more robust answer than "its nvidia cards" please web the answer for the rest of the world (err nvidia card owners).
Comments
Faulting application hl.exe, version 1.1.1.1, faulting module d3dim.dll, version 5.1.2600.0, fault address 0x00011aad.
Now about the 2.0 fix .... nah ... you'll be seeing 3.0 soon ... and I use custom skins in the beta and don't get any problems ... so I guess what should be fixed .. is fixed...
If you aren't using custom skins ... I really don't know what to say