https://bugs.winehq.org/show_bug.cgi?id=47651
Chiitoo escomk3@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Status|RESOLVED |UNCONFIRMED
--- Comment #5 from Chiitoo escomk3@hotmail.com --- (In reply to Matteo Bruni from comment #4)
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.
That does seem plausible, and makes things make more sense to me, too.
I gave it a go with Wine 4.11, installing the PlayOnline Viewer in a clean prefix, then after the first start, launching it with 4.17 will indeed produce the error.
However, if I use 4.17 for the first start, then 4.11 will work as well (and 4.17 keeps working after that too).
The traces seem to be talking about 'WINED3DFMT_D32_UNORM' quite a bit too.
Example steps to reproduce (no subscription needed):
1. Download the installer files ( http://www.playonline.com/ff11eu/download/media/install_win.html ). 2. Run 'FFXIFullSetup_EU.part1.exe'. 3. Run 'FFXISetup.exe'. 4. It will be enough to select the 'PlayOnline Viewer' only for installation. 5. Run 'pol.exe' using Wine 4.11 (or with the discussed commit reverted). 6. Close the PlayOnline Viewer. 7. Run 'pol.exe' again using Wine 4.17 (or without reverting the commit).
Re-opening for now, as this does seem like rather unwanted behaviour.