ValveSoftware
Clair Obscur: Expedition 33 (1903340)
Compatibility Report
- Name of the game with compatibility issues: Clair Obscur: Expedition 33
- Steam AppID of the game: 1903340
System Information
- GPU: RX 6800 XT
- Video driver version: Mesa 25.0.4-cachyos1.2
- Kernel version: 6.14.3-2-cachyos
- Link to full system information report as Gist: https://gist.github.com/HalmyLyseas/45a1eda6ee39d1d16fbaa0960f99ea33
- Proton version: proton-9.0-4e
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
The game crashes during one of the first opening screens, the one about controls and autosave. I've tried with Proton 9.0-4 (attached log), experimental, hotfix, the one provided by CachyOS, same behavior.
Reproduction
Nothing special, as explained above it crashes during one of the first screen before any user input can be provided.
I managed to get past this issue by enabling the Steam overlay thanks a reply on Reddit. Not sure how to requalify or close this bug. As far as I can remember it's the first time a game did require this option for me.
Edit: Patch for the game just dropped and after installing that it now gets past the crash point even with Steam Overlay disabled. Acknowledged in the changelog.
Hello, I'm playing on Archlinux, but the video doesn't work (like the introduction cinematic). I tried with proton hotfix and experimental, but no luck so far.
Maybe I just have to install a codec, but I cannot figure which one. Do you have any idea perchance? I had the same problem with Blue Prince recently btw.
Game starts fine on my end but sounds have a lot of stuttering. Already had a stuttering fix on my pipewire-pulse.conf by changing pulse.min.quantum to 1024/4800 some months ago which fixed the same problem on other games, since then this is the first time getting problem.
If you are using an amd card you might need to use proton experimental for the game to render properly, as proton 9 shows a brightened main screen.
@Ealrann the game is using h264 videos yet isn't currently configured to unlock support for h264, this should be changed in the upcoming days, so the videos will start working automatically. People who have played other games requiring h264 support should already have working videos in this title. You can wait for the changes to go live steam side or you can unlock it yourself with steam steam://unlockh264/ on your terminal.
the game is using h264 videos yet isn't currently configured to unlock support for h264, this should be changed in the upcoming days
That's great to hear.
The game should now unlock h264 support on its own.
@EBertranDiaz I've played for a couple of hours without a single stutter, the problem with this kind of audio stutter is that they are very setup dependent. The better the cpu, the less demanding the game, and the bigger the audio buffer size (which you increase by increasing the minimum quantum), the lower the chance for this kind of stutter to appear. In my case the game is using 280/48000, and I have a 5700X3D.
I had no issues playing the game (steady 60 fps) until I entered Flying Water, after that I got huge lag spikes, with rendering issues (no walls, entities disappearing, etc) always before a cutscene or a fight. It always ends with my DE crashing.
I tried the game with proton experimental, stable latest, 9-27GE with no success.
I also tried using RADV as well as AMDVLK with no success either.
I did the same with linux kernels ranging from 6.14.1 to 6.15-rc3
I also tested Cinnamon and Hyprland DE just in case, both resulted in the same issue.
Specs for the logs: CPU: i5-10400F GPU: AMD Radeon 7800 XT RAM: 32 GB Kernel: 6.15-rc3 Driver: AMDVLK 2025.Q1.3-1 Proton: experimental-9.0-20250402c
System infos: https://gist.github.com/Estyms/86cc825809fd756417c8a4ff46a8d949 Log Gist: https://gist.github.com/Estyms/06fb1f03d9a90f0e321502bbbdc6810c
Update: Using -dx11 the game works well
The game should now unlock h264 support on its own.
@EBertranDiaz I've played for a couple of hours without a single stutter, the problem with this kind of audio stutter is that they are very setup dependent. The better the cpu, the less demanding the game, and the bigger the audio buffer size (which you increase by increasing the minimum quantum), the lower the chance for this kind of stutter to appear. In my case the game is using 280/48000, and I have a 5700X3D.
I managed to fix this by changing default.clock.allowed-rates on pipewire.conf to look like this
default.clock.allowed-rates = [ 44100 48000 ]
been playing for 24h now and found no more audio problems, now the only problem I have is the missed input bug or stuck inputs, but that is an Unreal Engine 5 problem since it also plagues windows users and other games like Oblivion remastered
Hi all,
The game crash consistently after 5-10 minutes of playing, I've tried Proton 9 / hotfix and experimental. I've tried deleting the compatdata folder, modifying the quality setting of the game, restarting the PC, changing Nvidia driver version, verifying game files and using -dx11 but to no avail.
This only happens with this game. I also play Path Of Exile 2 (Vulkan) / Split Fiction / Elden Ring all at max settings without any issues.
Could someone help me ? I'm pretty desperate...
System info : https://termbin.com/jhgo Proton log : https://gist.github.com/Toucan4Life/353a77f74b19cc70758de6c413bc4880
Hello @Toucan4Life, are you able to test with a newer video driver?
These lines in your Proton log hints towards a graphics issue:
err:vkd3d-proton:d3d12_command_queue_execute: Failed to submit queue(s), vr -4.
warn:vkd3d-proton:d3d12_device_mark_as_removed: Device 00000000223f0080 is lost (reason 0x887a0005, "VK_ERROR_DEVICE_LOST").
@Estyms I haven't observed issues yet with flying waters, "M" has already joined the party where I am, as a reference and have gone through a number of fights. My testing has been on mesa 25.0.4, with proton experimental bleeding edge.
If your DE is crashing, and also going by your proton log, there's probably a related kernel log. You can check the kernel log of the current session with dmesg, and you can use journalctl to check previous boot sessions like so journalctl -k -b <num> where a number 0 would be the current session, -1 the previous session, and so on.
I too am having issues; during the first tutorial fight, I had a hard game crash (freezing with the music still playing but no response from my controller or keyboard) and then hard system crash (no system response and control alt function to switch to another tty also gave no sign of life) but with different specs, notably an Nvidia RTX GPU:
CPU: AMD Ryzen 9 7950X
GPU: Nvidia RTX 4090 (with the Nvidia open kernel modules)
Video driver version: 570.144-1
Kernel version: 6.14.4-arch1-1
Proton version: proton-9.0-4
I'm not sure where I can get a log of the game crash; if you need more information, I can try to give it.
@EBertranDiaz about audio stutters, and other who have it:
idk why - but audio freq for pipewire-pulse must be 256/48000 for this game, maybe other UE5 games also
if it any other - it will stutter, I had 512 - stutters - for testing I set 1024 - huge audio delays fully bugged audio
Fix:
copy:
mkdir -p ~/.config/pipewire && \
cp /usr/share/pipewire/*.conf ~/.config/pipewire && \
chown $USER ~/.config/pipewire/pipewire-pulse.conf
open ~/.config/pipewire/pipewire-pulse.conf
find and change to 256/48000:
pulse.properties = {....
pulse.min.req = 256/48000
pulse.min.frag = 256/48000
pulse.min.quantum = 256/48000
Then run:
systemctl --user restart pipewire pipewire-pulse wireplumber
Hi,
@kisak-valve I removed my driver version (Nvidia 550) and switched to version 565 & 570, I still got the same issue. I also tried proton-GE to no avail. I can see these line in the output of dmesg
[ 1542.222580] NVRM: GPU at PCI:0000:06:00: GPU-20f852e5-61e9-dd82-7ce2-11d4885d7606
[ 1542.222586] NVRM: GPU Board Serial Number: 1321621094283
[ 1542.222587] NVRM: Xid (PCI:0000:06:00): 69, pid=7243, name=GameThread, Class Error: ChId 0041, Class 0000c7c0, Offset 000001b0, Data 00000040, ErrorCode 0000000b
@cameronbosch to enable log:
- right-click your game on the steam library
- go to properties
- in the general tab, put this on the launch options
PROTON_LOG=1 %command% - you will see the log file
steam-1903340.login you home folder
@cameronbosch to enable log:
- right-click your game on the steam library
- go to properties
- in the general tab, put this on the launch options
PROTON_LOG=1 %command%- you will see the log file
steam-1903340.login you home folder
Thanks, I'll do this and try again later today and will post the log if the crash happens again.
@Toucan4Life Thanks for the report. Could you attempt to run the game with the latest r575 driver and Proton Experimental? That is what I have used for my initial testing and have not hit a GPU hang yet.
The game works fine on my AMD Radeon RX 7800 XT, but I am seeing an issue with a shader in an early part of the game.
In the area with the first boss fight, there's supposed to be a faint red fog, with most of the area being dark. I'm seeing an extremely intense red fog that brightens the scene instead.
Comparison screenshots (I cropped the image, but the effect is quite obvious):
Correct:
Buggy:
This happened in the default Proton 9 as well as Proton Experimental. This log is from Experimental:
@kisak-valve @esullivan-nvidia I found the issue, it was related to my RAM. I disabled the XMP profile and now everything run well. Thank you for your support guys
Clair Obscur: Expedition 33 (1903340)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/8642. @TheM1Stery posted on 2025-05-01T21:20:49:
Compatibility Report
- Name of the game with compatibility issues: Clair Obscur: Expedition 33
- Steam AppID of the game: 1903340
System Information
- GPU: RTX 3060
- Video driver version: 570.144
- Kernel version: Linux 6.14.4-1-default
- Link to full system information report as Gist: Gist
- Proton version: Proton Experimental
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
Dualsense stops working after you turn off the mouse or the keyboard. You need to restart the game for the controller to work again.
Reproduction
Don't use Steam Input (the game natively supports Dualsense). Start the game and connect your controller to the game. After just turn off your mouse or keyboard. Also connecting a keyboard or a mouse reproduces this bug.
This did not happen on previous version of Proton Experimental. I also checked Proton 9.0-4 and that bug doesn't occur there
Just to update on my previous comment: I think whatever is happening affects just about every environment in the game. Another symptom of the issue is, because the effect isn't attenuating with distance as it should be, it's obvious when the game swaps from one environmental effect to another, as seen here: https://youtu.be/eDoUDnhupAI
Here's what it looks like when a PS5 player walks through that same threshold: https://youtu.be/QyS5AkSyiVI?t=424
You can see that both environments in my game are rendered totally wrong, and while the swap isn't completely seamless on PS5, it's not nearly as obvious.
Update: adding SteamDeck=0 to the launch options - and changing nothing else - completely fixed my issue. I was unable to get the issue to occur with SteamDeck=0, even after trying multiple combinations of different graphics settings.
Responding to https://github.com/ValveSoftware/Proton/issues/8626#issuecomment-2845812523 : @TheM1Stery I also asked this in the other thread - could you please retest this with Proton - Experimental? We believe we have a fix for the random controller disconnection 🤞
Not sure if this would deserve its own ticket but I will post it in here for now I guess:
I have the issue with Clair Obscur that when I try to launch it as is it will go until the screen where it explains the saving mechanism and then it will hang with a black screen. When adding -dx11 to the launch options the game will start but in-game all 3d elements will be low polygon version, i.e. flowers in the initial garden scene will be 4-sided polygons, the floating rocks above will be very basic shapes, etc. Another issue with using -dx11 is that the first few seconds of a cutscene will be just a red screen before the actual animation is visible.
- GPU: RTX 4070 Super
- Video driver version: 570.144
- Kernel version: 6.14.2-1
- Link to full system information report as Gist: https://gist.github.com/Juppstein/46fb66bd000cd67585b7923c455b5e45
- Proton version: Proton Experimental Hotfix
I have seen some others on the Steam forums that had the same issue and apparently this got introduced a short while ago with a game patch. I seems that this issue was not happening when the game was freshly released:
https://steamcommunity.com/app/1903340/discussions/0/592896539385460718/
There is also someone on protondb with a similar issue:
https://www.protondb.com/app/1903340#vfmAuFnjXk
EDIT: A workaround is to downgrade mesa to 25.0.x The recent 25.1.x versions will not allow the game to start successfully
I'm using the SteamDeck Oled with the latest 3.7.8 version of the OS, latest game version too, and the graphics menu is not working correctly:
- The advanced graphic options are not available. Contrary to the other Settings menus, it is impossible to scroll down in this list of options. I tested on Windows with a controller, and it is working fine.
- After having done some simple modifications in the graphic options (I could not point on which one), all the graphic options become not modifiable (edit, only moving in the menu with the controller without changing anything and then press B to exit without changing anything will exhibit this behavior)
I tried to add SteamDeck=0 to the launch options, but it did not change anything. Using Proton Experimental does not change anything too.
Not sure if this is related to proton but appears to be related to given the error message but latest Nvidia new feature branch driver (575.57.08 )causes this error on launch with the game. DX11 mode works without issue but then geometry in the game is not properly rendered.
I’m also seeing the same error as @SimpleHeuristics when launching on the latest Bazzite stable branch, which updated the nvidia driver from 570.153.02-1 to 575.57.08-1.
