Total War: WARHAMMER III (1142710)

[tmespe]

Compatibility Report

• Name of the game with compatibility issues: Total War Warhammer 3
• Steam AppID of the game: 1142710

System Information

• GPU: RTX 2060
• Driver/LLVM version: nvidia 515.57
• Kernel version: 5.18-9
• Link to full system information report as Gist: https://gist.github.com/tmespe/05cf1d62146b8926f442e0122961dc01
• Proton version: Proton-7.0-3, Proton Experimental

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

The game is stuck at the loading screen when entering any campaign map or the campaign benchmark at about 95%. It seems the game actually finishes loading, but does not remove the loading screen, as I can hear the sounds of the campaign map and can click and interact with it while the loading screen is still up. The prologue seems to work, probably because it's using a completely separate campaign map.

PROTON_LOG

Reproduction

Open game. Start a new campaign (not prologue) or start the campaign benchmark.

[raaffaaeell]

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

[raaffaaeell]

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

[kisak-valve]

Total War: WARHAMMER III (1142710) won't launch

Issue transferred from #6570.
@RicardoVizcaya posted on 2023-02-25T15:09:39:

Compatibility Report

• Name of the game with compatibility issues: Total War: WARHAMMER III
• Steam AppID of the game: 1142710

System Information

• GPU: AMD® Radeon™ RX 6800M
• Driver/LLVM version: Mesa 22.3.6-1
• Kernel version: 6.1.12
• Link to full system information report: Gist Link
• Proton version: 7.0-6

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Since around two months I have been unable to launch the game as I did before with the following launch options:
DRI_PRIME=1 %command%
The launcher opens alright, but the game crashes after clicking PLAY without even showing the black screen. The closest issue I could find to this was #6262; it is closed though and didn't apply to me. I have tried different Proton versions, opting in and out of Steam Beta, and toggling on and off the Vulkan shaders to no avail. The only way I can make the game run (as recommended in ProtonDB) is with the launch options:
PROTON_USE_WINED3D11=1 %command%
In this case though, only my integrated GPU is recognised by the game, which does not meet the requirements to play it. Even adding gamemoderun and configuring using the dedicated graphic card as environment variable does not make my dGPU appear in the game settings.
What can I do to have the game working again under Proton?

Reproduction

1. Launch the game with PRIME arguments to select your dGPU
2. On the launcher, click PLAY
3. The game will close without opening.

Proton Log

steam-1142710.log

PS

This is my first report so please let me know if I am missing to provide some information.

[kisak-valve]

Hello @RicardoVizcaya, info: Driver: 2.0.249 in your Proton log tells us that AMDVLK is being used. It might be interesting to test how the game behaves with mesa/RADV.

[RicardoVizcaya]

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)?

[cncz42]

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

[Natherul]

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)

[Liemaeu]

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)

[mimotej]

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

[mimotej]

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.

[raaffaaeell]

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

[trgeiger]

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

[trgeiger]

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.