It's probably due to #4056?
Try setting DXVK_FRAME_RATE=-1.

It's probably due to #4056? Try setting DXVK_FRAME_RATE=-1.

unfortunately didn't help and made it worse where fps dropped to a slideshow of steady 1fps

just retested with mesa 24.2.5-1 with same behavior but interestingly it works correctly with the nvidia drivers

Try using -freq 144 launch option.

Such as:
DXVK_FRAME_RATE=0 %command% -freq 144

Try using -freq 144 launch option.

Such as: `DXVK_FRAME_RATE=0 %command% -freq 144

Didn't help unfortunately. The only thing that helps is disabling vsync inside the game.

Does -windowed -freq 144 work?

Does -windowed -freq 144 work?

Windowed worked! It also works without any other env vars or parameters if you choose windowed borderless mode in video settings.

Just a small disclosure: i tested this one with Portal 1 because it was a smaller download and i just deleted the previous game, it should still be the same as far as i understand since it also is a Source 1 game.

This is https://github.com/ValveSoftware/Source-1-Games/issues/5704 then. The issue is probably on Valve's side.

Try using -freq 144 launch option.
Such as: `DXVK_FRAME_RATE=0 %command% -freq 144

Didn't help unfortunately. The only thing that helps is disabling vsync inside the game.

The "-freq" command is worthless.

Long story short:
Source-Engine-1 should not have the games cap to a lower refresh rate than the monitor IF you are playing them fullscreen, so it's possible that your monitor is set at 60hz instead than 144.

The command DXVK_FRAME_RATE=X should not be needed for S-E-1 because reasons.

Many S-E-1 games, except TF2 and some others (I can't remember, maybe CS:S?), will cap the max fps of the game to the monitor's hz (at least on Wayland) if set at fullscreen, so borderless window is the best option.
This tends to happen with pure Vulkan games and/or with Freesync Monitors (variable refresh rate).

Here's my source for the DXVK_FRAME_RATE=X claim:
https://steamcommunity.com/sharedfiles/filedetails/?id=3424834997

Here's my source for the S-E-1 claims:
https://github.com/doitsujin/dxvk/issues/4895#issuecomment-3015322890

https://github.com/ValveSoftware/Proton/issues/8889

Just a quick note:

I was fighting for my life against a TV from EARLY 2010s (tx 32cw304).
It has a TERRIBLE resolution+hz control system.
It also has RMR tech...

To avoid making the image look like it had a "vomit filter" (imagine PS2 motion blur) when moving I HAD to force -freq 59 in those games which tried to launch at a different resolution than the selected one (because they'd try to use either 50hz or 60hz instead of 59hz), because altho the LCD panel is 1360x768p, the TV "supports" 1920x1080p (which is a lie, it's an internal resolution, it can mess up with the Refresh Rate).

59Hz making motion smoother than 60 is just your TV switching to PC mode (or disabling postprocess) on non-standard resolutions.

And it's somewhat normal that they report 1080p, as there's a lot of crappy equipment that only accepts either that or 720p.
That wasn't a big deal until a few years ago (when a lot of the logic was still implicitly based on CRT assumptions), but now both windows and linux are starting to remove non-standard resolutions which means that they try to use the supposed native resolution of the display as much as they can.

It should be nothing that setting game mode and a custom resolution cannot fix (even though the manual of the thing has 1366x768 as the native resolution, and apparently it should be able to do 85Hz too?).

Anyway back to this issue, did anybody try to see if this still happens with X11?

@mirh

I don't have a X11/Xorg distro, so I can't test it.
That said, a partial problem I have is that the "infrared receiver" is broken and should be changed, otherwise the remote doesn't work, which means that I can just control volume, channel and input.

I am pretty sure that those "resolutions" may as well be lies, because when setting those Hz I saw no difference (UFO test).

1360x768p is literally the native resolution of that TV, and since I couldn't fiddle with the remote into the menus, just and only forcing the games to run at 59hz made them not derp out (basically the TV's pixels started melting, like if Motion Blur was activated)...

If anything I can add this (since I'm chronically ill I got more forgetful):

I have a PC with a GT 1030 running Fedora KDE.

Basically just and only with Half Life 2 (Lost Coast map for easier testing) the framerate "skips" by leaps of 30.
Instead than going 100% (GPU) and getting 108 or whatever FPS, the FPS will lock at 90 and use 88%, then I look at the sky and it's 120fps at 79%, then I look at the corner of the skyboxit can reach 180fps at 98%...

It's not a mortal problem, but I just remembered my PC has it.
If I'm not wrong, no other S-E-1 game has it.

@K0bin probably not our bug: https://github.com/doitsujin/dxvk/issues/4290#issuecomment-2509538036