https://bugs.winehq.org/show_bug.cgi?id=54436
--- Comment #8 from kolAflash kolAflash@kolahilft.de --- Replaced the commit ids with git describe infos for comprehensibility. (example: commit deaf0891b09 is wine-7.9-314-gdeaf0891b09, see last 11 digits)
I assume with native you mean "d3dx9_29.dll" from "winetricks d3dx9"! Correct?
(In reply to Austin English from comment #7)
[...] If you use native d3x9, does it not crash at wine-7.9-314-gdeaf0891b09, but does crash at wine-7.22-56-gfd8e52b4e76 ? If so, a bisect (with native d3dx9) between those two commits should identify the problem.
Sadly this seems not to be easily testable, because: ---> With native d3dx9_26.dll and wine >= 7.9-314-gdeaf0891b09 the application sometimes immediately crashes and sometimes gets to the main menu.
With this in mind: ---> My bisect regarding native d3dx9_29.dll working (with glitches) with wine
= 7.9-314-gdeaf0891b09 may have been incorrect!
But the bisect with builtin d3dx9_29.dll seem to be fine. ---> So I suggest to debug the Wine buildin d3dx9_29.dll regression with wine-7.8-192-g4a98b07c4bc first.
If that is not the case, then I'd suggest trying wine-7.8-192-g4a98b07c4bc , then cherry-pick wine-7.9-314-gdeaf0891b09 and/or wine-7.22-56-gfd8e52b4e76 and see how that behaves.
wine-7.9-314-gdeaf0891b09 and/or wine-7.22-56-gfd8e52b4e76 conflict if being applied on wine-7.8-192-g4a98b07c4bc Unfortunately I don't know enough about the Wine code to resolve these conflicts, so I can't test that.