Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
i.e. See if Portal 2 works any better with +fps_max 61 in its launch options.
Some games drop you to 30fps Vsync if you're between 31 and 59 area; and 60 only if you're above 60 frames per second. Viktor Vran is the first game in my mind that I can think of doing this.
Not saying you should keep it disabled, but just wondering if it could be similar to my Viktor Vran scenario where framerates between 30 and 60 are locked to 30 and framerates above 60 are locked to 60.
Next time you get 60 FPS with Vsync, could you try disabling Vsync again and seeing your framerate?
But 60 to 30 is what I'm wondering about; and I'm thinking it's due to how the game enforces FPS to 30 if it's wandering between 30 and 60 in Ryse.
Vsync can't do that. It's refresh rate divided by an integer. If your display is 60Hz, vsync can do 60/1 (60fps), 60/2 (30fps), 60/3 (20fps) and so on. The numbers you're seeing is the counter messing up while Vsync is switching between 30 fps and 20 fps, which is quite jarring.
Either lower resolution and/or settings so the game can stay above 30fps, or turn of vsync and live with the tearing. Or spend money on a better GPU.
^This is 100% the correct answer.