Just reporting, but if you are experiencing blocky shadows with latest mesa, it might be this problem https://gitlab.freedesktop.org/mesa/mesa/-/issues/7319

Cyberpunk and gtav are having the same issue currently, so we'll have to wait for a fix for this

As stated in the Cyberpunk thread, the blocky shadows are gone from this game, it seems

Hello @kisak-valve, thanks a lot for your quick reply.
This worked! I followed the instructions from the Arch Wiki and set an environment variable AMD_VULKAN_ICD=RADV. After restarting, running the game on Steam with the launch options:
DRI_PRIME=1 %command%
worked flawlessly, with the dGPU recognised as well. It was clearly an AMDVLK issue here. Do you need some more information from me (e.g. another test with AMDVLK)?

Moving the camera over objects trees in a battle causes significant hitching, anyone else have this problem?

steam-1142710.tar.gz
gist: https://gist.github.com/Natherul/1e30299733e7821ae63acb3559cca46a

I get to the splash screen and then it just fully freezes my system. I cannot even change tty. This is not the only game it happens to but not games. (same does happen for Stellaris for example, even in native linux)

When I open the Steam overlay, the game window gets moved behind my taskbar (in both fullscreen and windowed mode).

The Shift key gets "sticky": unless I press Tab in the Steam overlay, the Steam overlay opens again when I press Shift ingame.

Since the "recent" big Steam UI update the game crashes sometimes when opening the Steam overlay or taking a screenshot with it.

I tried Proton Experimental and GE too, same issue.

My PC:
openSUSE Tumbleweed, KDE
X11
Nvidia RTX 3070 (535.104.05 at the moment, but I had this issue since the game released, with older drivers, too)

System Information

• GPU: RX 6700XT
• Video driver version: Mesa 23.3.5-1
• Kernel version: 6.7.3-zen1-1-zen
• Link to full system information report as Gist
• Proton version: Proton Experimental / Proton 8.0-5

Proton Log

steam-1142710.log

Symptoms

I am currently having similar issues to @ RicardoVizcaya, I am unable to start game - CA launcher starts without any issue, but once I click on start or continue, the launcher closes and game does not start, steam stays for a few minutes in running state, but after a while game "stops" (button shows green again with play option).

Compared to previous case I am running on RADV drivers I tried installing and running also AMDVLK (by setting AMD_VULKAN_ICD=AMDVLK) but that did not help also. Currently I am using Wayland (Hyprland) but I tested this also under X11 (awesomeWM) with the same result.

I was able to to play game on earlier patches (not sure on which the game started to break since I did not open it in quite a while but I know that I played on 4.1 so it broke probably on one of the hotfixes).

Running under gamescope or using gamemode did not help.

If anyone has an idea, which could help feel free to let me know.

Reproduction

1. Launch the game
2. Click on PLAY
3. Launcher closes and the game does not start

Ok so I did a little bit more digging, and I found out that this is actually not even an issue just for proton, but also people on Windows have the same issue, here is how to solve it:

1. If you need backup your saves/settings, they will be deleted!
2. Go to prefix for the game
3. Go to drive_c/users/steamuser/AppData/Roaming/The Creative Assembly
4. Delete Warhammer 3 folder
5. In Steam right-click on the game -> Properties -> Installed files -> Verify integrity of the game files

Game should start now.

~The game wont launch with proton 9 or experimental now, will try to get the log later. But I get to the launcher, after that it takes a long while and then crashes~

Edit: Nevermind, I think it was a steam update

The game doesn't seem to work on Proton 9. The launcher opens but then the game launches to a black screen that dies after a few seconds.
steam-1142710.log

Newest Proton fixed the launch regression.

There's another issue I've been trying to figure out for a while. In Wayland, when clicking the middle mouse button for free look during battles, the game will stutter and the frametime graph will spike up and down very rapidly until you let go of the middle mouse button. You don't even need to be utilizing the free look, you can just hit the middle mouse button and then move the camera with the keyboard and you'll see the same fuzzy stuttering. This doesn't seem to happen, or at least isn't nearly as noticeable in an X11 session.

This issue is very striking in Gnome, sway, and hyprland from what I've tested so far. It's not as noticeable in an embedded gamescope session, unless you're on a more demanding map.

I've tried remapping BTN_MIDDLE to a keyboard key or a different mouse button and the issue persists. There's no way to change the input for free look in the game settings so I'm unable to test if it's something weird with how BTN_MIDDLE is handled. Sometimes you can even just click the middle mouse button without moving the camera at all and see the frametime spikes in a very clear block until you release the button.

Moving the camera over objects trees in a battle causes significant hitching, anyone else have this problem?

I can confirm this as well. There is still some microstutter even without looking at trees specifically, but far less pronounced. Weirdly, even with ~80 FPS, it does not feel like 80 FPS.

I noticed this on the latest Bazzite KDE and Bazzite GNOME, with Wayland. I have previously tried Fedora a while back on this game, and I had the same issue.

Note that the native Linux version of the game does not exhibit these issues for me, despite it having lower FPS than Proton.

System Information

• GPU: AMD 7900 XTX
• Video driver version: Mesa 24.1.7
• Kernel version: 6.9.12
• Link to full system information report as Gist: https://gist.github.com/RaduAvramescu/0d1302de50a0c977187790a549318e8d
• Proton version: Proton Experimental

My current experience with this title is that it has no compatibility issues and runs out of the box with standard Proton 9, but performance is rather poor, and there is a huge gap between Windows and Linux+Proton, seemingly much larger than in other games. Especially on high resolutions, the impact is massive.

