Thank you for the issue.
While i have not reproduced something as bad as shown in the video so far i am seeing small colored artifacts showing up in the main menu on both AMD and Intel.
I have bisected this to start with commit https://github.com/doitsujin/dxvk/commit/fd9b561100b1fd3dd47a959f4687c16d2d526fe2
Apitrace: https://drive.proton.me/urls/T2MPTPCCX4#GVDrD9UFxwfQ
Edit: On second look i was mistaken about the AMD part. So maybe this is unrelated
Trace replays fine here.
Game also renders fine on my 6900XT.
Probably a driver issue specific to RDNA4, those things are not exactly unheard of.
Wild guess, but can you test if this branch works around it: https://github.com/doitsujin/dxvk/tree/radv-no-secondary
Build should be here once CI is done.
Hey I just came back from easter vacation, and realized that this was meant for me.
Unfortunately I can no longer repro the visual glitches, it seems to have been fixed somehow, I suspect by a patch to the game itself. It might have been an issue with cached shaders.
However I suddenly started getting really bad performance when I start the game and enter the 3D world, it only runs at around 15-25 fps, where it used to be a consistent 60. The main menu still renders at 60.
Not sure if these are related, I will try the artifact you provided to see if that has any effect. But I suspect they are separate issues.
Nevermind the performance issues. I found out that it was caused by me leaving the dll's for the apitrace in the executable folder, since I wrongly assumed they needed a launch command to be used. Deleting them solved the performance issue.
But good news, I was able to find the trace file from when I originally ran into the visual glitches. I thought it didn't work initially because proton dumps them in the steamuser user folder instead of my username.
Updating the original post with this link too.
Again, replays fine. My money is on a radv bug that's exclusive to RDNA4.
@S-N-D-R Do you know if anything has changed in regards to this with driver updates?
As mentioned before on April 22, I was not able to repro this issue. And it has not occured again ever since. I suspect the cause might have been mis-compiled shaders that got sorted out over time, or a fix from the game's devs. Since there was no driver update in the interim as far as i can remember.
This ticket can be closed as far as I'm concerned. Unless you feel there is some broader issue that needs to be fixed?
Feel free to comment here again if it shows up
ge-proton9-25x1 2025-04ge-proton9-26x1 2025-04proton experimentalx1 2025-04proton hotfixx1 2025-04
Getting some really bad visual glitches in Blue Prince recently after updating to latest versions of GE-Proton9 (27). Also tried GE-Proton9-26, Proton Hotfix, UMU Proton, and Proton Experimental as well as the bleeding-edge beta branch of Proton Experimental. Those also glitch out, but it seems to be in different ways. I either get these flickering triangles radiating around the center of the screen, or certain surfaces in the game flicker with this multicolored glitchy pixel trash.
https://www.youtube.com/watch?v=ExKWmLgSSaU
This video was captured with Proton Experimental [bleeding edge], and is by far the worst glitches i have encountered. It shows a combination of all the different glitches I saw on different proton versions, and at a much higher magnitude.
Sometimes it's instant from boot, other times it takes a while to kick in and then comes and goes at random times. It's quite inconsistent. I have not been able to reproduce the glitches in the video since. Except some minor glitches on the logos in the startup screen.
Switching back to base Proton 9 or GE-Proton9-25 seems to have resolved the issue. Which indicates a regression of sorts. I brought this up in the GE Discord and was told to report it here.
Software information
Blue Prince (https://store.steampowered.com/app/1569580/Blue_Prince/)
No special settings, running everything at default at 4K.
System information
Apitrace file(s)
https://www.dropbox.com/scl/fi/n5qo0n55sfv1rrocwl1ci/BLUE-PRINCE.trace.zip?rlkey=22a3brb7fxtqzfizqvj4kxupx&st=2a8apw52&dl=0)
Log files
The log file appears to be too large to upload, so I am sharing it through my dropbox:
https://www.dropbox.com/scl/fi/gud1q25blo2qz787o2v30/steam-1569580.zip?rlkey=79ug3mguxz4f2r9zmkujlkbbw&st=yz4s8cig&dl=0