Crash on startup

[Sgt-PieFace]

So I just upgraded my monitor, and now when I launch either proquake or darkplaces, I get an error.

Proquake error says Couldn't set fullscreen DIB mode, and darkplaces says video modes failed.

My old monitor was running at 1280 X 1024 @ 62 Hrz. My new one is running at 1920 X 1080 @ 60 Hrz.

I have already tried reinstalling both clients, and tried to force them to run in 640 in the compatibility window, with no results.

Any help would be appreciated

[R00k]

try running -native on the commandline? this will force the resolution to the desktop, if those two engines support it; GlQuake did.



ie

"c:\quake\glProquake.exe -mem 64 -noforcemparms -native"

[Cobalt]

Sounds like the Video card cant support that higher resolution. Kick the desktop res back down to your old resolution, then try higher modes from there.

[Sgt-PieFace]

Fixed

So I was talking to Dee-Killah, and he said something about the aspect ratio. I checked AMD CCC and found out that by default, the new monitor couldn't display anything other than 1080p and 720p. I changed that, and it worked.

Thanks for the replies everybody!

[Mindf!3ldzX]

open the config file, and search for vid , they will be vid_height and vid_width
change the resolutions to match your desktop resolution

or (last resort)

try deleting/moving the respective config file for each client, but make sure you copy paste it somewhere else first, this will force the client to recreate a new config file, but will also force you into having to setup config again, which suxorz.

if you have to do this, you can edit the config file before deleting/moving and toss the relevant configuration settings into an autoexec.cfg and just retain/add that file whenever you have to do a new setup.

I got so tired of losing my configuration , that I just permanently now manually make a autoexec.cfg everytime

[Mr.Burns]

Hi Pie ;-)
I wonder if the new monitor is able to run at the lower res settings. Which settings have you tried other than the 640?
As I recall, and I could be wrong about this, that message suggests that the engine tried to launch Quake at a resolution that your display does not support. You could look at your settings, either in the command line or the config and try resetting them to something your new display is more comfortable with.

Kind regards
Monty