http://bugs.winehq.org/show_bug.cgi?id=32559
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Component|msvcrt |-unknown Summary|Warlock - Master of the |Warlock - Master of the |Arcane 1.4 crashes on |Arcane 1.4 (Steam) crashes |startup |on startup
--- Comment #20 from Anastasius Focht focht@gmx.net --- Hello Alexander,
unfortunately the trace log you attached is too short. The backtrace/page fault is a secondary one, the real damage had already been done before.
Within the log I spotted this:
--- snip --- 240019.969:002a:Ret dbghelp.MiniDumpWriteDump() retval=00000001 ret=00402a55 ... <crash here> --- snip ---
The app installs its own crash handler which calls dbghelp.MiniDumpWriteDump() on unhandled faults. Unfortunately the call is not in your log file.
Please generate a new log. Also use 'append' mode because the app is multi-threaded which tends to produce interleaving messages, messing up the trace.
--- snip --- $ WINEDEBUG= ... >>log.txt 2>&1 --- snip ---
BTW .. I found a distributed 'backup' for testing. The game starts for me in clean WINEPREFIX without crash.
After the intro animation/splash screens, a main menu is shown with some wizard guy and glowing effects on the left hand side.
The main menu isn't actually visible because of this:
--- snip --- fixme:hlsl_parser:hlsl_parse Array. err:d3dcompiler:compile_shader HLSL shader parsing failed. --- snip ---
After doing 'winetricks d3dcompiler_43' the main menu is properly shown and I was able to play the game. The d3d compiler shortcoming is definitely a dupe of existing bugs.
Did you really install the game in an own, clean WINEPREFIX? Installing multiple games and their prerequisites in the same prefix tends to mess it up at one point, leading to crashes.
Regards