I'm running Vavoom 1.15Beta under Mandrake Linux 9.  Vavoom was built with default settings.  No known problems running Ultimate Doom, Doom 2, or Heretic under Vavoom with the -opengl command line option.  Also starting Hexen with Vavoom -opengl option.  Runtime settings are 1024x768, 16 BPP, all video options in video menu enabled (dynamic lighting, and the other three, whatever they are  ;) )<br><br>When I start the game as a Mage and shatter a stained-glass window with the wand, Vavoom abruptly ab-ends.  It leaves my system so unstable I can't control the mouse and must hard-reset  :-/<br>

I would like to withdraw this bug report because I have been unable to reproduce the bug since I took the following two steps:<br><br>- moved the Vavoom directory from /usr/local/games to my home directory<br>- ran glbsp and glvis on hexen.wad<br><br>Take care,<br>vaustein

It must be the glvis/glbsp run, moving the files to your home dir shouldn't have caused such a difference - a difference should've been there only in the case if the game wouldn't have run in /usr/local/games because of permission probs. Also, glbsp/glvis is automatically ran on all wadfiles in Vavoom Winblows version, pointing in the same direction.

Yep, there's no difference in permissions between /usr/local/games and home. The fact that system became unstable most likely means that Vavoom wasn't shut down properly and that might be because of some unhandled signal or exception.