Originally Posted by FreonTrip
FitzQuake is my gold standard, but so far I really like this port. More thorough documentation about supported hardware and new command-line switches would be really great*, and there are still a couple of rough edges here and there+. But the color saturation and lighting are gorgeous, and the Direct3D implementation is sound and effective. Major kudos; I will keep an eye on this one!
* Does this work with any cards that don't support VS/PS 3.0 or higher?
+ In this case: there were a few moments when I could float just between water and its surface and see entities through world geometry (in this case, an ogre behind a door). Could theoretically be used as an exploit either in deathmatches or single player Quake. This was noticed in the Quoth Red777 map.
Good suggestions, and I'll deal with them in the docs for the next release. To answer your specific examples though, in the first case PS2.0 should be all that's needed, and that includes cards like the Intel 910/915 that don't even support vertex shaders in hardware. I'll be pulling back from the shader requirements over the next few versions, so hopefully after a few revs we'll be back to a stage where no shaders are needed at all.
Also, I've deliberately set things up so that almost all command-line switches are no longer necessary: -heapsize is gone totally, -width -height etc can be used but you don't need
them, -game can be used but you don't need
it, the 4 player cap is gone so you don't need -listen 16 anymore, and so forth.
The water bug is a GLQuake legacy, only way to really get rid of it is by re-vising your maps. I might be wrong here, and if there is a way it will be fixed.
For the black screen people - try setting a vid_mode of 0 in your config.cfg then work from there through the video menu and it should come good. I'm going to change the name of this cvar (but leave the old one there, just ineffective) in the next release as it seems to be causing all manner of grief by DirectQ picking up old values from people's configs and trying to set invalid modes at startup. I'm also going to change the default startup mode from fullscreen desktop res to 640x480 windowed so that first run will always pick up a mode that's guaranteed to work.