protonscr

[GoldSource] fps_max does nothing

steamclosed reviewedMOVED: Half-Life 1
ValveSoftware/steam-for-linux#1578 · opened 2013-02-11 by xPaw · updated 2013-02-11 · 9 comments · github
XxPaw 2013-02-11 github

Since last update, fps_max seems to be ignored. Happens on Windows.

51195c64e4b08631241178c7

AAnAkkk 2013-02-11 github

You're probably moving in slow motion then...?

Aalfred-valve maintainer 2013-02-11 github

If gl_vsync is set to 1 then this is true, have you set gl_vsync?

Aalfred-valve maintainer 2013-02-11 github

Try toggling gl_vsync too and see what happens, may be related to #1577 with default vsync value not being picked up.

XxPaw 2013-02-11 github

If gl_vsync is set to 1 then this is true, have you set gl_vsync?

Oddly enough, if it's set to 1, then fps_max is ignored, and FPS is just jumping around from 70 to 600. If it's zero, then it's just fine.

Aalfred-valve maintainer 2013-02-11 github

Okay, so this suggests that the vsync impl on your GL driver is bugged (or you disabled vsync?). What are your OS details

Zzp 2013-02-11 github

This happens if you have vsync forced off in your video card's control panel and gl_vsync set to 1 in cs/half-life.

If you have vsync set to application controlled it works fine, gl_vsync 1 = capped at monitor refreshrate, gl_vsync 0 = capped at fps_max.

Aalfred-valve maintainer 2013-02-11 github

So I think this is not a bug, the system is doing what you asked it to do. I changed fps_max to not apply when using gl_vsync to prevent frame rate drops due to timing getting slightly out of sync between fps_max and vsync.

XxPaw 2013-02-11 github

Okay, so this suggests that the vsync impl on your GL driver is bugged (or you disabled vsync?)

Just checked my graphics settings, and I indeed had vsync disabled, I set it to application controlled, and it worked just fine. However #1577 is indeed an issue.

Aalfred-valve maintainer 2013-02-11 github

Okay, closing out as non bug. #1577 will be fixed in the next release.

Nothing extracted yet.