RADV+Zink vs. RadeonSI OpenGL Performance On Mesa 23.2-devel

[QwertyChouskie]

SuperTuxKart regressed upstream, unfortunately... Last attempt I wasn't able to workaround it, but basically vsync mode ended up getting forced on when in the profiling/benchmark mode and the developer who made the test profile previously is no longer working on it I believe he said.

Should be fixed in 1.4, as vsync and framerate limiting options were reworked.

[Michael]

Should be fixed in 1.4, as vsync and framerate limiting options were reworked.

Ah great, will try it out then! Thanks.

[QwertyChouskie]

Ah great, will try it out then! Thanks.

Let me know if you run into any issues.

[Michael]

Let me know if you run into any issues.

Just tried with 1.4... Unfortunately, with same arguments as before, including --swap_interval=0 and --max_fps=999, still getting 120 FPS results.

[Michael]

Let me know if you run into any issues.

Also tried with max_fps 999 in the config.xml file and still maxes out at 120 on stk v1.4.

[QwertyChouskie]

Just tried with 1.4... Unfortunately, with same arguments as before, including --swap_interval=0 and --max_fps=999, still getting 120 FPS results.

Not sure where you're getting those command line arguments, but they don't seem to exist according to a quick search of the codebase. Probably a good addition, but for now, setting via config.xml or the interface is the way to go. Once it's been set once, it will remember it as long as config.xml isn't deleted or such.

In config.xml, your settings are `swap-interval` (should be 0) and `max_fps` (should be 1000 or higher).

[Michael]

Not sure where you're getting those command line arguments, but they don't seem to exist according to a quick search of the codebase. Probably a good addition, but for now, setting via config.xml or the interface is the way to go. Once it's been set once, it will remember it as long as config.xml isn't deleted or such.

In config.xml, your settings are `swap-interval` (should be 0) and `max_fps` (should be 1000 or higher).

Yeah looks like those options were dropped in a prior version... I just re-confirmed though even with swap interval 0 and max fps 999 in the config.xml, when using the --profile-time=60 mode for benchmarking I am still stuck to 120 FPS.

[QwertyChouskie]

Yeah looks like those options were dropped in a prior version... I just re-confirmed though even with swap interval 0 and max fps 999 in the config.xml, when using the --profile-time=60 mode for benchmarking I am still stuck to 120 FPS.

I just tried it on my system and it gave more the 120FPS. Any chance you have multiple copies of STK (e.g. deb/snap/flatpak) and are changing the wrong config file? The easiest way to be sure you are changing the correct config file is just to open STK and change it in Options -> Graphics.

EDIT: It's also worth checking if it's a Wayland vs Xorg thing. AFAIK you can't disable vsync on most Wayland implementations currently.

[Michael]

I just tried it on my system and it gave more the 120FPS. Any chance you have multiple copies of STK (e.g. deb/snap/flatpak) and are changing the wrong config file? The easiest way to be sure you are changing the correct config file is just to open STK and change it in Options -> Graphics.

EDIT: It's also worth checking if it's a Wayland vs Xorg thing. AFAIK you can't disable vsync on most Wayland implementations currently.

It's the correct config file, I see it being written to after launching (and still preserving the max fps). It may be a Wayland integration issue then with STK perhaps. Though last check falling back to like a pre-1.0 STK version had worked out fine I believe.

[QwertyChouskie]

It's the correct config file, I see it being written to after launching (and still preserving the max fps). It may be a Wayland integration issue then with STK perhaps. Though last check falling back to like a pre-1.0 STK version had worked out fine I believe.

If you force XWayland it may work. I assume most games you test don't natively support Wayland.

EDIT: Try:

SDL_VIDEODRIVER=x11 supertuxkart --profile-time=60

EDIT 2: try this one instead:

IRR_DEVICE_TYPE=x11 SDL_VIDEODRIVER=x11 supertuxkart --profile-time=60