Monster wrote:So I believe I've found the reason why DirectQ was giving me a grey screen of death. After updating my video card drivers and updating directX drivers, I downloaded DirectQ 1.8.1 and installed it into a fresh quake folder, with nothing but the two .pak files. I loaded it up and it seemed to work fine.
When I was turning off all the cl_bob settings, cl_bobcycle 0 made the screen completely grey again. It seems anything above 0 fixes it. my autoexec.cfg and config.cfg files before had cl_bobcycle 0 in them, explaining why the screen was always grey until I did a fresh install.
So cl_bobcycle 0 seems to be my problem. oddly enough.
I noticed upon connecting to a server with a custom map I don't have, the engine crashes. Also it'd be nice to show the rankings at the end of a multiplayer game. The customize controls menu doesn't seem to respond to my mouse clicks, so I have to do a bind mouse1 "+attack" command in the console. It does, however, respond to mousewheel. Is there a way to adjust the size of the gun model? I'm on 1680x1050x32 resolution, using fov 110 and the gun model still looks quite big as compared to other engines like Darkplaces or Fitzquake.
I'm glad I finally discovered the reason for all my directq problems! Awesome engine. A timedemo of demo1.dem gives me 600 fps with 1.6 seconds. loving it so far.
Confirmed the same happens for me with cl_bobcycle 0 - I have something to test now!
I'll take your other suggestions (and required bugfixes) on board.