ValveSoftware
Throne and Liberty (2429640)
Compatibility Report
- Name of the game with compatibility issues: Throne and Liberty
- Steam AppID of the game: 2429640
System Information
- Hardware Model: ASUS ROG CROSSHAIR VIII DARK HERO
- Memory: 64,0 GiB
- Processor: AMD Ryzen™ 9 5950X × 32
- Graphics: AMD Radeon™ RX 7900 XTX
- Disk Capacity: 3,0 TB
Software Information:
- Firmware Version: 4805
- OS Name: Fedora Linux 39 (Workstation Edition)
- OS Build: (null)
- OS Type: 64-bit
- GNOME Version: 45.9
- Windowing System: Wayland
- Kernel Version: Linux 6.10.11-100.fc39.x86_64
ID: com.valvesoftware.Steam Ref: app/com.valvesoftware.Steam/x86_64/stable Arch: x86_64 Branch: stable Version: 1.0.0.79 License: LicenseRef-proprietary Origin: flathub Collection: org.flathub.Stable Installation: system Installed: 45,5 MB Runtime: org.freedesktop.Platform/x86_64/23.08 Sdk: org.freedesktop.Sdk/x86_64/23.08
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
With Proton Experimental, the game starts and runs good so far (have completed the Tutorial and got to the first city port).
One issue I have is that the game says Dualsense controller supported, however when the controller is connected wireless via Bluetooth, it is not recognized / not working in-game. This is both with Steam Input enabled or disabled.
But when connected wired via USB, then it works (button icons are OK).
EDIT1: Using the Dualsense controller via Bluetooth, with Steam Input disabled and changing the registry: DisableHidraw=1 Enable SDL=0
Results in Wine using the controller as Xinput in Wine / Control Panel / Game Controllers and the game then detects the controller as Xbox and works, the button icons are Xbox styled.
anyone else getting degrading performance over time ? The game is very fluid at first but as time goes on it gets choppier and choppier when moving the camera.
Kernel Version: 6.11.4-zen1-1-zen Driver: AMD AMD Radeon RX 7800 XT (radeonsi, navi32, LLVM 18.1.8, DRM 3.59, 6.11.4-zen1-1-zen) Driver Version: 4.6 (Compatibility Profile) Mesa 24.2.5-arch1.1
anyone else getting degrading performance over time ? The game is very fluid at first but as time goes on it gets choppier and choppier when moving the camera.
Kernel Version: 6.11.4-zen1-1-zen Driver: AMD AMD Radeon RX 7800 XT (radeonsi, navi32, LLVM 18.1.8, DRM 3.59, 6.11.4-zen1-1-zen) Driver Version: 4.6 (Compatibility Profile) Mesa 24.2.5-arch1.1
Same on my system. It gets unplayable with constant stutters and so far only restarting the game seems to fix it.
I'm also having my character get stuck like on this protondb report.
Replying to https://github.com/ValveSoftware/Proton/issues/8147#issuecomment-2489425828
I found disabling directX 12 helps a lot.
I found disabling directX 12 helps a lot.
I'm already using dx11 but the kind of stutters I got seem pretty similar to what I got by turning on dx12. Probably unrelated tho, idk.
I tried using the default latest kernel on arch since @dlicois was using zen like me, just in case it was something like a weird kernel scheduling thing or something like that, but it changed nothing for me, both problems persisted.
Still gotta test for a bit longer, but I tried re-enabling the steam overlay and it seems like it stopped happening... @dlicois is yours disabled? Try turning it back on.
It has always been on for me. Perhaps you've benefited from the Mesa 24.3 release ?
It has always been on for me. Perhaps you've benefited from the Mesa 24.3 release ?
I haven't updated yet, I'm on 24.2.7
Haven't gotten the fps stutters anymore(since re-enabling steam overlay), but since the last game update the player position rollbacks have gotten a lot more frequent, sometimes occurring right after starting to play.
EDIT: might actually be related to my internet this time, just noticed I'm having a lot of packet loss
The game still lose performance over time and it always starts with mouse movement for me. After a couple of hours, it turns to constant stutters every few seconds. Restart solves it. Enabling/disabling overlay didn't do much for me, well, overlay isn't even working for me right now so I'm not sure what else I can provide. This is on NVIDIA GPU.
There appears to be an input issue in Proton Experimental and 10+. If you left click at the same time as pressing any of the movement keys, a/w/s/d it's as if the key input is not registered and the character does not move. Swapping to Proton 9.0-4 fixes the issue. Sysinfo: https://gist.github.com/wescode/eacb57c97befc2e710cc5b1e7237e2ae
Hello @wescode, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
Hello @wescode, please add
PROTON_LOG=1 %command%to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
@wescode couldn't reproduce your issue on proton 10 or experimental, could you give more details about in what situations it happens? do you have to be in battle? does classic or action mode matter?
I tried holding the left click and then, as I kept holding it, using wasd. Also tried activating both at the same time, but neither prevented movement.
@wescode couldn't reproduce your issue on proton 10 or experimental, could you give more details about in what situations it happens? do you have to be in battle? does classic or action mode matter?
I tried holding the left click and then, as I kept holding it, using wasd. Also tried activating both at the same time, but neither prevented movement.
I'm using action mode. Sometimes it can take several attempts of pressing lmb+movement key. I also noticed that if I turn off the hud with alt+b I can't reproduce the issue. Once I turn the hud back on I can produce the issue.
@wescode in my case I had the hud on the whole time. Tried cycling through fullscreen, borderless and windowed options but neither of these helped me repro this issue
@wescode Are you clicking on something specific when you are simultaneously trying to move? I also could not reproduce, and I found that I never had any reason to hold the left button down in my limited testing, so I'm wondering if there is some action where holding the left cursor causes the failure, or if you can reproduce when just running around randomly and holding down the left cursor button while not selecting anything. Also - you are using Gnome+xorg as your window manager, right?
@wescode Are you clicking on something specific when you are simultaneously trying to move? I also could not reproduce, and I found that I never had any reason to hold the left button down in my limited testing, so I'm wondering if there is some action where holding the left cursor causes the failure, or if you can reproduce when just running around randomly and holding down the left cursor button while not selecting anything. Also - you are using Gnome+xorg as your window manager, right?
I don't hold lmb, I click it the same time as a movement direction. I've tested it when clicking the test dummies or just clicking on the open ground, can happen either way. I'm actually running Gnome + Wayland.
@wescode Thank you for the additional details ... I was finally able to reproduce, which is the first step towards figuring out what is going wrong :) In my testing so far, I could only reproduce with Gnome+Wayland. It is extremely intermittent for me, so if you happen to have time to try Gnome+Xorg to see if you can reproduce there, please let me know. In any case, we'll look into this further - thank you for the report!
@wescode Thank you for the additional details ... I was finally able to reproduce, which is the first step towards figuring out what is going wrong :) In my testing so far, I could only reproduce with Gnome+Wayland. It is extremely intermittent for me, so if you happen to have time to try Gnome+Xorg to see if you can reproduce there, please let me know. In any case, we'll look into this further - thank you for the report!
@alasky17 Was the root cause every found? I actually tried out the latest GE-Proton and enabled Wayland and that seems to have fixed the issue.
@wescode Sadly not yet - it is still an open issue. These bugs can be extremely tricky to track down :( This seems like almost certainly a race condition since it is intermittent, so it makes sense that any change of variables could make it so rare that it basically never happens.
Yea interestingly enough I tried proton experimental today and I was not able to reproduce the issue now.
And now the issue is back. I'm not sure if it's related to some system update or what exactly. I will say that when this occurs I also have the issue where pressing the default ALT key to show the cursor in action mode does not work. Both issues seem related and I didn't realize this until it was working the past few days and then stopped. No change in proton versions as I was using the latest GE-Proton the past few days.
Edit: The issue where pressing ALT in action mode does not show the cursor also happens in proton experimental/proton 9
Edit2: So I noticed something interesting with the ALT show cursor bug. If I hold ALT then left click once the cursor will show, I can do the same to hide it again. To add a little more info to this, if I use GE-Proton and enable wayland both the show/hide cursor issue and original bug do not occur.
Hey @alasky17 I just wanted to let you know that the root cause of both of my issues appears to be ibus. An easy workaround is to kill the ibus-daemon and both issues are then resolved; the mouse shows when i hit ALT and there is no input issue when moving and clicking LMB. I will open an issue with ibus.