https://bugs.winehq.org/show_bug.cgi?id=40479
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW
--- Comment #3 from Matteo Bruni matteo.mystral@gmail.com --- The game requires d3d11 so I don't expect it to work decently in the shortest term.
That said, it currently crashes very early in the startup process. From the relay trace it seems to crash "immediately" after d3d11.dll and its dependences are attached to the Overwatch.exe process. The crash itself is quite weird, apparently it's a STATUS_ACCESS_VIOLATION when executing game code but the relevant instruction is very suspicious ("leave" for the attached backtrace while I get "sbbl $6740e54f,%eax"). I don't know if that's winedbg screwing up though.
I haven't really looked further yet and I'm not sure I'll have time to :/ I wasn't able to attach winedbg at the game process start (with a small hack to delay execution of the game code), winedbg hangs in that case.
For the records, the game is in open beta until May 9. If someone wants to take a look this is a good time ;)