nexuiz-sdl.exe crash

[AnArKiSt]

I've been using Nexuiz sdl, because my mouse never moves right in glx. It moves more responsivly in sdl.

During a match played in fullscreen, and with r_showsurfaces 3 enabled to maximize performance, the Nexuiz game window closed for a reason unknown to me, and the process nexuiz-sdl.exe remained running on my machine. See below:



No error message, no complaining, the game window just vanished, and my desktop returned to it's normal screen resolution.

Thanks for reading.

[AnArKiSt]

*BUMP*

I'm still waiting for a fix here.

Nexuiz-SDL runs like the OpenGL version but with reduced input lag on my machine, however it crashes shortly after a new map loads.

It should be noted that even after nexuiz-sdl.exe crashes in this manner, its process remains running in the background and uses a small amount of system resources.

[LordHavoc]

What video card? Usually it's a driver issue.

I'm not sure why it would continue running, but it sounds like it was trying to clean itself up after a crash and got stuck before it could fully quit, so most resources were freed but not all.

Side note: I think you mean WGL (Windows OpenGL) not GLX (GLX is a Linux thing).

[AnArKiSt]

Sorry about the really late reply.

My graphics hardware is called "ATI Radeon Xpress 1270"

[LordHavoc]

Sorry about the really late reply.

My graphics hardware is called "ATI Radeon Xpress 1270"

In my experience this happens when the graphics context is destroyed by the OS for some reason - typically to do with video driver being reset for some reason or another, usually a form of driver crash (which may or may not be related to overheating).

A typical case is a graphics card overheating and then the driver is reset (causing the screen to go black for an instant and then windows reappearing one by one) by the Vista/Windows 7 kernel to keep the system usable

In your case I do not know what is going on, but the symptoms are consistent with my own experiences with Vista video driver crashes and the kernel recovering from it.

One weird workaround you can try (and I've had this work!) is this one:
Click the still-running game on the taskbar, no window pops up.
Blindly type: `vid_restart<enter>
If it fails, try a few times until it is typed correctly, when you get it right it tends to spring to life in a new window exactly where you were.