• Battle benchmark: ~45-55fps
• Campaign benchmark: ~40fps
• Immortal Empires benchmark: ~30-40fps

• Battle benchmark: ~55-60fps
• Campaign benchmark: ~55-60fps
• Immortal Empires benchmark: ~55-60fps

Desktop: 3440x1440 resolution, Windows 10

• Battle benchmark: ~95-140fps
• Campaign benchmark: ~60-80fps
• Immortal Empires benchmark: ~55-60fps

This is one of the only games I've tested where the much lower resolution of my laptop resulted in significantly better performance despite the mismatch in hardware. For this test I explicitly left the settings the same on both desktop and laptop. I frequently test games on both my laptop and desktop, and the laptop always has much worse performance than my desktop despite the large decrease in resolution (as one would expect, the RX 7900 XTX is one of the best GPUs on the market).

It's also a game where the gap between Proton and Windows performance is really, really large. For the Windows 10 benchmark I even left everything on max, no tweaking whatsoever. I often dive back into my Windows 10 install exclusively for the purpose of comparing performance, and the difference for this game is much bigger than usual.

The same can be said for other Total War games. I get similar results for Three Kingdoms (779340) for example (although performance for Warhammer III is certainly the worst).

In my case Proton is working fine with latest RADV on RX 7800XT BUT during battlefield many surfaces is flickering and it's very annoying.
PS native version is much worse and some surfaces just not exist, the Mesa bug ticket exist.

@romatthe I've had a similar experience overall. However, I recently tried using the native wayland driver in a custom Proton and the difference is huge, more so than for any other game I've tried in native wayland. So if you're able to try that out, you might want to give it a shot, and hopefully the native wayland driver is exposed in default Proton fairly soon.

Thanks for the suggestion @trgeiger! I had a go at it last night, using one of the latest nightly Proton builds from the wine-tkg project based on a Wine 10.1 release candidate.

I was able to get the Wayland Wine driver working, but performance gains did not seem significant. The battle benchmark did see some minor improvements, but the Immortal Empires benchmark remained fairly dreadful with no real improvement.

That said, I will definitely come back to this at a later point. If/when we'll see a vanilla Proton 10 release and if/when that includes the ability to use the Wayland driver, I'll try to do more in-depth benchmarking.

Do you have some details on what build you used btw?

@stalkerg I am also experiencing significant amounts of surface texture flickering, both in the campaign map and the battlefield.

I had to downgrade mesa to 24.3.4 to get rid of it, so I guess we just have to wait for it to be patched upstream.

I've seen reports of this elsewhere (even going back two years ago) but shadows on I get really bad lag in battles if I look at an army and move my screen. It's fine if I turn shadows off.

Using
Proton 10.10 GE (tried older versions and still same issue)
mesa 1:25.1.6-3 (tried git version and still same issue
Wayland Enabled (Tried without and other issues)
CachyOS

Hardware
9070xt
9950x3d

@Rhiyo Could you check if this improves when restricting the game to only 8 threads? This can be done by launching it with WINE_CPU_TOPOLOGY=8 %command% in the games steam launch options

@Blisto91 Yep - that was it

I even used WINE_CPU_TOPOLOGY=16 and it worked

WINE_CPU_TOPOLOGY=32 starts to cause the issue.

I guess it's because there aren't many CPUs currently being used with that many cores that not many people encounter this anymore.

Would this happen on windows as well - I wonder?

I'll keep this in mind for potential issues in other games.

I'm having the problem that sometimes when a battle is finished and the loading screen appears to load the campaign map, my entire GPU crashes and resets by the kernel.

Operating System: Arch Linux
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 32 GB of RAM (27.3 GB usable)
Graphics Processor 1: AMD Radeon RX 7800 XT
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C56
System Version: 6.0

AMDGPU Device Coredump.txt

journalctl.txt

Replying to https://github.com/ValveSoftware/Proton/issues/5976#issuecomment-3250250407

If you have a GPU crash it's 100% a for Mesa and kernel issue tracker, not for Proton.

@TTVAUTISM0 Hi there. Does the performance improve with Proton if you limit the amount of cores the game can use? You can try inserting WINE_CPU_TOPOLOGY=8 %command% in the games launch options.

@Blisto91 It’s more stable but I’m hovering around 56-60 fps in both campaign and battle

having the same problem with warhammer 3. I was trying to launch the total war warhammer 3 for the first time on my cachyos desktop + intel arc gpu. I set the compatibility to either proton experimental & proton-cachyos but the still get black screen when trying to launch the actual game, however the total war launcher works just fine

System Information

• GPU: AMD Radeon RX 7900 XTX
• Kernel version: 7.2.0-1-cachyos
• Link to full system information report
• Proton version: 11.0-2 ( +Latest, 9.0-4, 8.0-5)

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.

Symptoms

In a multiplayer campaign session where a Windows player is present, Warhammer 3 immediately desyncs when going into a battle.
Additionally, starting a multiplayer campaign seems to skip the intro and the initial 'quest' that the game gives you. It does not matter who's hosting.

When all players are using Linux, the game starts and runs as expected. Singleplayer also works as expected.

Reproduction

Loading a multiplayer campaign game with a Linux and Windows client and immediately attacking a settlement causes the immediate desync.

Logs are attached in the gist. I've reproduced the issue and closed the game right afterwards. The logs are running on version 11.0-2