https://bugs.winehq.org/show_bug.cgi?id=47129
--- Comment #11 from Paul Gofman gofmanp@gmail.com --- (In reply to BieHDC from comment #10)
Indeed its a directory issue. For example i start steam like this:
WINEDEBUG=-all wine64 .wine/drive_c/Program\ Files\ (x86)/Steam/Steam.exe -no-cef-sandbox<<
which works fine.
and i have started ballerburg like this:
WINEARCH=win32 WINEPREFIX=~/.ballerburg wine "/home/biehdc/.ballerburg/drive_c/Program Files/Ballerburg/Ballerburg.exe"<<
and it fails.
Not all programs are the same, some behave completely different. This game needs to be started from its directory, it uses relative path to open its files and crash when it can't find them. BTW it is rather common case. If you start a game from, e. g., Steam, or desktop menu link, those starters set directory for you.
As for the crash, I now don't see any Wine issue here.
Rendering glitch discovered between the lines of this bug should be now fixed by commit 08d630e250d24d6f0f8c1f6106dff0397b4d058e.