I got an apitrace of crash on experimental and working dxvk version (7.0-6). Thank you for the help @Blisto91! The files are way too big to upload, so I uploaded them here with unlock code "apitrace" : https://www.codeweavers.com/xfer/alasky/blazblue-traces/
Unfortunately both apitraces replay just fine. I don't have access to the game either.
d3d9.textureMemory = 0 fixed for me.
Yes it's a issue with the new memory unmapping feature introduced in 2.0. The above option disables it when set to 0.
This appears to be an off-by-one bug in the game. If I pad the allocation for the texture by literally just 1 byte, it works.
This now happens again in Proton 8.0-1 again.
That's most likely an unrelated issue then. Please report that over on the Proton issue tracker.
That's most likely an unrelated issue then. Please report that over on the Proton issue tracker.
Oh sorry I thought I was lol
proton 8.0-1x1 2023-04proton 7.0-6x1 2022-12proton experimentalx1 2022-12
Software information
Blazblue: Centralfiction (586140)
Reported by folks here: https://github.com/ValveSoftware/Proton/issues/1031#issuecomment-1355716116
Blazblue: Centralfiction crashes when selecting Mai Natsume. The easiest way to test this is:
System information
Reproduced on Steam deck
Apitrace file(s)
Instead of getting this, I bisected the regression. It appeared to bisect cleanly and blamed:
commit 6ca6554452543cca14daf017437c5b7b3e848909
Author: Robin Kertels [email protected]
Date: Wed Mar 16 02:28:22 2022 +0100
Please let me know if apitrace would still be useful to try to obtain.
Log files