lowenz

That's exactly the point of having a slider.

But the selected value doesn't (can't?) reflect the actual value as stgatilov says, so a slider is a more adaptive solution. If I want adaptive sync on a 75 Hz monitor I must limit the frametime to 1/74 *actual* seconds, not a "75" nominal value.

It would be perfect

No problem about that, it's just about coherency of the FPS limiter option in the menu. 144 is already there, the only other common value missing is 75.

Suggestion/Request: we already have "144" as a dedicated FPS limit (for 144 Hz monitors), can you add "75" as another one? Thanks! 60 70 -> 75 80 90 100 110 120 130 140 -> 144 150 etc. G-Sync (compatible) issue (low performance value after loading a savegame) still is there. Press ESC, stand by in the menu screen for some seconds, return to the game and the framerate is alright. Or move around a little.

Of course it was in 2.08.

Possible the same bindless textures issue that's not really an issue. It's a limit of the method.

Just my luck!

Maybe related! https://www.phoronix.com/scan.php?page=news_item&px=AMDGPU-FP16-DCE8-Patches&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Phoronix+(Phoronix)

issue found (2.09 beta 2 but maybe is waaaaaaaaaay older) https://postimg.cc/8smv0rkq House in front of the tavern of "A New Job"

Link points to 2.1 ?

Thanks man and have a good time in these holidays!

Any news about the upcoming "hotfix" ? So I'll finally play the Volta series during Christmas time

I'm using RTSS (MSI Afterburner monitoring companion), not (only) internal values. And I use 64 samples to smooth the (moving) average value: seta com_showFPSavg "64" And you can clearly see the difference between 30 and 50 FPS moving around a bit, I mean simply walking around a bit. After the first movements + camera rotations the framerate goes up to the "right" value. Savegame is required.

Frob https://www.ttlg.com/forums/showthread.php?t=53496