Proquake 4.51 - Cannot get 1920x1080 to run at 60 HZ refreshrate

[vis]

For some reason on my pc here, I cannot get it to run at 1920x1080 at 60 hz. It will only run at 50 hz. This is not the case for Qrack or other clients. I also have the problem of when making any adjustments inside Video options within Proquake and then hitting 'Apply Changes' - NOTHING happens. I've also tried going to the console and making the neccessary command changes like - vid_refreshrate 60 or doing a vid_restart, etc. and nothing happens. Do you know why this is the case?

I can get Proquake to run at 1366x768 at 60 hz, but not at higher resolutions such as 1920x1080 (which my monitor was designed for).

My specs are:

Core i7-2600
AMD Radeon HD 6700 Series (latest drivers installed)

Please let me know.

Thanks,
vis

[Baker]

For some reason on my pc here, I cannot get it to run at 1920x1080 at 60 hz. It will only run at 50 hz. This is not the case for Qrack or other clients. I also have the problem of when making any adjustments inside Video options within Proquake and then hitting 'Apply Changes' - NOTHING happens. I've also tried going to the console and making the neccessary command changes like - vid_refreshrate 60 or doing a vid_restart, etc. and nothing happens. Do you know why this is the case?

I can get Proquake to run at 1366x768 at 60 hz, but not at higher resolutions such as 1920x1080 (which my monitor was designed for).

My specs are:

Core i7-2600
AMD Radeon HD 6700 Series (latest drivers installed)

Please let me know.

Thanks,
vis

Next time I get a chance I can look at it. I haven't experienced the problem personally and unfortunately something that might at least in the short term limit my ability to duplicate your issue is that my display only supports a single refresh rate --- 60 Hz

You might try adding -current to the command line and seeing what happens, although I wouldn't be able to guess whether or not that would or wouldn't solve the issue.

[vis]

Next time I get a chance I can look at it. I haven't experienced the problem personally and unfortunately something that might at least in the short term limit my ability to duplicate your issue is that my display only supports a single refresh rate --- 60 Hz

You might try adding -current to the command line and seeing what happens, although I wouldn't be able to guess whether or not that would or wouldn't solve the issue.

Thanks Baker! I would really prefer using your quake client over Qrack. I just like the normal settings of Proquake vs having to customize down to Proquake like feel on another client.

Maybe can you compile a version where 60 hz is the only supported refreshrate for the 1920x1080 res mode? and I can use that for the time being?

Anyway, any help is much appreciated. Thanks!

[vis]

Thanks Baker! I would really prefer using your quake client over Qrack. I just like the normal settings of Proquake vs having to customize down to Proquake like feel on another client.

Maybe can you compile a version where 60 hz is the only supported refreshrate for the 1920x1080 res mode? and I can use that for the time being?

Anyway, any help is much appreciated. Thanks!

woah, that seemed to semi-fix the problem. What happened now is it loaded it using desktop resolution which was 1920x1080x16 instead of 32 bit. But it is now 60 hz. I can live with that if that is the solution. However, I am clearly using 32 bit colors on my desktop, so this is strange.

[Baker]

woah, that seemed to semi-fix the problem. What happened now is it loaded it using desktop resolution which was 1920x1080x16 instead of 32 bit. But it is now 60 hz. I can live with that if that is the solution. However, I am clearly using 32 bit colors on my desktop, so this is strange.

Qrack's and ProQuake's video switch code are nearly identical, both derived from FitzQuake. R00k and I handle error conditions a bit differently, maybe there are circumstances where Windows says a mode isn't available and ProQuake honors that and doesn't make an attempt, but Qrack makes the attempt anyway on what Windows didn't indicate was a valid mode but it happens to be one ...

Wouldn't be the first time that some of the Windows API calls were "wrong" about what they report to the engine (ProQuake accepts gamma changes regardless of whether or not Windows says the gamma change failed versus say DarkPlaces which sticks to the API documentation as a result I have never been able to adjust gamma in DarkPlaces even though I can in ProQuake ... ugh). I know on my old CRT that it had some higher refresh rates (Polarite complained about this too once upon a time) that Windows did not list as being available yet they showed in Nvidia control panel.

Either way, I'm glad that -current largely (but slightly incompletely) addresses the issue.

[vis]

Qrack's and ProQuake's video switch code are nearly identical, both derived from FitzQuake. R00k and I handle error conditions a bit differently, maybe there are circumstances where Windows says a mode isn't available and ProQuake honors that and doesn't make an attempt, but Qrack makes the attempt anyway on what Windows didn't indicate was a valid mode but it happens to be one ...

Wouldn't be the first time that some of the Windows API calls were "wrong" about what they report to the engine (ProQuake accepts gamma changes regardless of whether or not Windows says the gamma change failed versus say DarkPlaces which sticks to the API documentation as a result I have never been able to adjust gamma in DarkPlaces even though I can in ProQuake ... ugh). I know on my old CRT that it had some higher refresh rates (Polarite complained about this too once upon a time) that Windows did not list as being available yet they showed in Nvidia control panel.

Either way, I'm glad that -current largely (but slightly incompletely) addresses the issue.

Yeah, no problem. Thank you for that command line parameter. I narrowed down the issue i was having with the video to the refreshrate and realized it was using 50 hz. I don't understand why I cannot go into the menu options and change it though. It doesn't allow me to make any video changes once I am in proquake. Very strange... Anyhow, since the -current gets it to run at 60 hz, that will at least solve the video smoothness problem i noticed. So THANK YOU!

[bluntz]

I keep shaking that big red box under my tree hoping to get some clue as to whats in there......

[PRINCE_ALI]

Which .exe are you using? I had that problem with glpro451.exe, couldn't switch refresh rates at all, so I tried dx8pro451.exe and problem solved.

[vis]

dx8pro451 seems like it works, but it actually is not switching to new resolutions for me. when i type vid_describecurrentmode it still shows as 640x480x16. Something is oddly strange with proquake 4.51 and the ati 6700 series or ati cards in general. Baker please help!

[rev]

vis lets play!

[sschm]

Refresh Lock

This has been mentioned before, but "Refresh Lock" is a program that I have been using for GL ProQuake 4.51 to force my CRT monitor to use a 120hz refresh rate. If I do not use this program, ProQuake forces my monitor to use 60hz no matter what.

I got this information from the following URL: Smooth Quake - QuakeWorld Wiki

You'll have to do a Google search for the Refresh Lock program to find the proper URL.