"Couldn't set fullscreen DIB mode" in QRack AND ProQuake 3.95 but not ProQuake 3.50

[BizarroMonkey]

You heard it here. I can't start Qrack or ProQuake 3.95 because that error message pops up before going into fullscreen mode. Anyone seen this?

It happens in GL and D3D ProQuake 3.95's. On an unrelated note, WinProQuake 3.95 crashes before it gets in game too, but not for the same reason.

My specs are:
Newest NVIDIA drivers
Intel Core 2 Q6600
8800GT
WinXP SP2 (pretty fresh install)

[R00k]

try -current (in Qrack) or -dibonly (for both), which is a safe measure to startup the engine. From there you can set the resolution from within the options menu.


oh btw Hi monk long time no see ;P

[PapaSmurf]

-dibonly works for GL engines as well?

[Baker]

Hey Monkey, try use ProQuake 3.98 or higher (download 3.99b).

I made a change in 3.98 that should immune against that error message.

3. I made a change that I hope will eliminate that that "Can't set full screen dib mode" message on certain laptop displays that don't support 60 hz. I don't have any way of testing this directly, but I'm pretty confident it works because I tried to simulate a situation where an error would occur --- but still, I need to get verification.

Monkey, let me know if using 3.98 or higher resolves the situation. I don't experience the error firsthand, but I did some tests to simulate it, but I still need verification.

Thanks for your feedback.

/Note to Rook: this seems to be the offending code in Qrack. vid_refreshrate defaults to 60 and this code forces the engine to use the cvar value if it is less than 60, but not all displays support 60 hz refresh rates.

#if 0
// Baker 3.97: Rook uses this and appears to be related
// to "Full screen dib issue".

if (vid_refreshrate.value > 59)
{
gdevmode.dmDisplayFrequency = modelist[modenum].refreshrate = vid_refreshrate.value;
gdevmode.dmFields |= DM_DISPLAYFREQUENCY;
}
else
#endif

[R00k]

ahh, true some modes are below 60!

[Baker]

ahh, true some modes are below 60!

Opposite actually

Case in point:

Quazy's laptop that has this problem is 115hz.

The code says use the vid_refreshrate value (it's gonna be 60 when first starting Qrack after a download, because vid_refreshrate default = 60) and that code says to use the cvar value if the cvar value is >59. And the default value is >59.

So it's going to use 60 on first startup. But if your monitor only supports, say, 115hz and nothing else that's going to generate "Can't set fullscreen dib mode".

If you comment that code out, it checks the mode list and uses the refresh rate from that. The code I quoted above, it isn't checking to see if the refresh rate is available in the mode list, it's just setting it without knowing whether or not it's valid.

[BizarroMonkey]

Oh yah, I actually used a refresh rate fixer utility to get my refresh rates up in games. And believe me, it's WAY smoother on my CRT with a 120hz refresh in Quake .

Turning vsync off and getting 120hz is the best way to go in quake, imho.

[BizarroMonkey]

Oh and 3.99b ProQuake works great without any extra command lines or anything. Qrack also works fine with -current in command line. Thanks for the help eh.

Indeed, long time no see r00k. I see you on servers sometimes though . You should drop by the channel from time to time, #bizarroteam.

[Baker]

Excellent. Thanks for the feedback on that.

[BizarroMonkey]

Oh yah, I did see graphical issues with QRack though. Wondered if anyone else has seen this before. Weird colors and some box at the bottom left that was different colored at all times.

[R00k]

It looks like your gfx card doesnt like the bloom feature,
Its only rendering the bloom over that part of the screen.