This was discussed a couple months ago, but I can't find the thread.

When I close Nexuiz, it freezes for about 20 seconds and then gives an error message saying the program crashed. It does this every time (on Windows).

I knew that some other players experienced the same problem. I don't remember if I've had this problem on other computers, but I think I have.
I use this laptop
http://www.amazon.com/HP-Pavilion-zd705 ... B0009M18H8

which uses a NVIDIA GeForce FX Go5600

Someone had asked for the event log entry for the crash.


-----EVENT VIEWER - APPLICATIONS------
Faulting application nexuiz.exe, version 1.0.0.0, faulting module nvoglnt.dll, version 6.14.10.4482, fault address 0x001b14d8.
-----------------------------------------

Hope that helps

Dokujisan wrote:-----EVENT VIEWER - APPLICATIONS------
Faulting application nexuiz.exe, version 1.0.0.0, faulting module nvoglnt.dll, version 6.14.10.4482, fault address 0x001b14d8.
-----------------------------------------

nvoglnt.dll is part of the nvidia OpenGL driver. The crash occurs in the driver, not the engine. Strictly speaking it's not a Nexuiz crash.

Trying out a newer driver may help (albeit hunting down drivers for mobile graphic devices often is a pain in the...).

SavageX wrote:nvoglnt.dll is part of the nvidia OpenGL driver. The crash occurs in the driver, not the engine. Strictly speaking it's not a Nexuiz crash.

Trying out a newer driver may help (albeit hunting down drivers for mobile graphic devices often is a pain in the...).

Padraig sent me a backtrace for such a crash a while ago. According to that, the crash occurs in the driver when glDeleteTextures is called on shutdown, but according to the OpenGL specs, that function is not allowed to crash

Serious question - what hell would break loose when NOT deleting the textures on shutdown?

SavageX wrote:

Dokujisan wrote:-----EVENT VIEWER - APPLICATIONS------
Faulting application nexuiz.exe, version 1.0.0.0, faulting module nvoglnt.dll, version 6.14.10.4482, fault address 0x001b14d8.
-----------------------------------------

Trying out a newer driver may help (albeit hunting down drivers for mobile graphic devices often is a pain in the...).

A pain in the what?
I'm sorry, but you didn't finish your sentence.