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
Also seen when you used in nvidia optimal or adaptive performance mode instead of max, the game would drop to very low fps while in the game, but pausing it went back to normal, while still the same stuff visible, if you changed that nvidia setting then everything was normal, basically game didn't know when to properly idle.
It's so stupid that I don't believe it yet
The stutter Im getting is usually happening in Dense areas, not always, but usually
It basically is a game freeze for like 2-4 seconds and then it resumes, audio cuts out too.
Is that the same symptoms of your stutter, that you fixed with Riva and the Nvidia App?
Im on 3080ti, it runs smooth at 58-60 fps 95% of the time, then I get these random stutter/freezes that last for 2-4 seconds.
This is what Im wondering; Im worried they may not realize theyre actually running at 30 and think its done something.
That's the stupid part. MSI still shows 60 and I know it's running on 60. I play games since I was a kid so 30/60 fps it's a huge difference.
I think the in game lock did something to the frametime because that was my problem, the game was locked at 60 but the jittering was so bad that I know it was actually running on 55/58 fps. I know because assassin's Creed Odyssey o had the some problem but there MSI actually showed the game running at 56/56 because the lock was not working.
I don't know how but now it's butter smooth. Even in Yokohama.
Thank you for that. Its so weird the game seems to always run at 60 FPS for me but the higher i set the cap, the slower it runs ingame..
Finally someone had this working hahaha
People seems to think that I can't differentiate 30 from 60 but yeah. Don't know why this works for me. This only proves the poor quality of this port.
TO AVOID CONFUSION, HERE IS WHAT I DID:
Add Ronin.exe from game folder to RivaTuner Statistics Server. Set the framerate limit to 60.
In game: Go to System>Graphics, set the in game FPS lock to 30 and the cutscene fps lock to 30. Then enable framegen.
This leads to a very stable framerate for me and makes the game more playable, parry timings seem weirdly easier as well. The frametime graph is perfectly smooth. I thought I felt some input delay in the menu, but I don't really feel it in the gameplay, I'm not even sure it exists in the gameplay.
**sidenote: Due to me having a Gsync display, I have Vsync disabled in the game settings but force enabled ON in Nvidia Control Panel and my monitor is set to 120hz
Only thing i need to remember is that i change the in-game fps back to 60 before i stop session. If i leave it to 30fps next time i start the game it will be 30fps. No need for rivatuner here.
Rtss uses async by default.
But you can't start the game with 30 fps mode. You gotta start with 60 fps and during the game you have to switch to 30 fps. CPU down to 30%, gpu down to 40-50%. I'm still getting 60 fps, which I was struggling to get on 120 fps mode with both CPU and GPU being maxed out.
These guys gotta learn to code man. Damn.
Thanks for the info, i didnt know rtss had a major update like that.
Ill have to try it later, i uninstalled the game.
Also this whole stutter thing and switching fps modes and stuff is exactly like Wo Long, they dont seem to have learned anything.