hedge-dev / hedge-dev/UnleashedRecomp

[GNU/Linux] Inconsistent frame rate on Wayland

Open
#1,677 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

linux
Dominant language
C++
Stars
5.1k
Forks
421
PR merge metrics
No merged PRs in 30d

Description

On X11 the frame rate is very consistent and stays around 60 fps with some very occasional dips to 55-59 fps, while on Wayland, with the same graphics settings, the game is constantly hovering around 50 fps when boosting or in areas with lots of transparency effects, with stages like Jungle Joyride running at around 30/40 fps.

Clip comparing the performance: https://www.youtube.com/watch?v=T9gI0FTy5QE

I have tried different settings combinations (vsync on/off, transparency aa off, no anti aliasing at all) and force the game to run with different video drivers as described in the readme with no luck.

For context, I'm only having this issue with Unleashed Recompiled. So far I have not experienced performance drops like this in other games when using Wayland, either natively or via Wine.

System details:

  • OS: Ubuntu 24.04.3 LTS
  • CPU: Intel Core i5-11300H (Intel Iris Xe Graphics TGL GT2)
  • GPU: NVIDIA GeForce GTX 1650 Mobile (nvidia-driver-580-open)
  • Memory: 16gb SODIMM DDR4 3200mhz

EDIT: As suggested by @Maesejesus, force disabling Wayland Window System (sockets=!wayland) in the flatpak overrides for Unleashed Recompiled seems to be the only workaround to fix the performance issues.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported frame-rate difference on Ubuntu 24.04.3 with Wayland and X11, using the system details and the README's driver-forcing instructions. Compare performance in boosting and transparency-heavy stages; done means the Wayland-specific drops are resolved or their cause is identified with supporting measurements.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
computer-graphics, operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.