https://bugs.winehq.org/show_bug.cgi?id=47651
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Chiitoo from comment #3)
Yeah, I think this can be closed for now at least.
I still don't know what it is with those two prefixes, and why the issue happens with only the specific commit reverted (or by not using Staging), but it does not happen in a really clean prefix and a new install of the application even after updating it.
I probably skipped some testing due to having found a commit that made a difference (though it didn't look like one that should), so apologies for that!
It might be possible that the application on first run selects a depth buffer format (which happens to be WINED3DFMT_D32_UNORM if available), saves it in some configuration file and proceeds to crash and burn on following runs if it's not available anymore.
Resolving INVALID for the time being, thanks for reporting the bug and feel free to reopen it if new info comes to light.