In the first camp and in the start menu I am literally seeing 10 fps. It does not matter the quality setting or if the GPU is forced to its high performance profile. Holy :smile:... Considering the game current state poor performance was expected. But I did not imagine it would be that bad...
Something interesting is that this game uses a lot more gtt memory than I usually see games using. Just getting to the start menu is enough to see 3 GB or more gtt memory used while the used vram is above 7 GB.
After doing many tests I found a way to increase the fps to around 40. Decreasing the texture to low and restarting the game did it. The change does not take effect on the fly. That is why I did not notice the texture quality having any effects before. The whole game has to be restarted...
The game still uses more than 7 GB vram. But the gtt memory now stayed close to 700 MB. So the ridiculously low performance before was probably this dumb game trying to use more vram than the GPU has. What forced radv/amdgpu to resort to gtt memory.
Considering how ugly the textures are even on "high quality" I wonder how they can still use so much gpu memory even when the quality is on low. Could this game be loading the whole map textures even if most of them may not even be used?
I find the model quality also heavily affect the frame rate. I can reach 60 with 5700XT in 1920x1080 and highest setting except texture and model, which is the lowest setting(only when GPU bound).
The game still CPU bound most of the time and keep running worst if stay in the map for too long.
Proton mpflat also failed to play video as those file is in asf(wmv) format. Manually transcode to mp4 work.
I find the model quality also heavily affect the frame rate. I can reach 60 with 5700XT in 1920x1080 and highest setting except texture and model, which is the lowest setting(only when GPU bound).
Interesting. I will try this later. Is this another setting that also only actually changes when restarting the whole game? I think I touched it at some point but I did not notice any difference. But I did not think about restarting the game at the time.
Reducing the model quality made no noticeable difference on my computer.
After switching the game fps limiter to 30 fps I actually got stable 60 fps!?!? Even setting the texture quality to medium. FPS is still poor with them on maximum. That is a weird bug. For some reason when the limit is set to 60 the actual result fluctuates between 30 and 40. The other limit targets seem to actually be trying to put the fps on 30. Only with 30 as target I get fluid 60 fps XD.
I have also disabled both steam and ea overlays. So maybe this is also having some whole in this unexpected result.
After today's update to Proton Experimental the game crashes in the initialization. Instead of the usual image for broken videos there is now a black screen. I imagine that now Proton is trying to play the video. But something is clearly going wrong. After pressing some buttons the game gets out of the black screen but then it freezes for some time and then crashes.
I saved a Proton log but it has more than 1 GB. I probably won't be able to provide it here just like in the past. This EA app in the middle makes the log huge...
Hello @wwmm, can you check how the game behaves with Proton 7.0-6 and 8.0-1 for comparison? Proton logs are known to compress well, so it might be worth checking how compact it can get in an archive.
can you check how the game behaves with Proton 7.0-6 and 8.0-1 for comparison?
I have been playing this game on Proton Experimental since it was launched. Including today. But after the latest update to the experimental branch a few hours ago it started to crash in the initialization after trying to play the intro video. As the EA app thinks we are using different computers when we try to change Proton prefix I am avoiding to create another one. The last time I tried this kind of test EA locked me out of the game for almost 24 hours =/...
Proton logs are known to compress well, so it might be worth checking how compact it can get in an archive.
They do. But even after compressing with 7z the file has 35,8 MB. So github won't allow me to put it here. Is there another place to put the log?
When the game crashes the output of sudo journactl -b | grep -i steam has the following
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/bin/wine64 without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/libopenxr_loader.so.1.0.20 without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/libopenxr_loader.so.1.0.20
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winevulkan.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winevulkan.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/wineopenxr.dll.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/wineopenxr.dll.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winealsa.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winealsa.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winepulse.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winepulse.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/opengl32.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/opengl32.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/avicap32.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winex11.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winex11.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/kerberos.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/win32u.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/win32u.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/libwine.so.1.0 without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/libwine.so.1.0
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/dwrite.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/secur32.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/winspool.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/bcrypt.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/crypt32.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/ws2_32.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/ntdll.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/ntdll.so
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/dnsapi.so without build-id.
Module /home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/netapi32.so without build-id.
#0 0x00007f37d20acdf8 n/a (/home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/ntdll.so + 0x4edf8)
#1 0x00007f37d20adb51 n/a (/home/wallace/games/steam/steamapps/common/Proton - Experimental/files/lib64/wine/x86_64-unix/ntdll.so + 0x4fb51)
I wonder if the last 2 lines give some hint about where the game is having problems.
@kisak-valve link to the log file https://mega.nz/file/qlMHWSib#IW4jokKryBFqw4fhDgzyrArC7ubU0QNCww3EFNkWTts. For now I do not see a better alternative. Even with ultra settings the 7z file is too big for github.
I will test if creating a new Proton Experimental prefix makes any difference. Maybe the upgrade from the old one had some problem.
Well... The game is working now but I do not know what fixed it. As soon as I deleted the prefix and launched the game steam started a runtime soldier update. So one of the two fixed the crash. The intro video is back to the usual "generic image" of non playable videos.
By the way EA overlay still hurts performance a lot. Thankfully I found some time ago on the web some commands that allowed me to launch only the EA app so that I could turn this overlay off.
steam started a runtime soldier update
I think that what actually happened was the runtime sniper installation. Until today I had only the soldier. I did not even know this sniper existed :smile:
And now out of nowhere the game is crashing again. But now it does not even get to show its window and deleting the prefix did not help. As far as I remember there was no update to Proton or Sniper. So strange...
@kisak-valve now that the game is crashing earlier the log is a log smaller
steam-1938010.zip.
This bug is obsolete/invalid now.
This game performs badly in Windows too. (This is obvious; see players' reviews.) And patches came during Feb and March in 2023, so the original claim became obsolete.
WildHearts Steamdeck Compatibility/Resolution Error
Issue transferred from https://github.com/ValveSoftware/Proton/issues/9951.
@Iceman711w posted on 2026-07-06T21:05:18:
Subject: Wild Hearts (App ID: 1938010) stuck in top-left tiny window resolution loop on Steam Deck
Issue Description:
When launching Wild Hearts on the Steam Deck, the game successfully passes the EA App verification, but immediately upon booting the actual game engine, the display collapses into a tiny, microscopic window in the top-left corner of the screen. Audio plays normally in the background, but the video pipeline fails to scale or maximize to full screen.
We have thoroughly verified that this is a display context conflict between the game engine's video pipeline, the EA App container, and the Gamescope compositor in Gaming Mode. The game runs successfully in Desktop Mode at 1280x720, but the saved profiles fail to migrate or bind properly when returning to Gaming Mode.
Troubleshooting Steps Attempted (All Unsuccessful in Gaming Mode):
Please investigate the Gamescope window focus mapping for this specific title under the current SteamOS build, as the title remains entirely unplayable in Gaming Mode due to this resolution constraint.
proton experimentalx4 2026-07proton 7.0-6x2 2023-04PROTON_FORCE_WINDOWED=1x1 2026-07PROTON_NO_FSHACK=1x1 2026-07wineopenxr.dllx1 2023-04
Compatibility Report
System Information
I confirm:
For some reason there is no audio when the game is set to
5.1/7.1surround. I can see the streams it creates in Pavucontrol but different from stereo there is no audio when surround is selected. Considering that on windows people having been switching to surround in an attempt to boost the poor game performance surround audio should be working here too. The question is if it is a PipeWire or wine bug.Unfortunately the Proton log is too big to attach here. The txt file has 1 GB and the only thing I did was starting the game with the audio set to 5.1/7.1 and then switching to stereo. Even after compressing with 7z the file was bigger than the 25 MB limit. I wonder if the EA app has something to do with this... Is there any other way to provide the log?