When using V1.18 with the new model pack, Vavoom95.exe works fine in the software renderer. However, if run with the -opengl parameter, the game locks up when any monster comes into view. Does not happen with non-moving animated things like barrels and armour helmets etc, only monsters. The music still plays, but nothing else works. It also leaves the screen with the Vavoom display; so if you CTRL-ALT-DEL to kill vavoom, you can't see the CTRL-ALT-DEL window (or anything else but Vavoom), which means you must reset or power-cycle the computer in order to regain control of it. Sometimes you can be lucky to type a command by dead reckoning: eg Start|run|cmd.exe <return> <alt-enter> which runs then maximizes a shell window then exit the shell and the desktop gets repainted as normal. In other words, the rest of Windows is still working, but you just can't see it, because Vavoom hasn't exited properly and is still running while locked up. For the record, this is Windows XP Pro SP2 with an ATI mobile Radeon 7500. Other details can be given on request. EDIT: This has also happened in GZDoom, but only once so far; with Vavoom it happens every time. It's gotta be an OpenGL driver problem, but I am using the latest ATI driver, so not sure what. I wonder if Vavoom could someday incorporate some sort of watchdog timer?

It could be a driver related problem, but I'm not quite sure of it...

Direct3D works fine (don't know why anyone would use the software renderer)... OpenGL does make the program lock up... not a coincidence...

I'm able to run both Direct3d and OpenGL, I suppose that you have an ATI card too Deathlike, or am I wrong??

Yes.. I use an ATI Radeon 9800 Pro using the latest CATALYST driver (5.10)... My assumption is Vavoom is the problem for the most part...

I don't have any problems with OpenGL, byt, unlike you, I have nVIDIA GeForce6600 GT. And I won't even consider bying an ATI card because I'm using Linux and I've heard that their Linux drivers are very bad. Anyway it's strange, because Vavoom uses standard OpenGL features. BTW does it lock up if you disabe models?

I have another system with an NVidia Geforce 6600... and it seems fine with that. I don't know how to disable models (heck, the documentation isn't very good at all) but I moved the models folder that was created when I got the models pack.. and it worked fine in OpenGL (didn't lock up).. so it has something to do with how the models interface with OpenGL when using an ATI video card.

Judging by the stuff that's happened with OpenGL for ATI cards in the GZDoom forums, I believe this to be an issue with the latest drivers from ATI. Someone over there said that they didn't have a bunch of problems, but they were using older drivers. I think ATI somehow managed to totally screw up OpenGL with the latest Catalyst drivers. To be honest, you shouldn't really be using OpenGL with ATI cards anyway, they work best with DirectX (a option which Vavoom has <!-- s;) --><img src="{SMILIES_PATH}/icon_wink.gif" alt=";)" title="Wink" /><!-- s;) -->).

Judging by the stuff that's happened with OpenGL for ATI cards in the GZDoom forums, I believe this to be an issue with the latest drivers from ATI. Someone over there said that they didn't have a bunch of problems, but they were using older drivers. I think ATI somehow managed to totally screw up OpenGL with the latest Catalyst drivers.

I don't think that new drivers have the best chance of breaking stuff (not that they cannot... then again, I don't use the Vavoom port of Doom as much.. I prefer the Doomsday port and it works JUST FINE in OpenGL) I acknowledge that ATI does have OpenGL driver implementation problems... and it still needs tweaking... but that doesn't mean you blame it totally on ATI for these lockups... I'm in the belief that the devs need to report problems to ATI and NVidia... (on the flip side, I hear more problems with NVidia with their Direct3D drivers...)

That's prety strange, since models are rendered the same way glQuake does it. Probably ATI drivers are more optimised for vertex arrays.

This seems to be resolved in the CATALYST 5.13... though I'm not sure if it works with the 5.11 or 5.12 (I'm not downgrading to test this anytime soon)