[Bug 30993] New: diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

Bug #: 30993
           Summary: diablo 3 d3d device error
           Product: Wine
           Version: unspecified
          Platform: x86
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: directx-d3d
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]
    Classification: Unclassified

Created attachment 40680
  --> http://bugs.winehq.org/attachment.cgi?id=40680
WINEDEBUG=trace+d3d output

when running diablo 3 on wine version d35cb8164a7635201c2ccdf73de2a78cebf6cb94
the game comes up with a fullscreen grey window (same as windows just before 3d
loads)
and gives an alert box with this message:

"graphics error
click to retry creating d3d device
click ok to retry"

clicking OK a few times changes the message slightly, to have retry/cancel,
retry just keeps retrying, cancel gives up as expected

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #1 from Austin English  2012-06-24 14:04:24 CDT ---
Sounds like bug 28201.

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #2 from michael bishop  2012-06-24 16:35:44 CDT ---
comments say its fixed, and ive got a git version past that fix

and in my case its happening on the first startup, rather then after any
changes, should i try to get more info?

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #3 from michael bishop  2012-06-26 15:51:08 CDT ---
after some trial and error, i think i found the initial problem

err:xrandr:X11DRV_XRandR_SetCurrentMode Resolution change not successful --
perhaps display has changed?

it seems to be failing to change my Xorg resolution for fullscreen play
manually setting it to windowed mode in the config file gets past that and
gives a new error

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #4 from michael bishop  2012-06-26 15:52:12 CDT ---
Created attachment 40737
  --> http://bugs.winehq.org/attachment.cgi?id=40737
a short winedbg session

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

Frédéric Delanoy  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #5 from Frédéric Delanoy  2013-04-13 13:11:57 CDT ---
Does this still happen with current wine (1.5.28 or later)?

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #6 from michael bishop  2013-04-16 07:20:43 CDT ---
its been too long, i don't remember how to reproduce the issue...

all i can get out of it is 'diablo 3 cannot run because this graphics card is
missing required features'

and this:

ERROR:  
        Could Not Find D3DKMTEscape in gdi32.dll
        Could Not Find D3DKMTOpenAdapterFromHdc in gdi32.dll

currently on wine-1.5.27

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #7 from Henri Verbeet  2013-04-16 09:27:24 CDT ---
(In reply to comment #6)
> all i can get out of it is 'diablo 3 cannot run because this graphics card is
> missing required features'

I don't know the exact requirements for Diablo 3, but if you're on a GeForce Go
7300, that could very well simply be true. Perhaps most significantly, NVIDIA
doesn't implement the ARB_shader_texture_lod extension for those cards, so it's
going to be limited to shader model 2.

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #8 from michael bishop  2013-04-16 12:37:37 CDT ---
now that i think of it, i was doing most of that testing on a dual-boot
desktop, that did run it under windows

but i'm a bit confused as to why that desktop didnt have linux anymore until
just last week, i dont remember removing it, maybe its a different box, lol

let me try installing it on the same hardware that can run it on windows, and
see what that says

[Bug 30993] diablo 3 d3d device error

http://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #9 from michael bishop  2013-04-19 13:37:01 CDT ---
when i run it on a dual-boot system, it also says 'diablo 3 cannot run because
this graphics card is missing required features, updating your driver may fix
this'

the hardware in that system is

01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220]
(rev a2)

but if i boot that system into real windows, it runs without any issues

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #10 from [e-mail] ---
I found few other bugs that have the same issue.

D3DKMTOpenAdapterFromHdc

is mentioned here

https://bugs.winehq.org/show_bug.cgi?id=35598
https://bugs.winehq.org/show_bug.cgi?id=24234
https://bugs.winehq.org/show_bug.cgi?id=29777

"A quick google of D3DKMT nets me this little two year old gem ...

"GPU Used Dedicated Memory and GPU Used Dynamic Memory are detected using
D3DKMT calls, and so they are video adapter manufacturer independent. They
represent the dedicated (on-board) memory usage, and the dynamic (off-board)
memory usage. ...

...

Please note that D3DKMT is an unofficial and undocumented interface, and NVAPI
is a properitary non-public interface. Due to the manner of those interfaces
they are not documented, not explained by their inventor or designer, and so
it's not easy to know anything 100% accurate and specific about the values they
provide."

It might worth asking CCP if they really need to be making undocumented system
calls.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff547047%28v=vs.85%...

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #11 from [e-mail] ---
Sorry for reopening the thread,

but I'm having the d3d device error and everything I've seen on internet
doesn't fix anything for the moment. That includes:
Changing screen resolution 
Add keys to HKCU direct3d videomemorysize, directdraw, etc.
My wineprefix is set to 32bit. I've checked all the driver and driver libs to
be 64 and 32 bits.

And here my final question, my cpu is a i5-5675 from intel. It has an
integrated iris hd pro 6200. Is is possible that not all the functionalities
are available with the current driver?

After the grey screen starting diablo 3 an error says that my gpu doesnt meet
the required features (I don't know the exact translation), however I've been
playing diablo 3 with nvidia GT9400m (about 6 year old). So the new one should
run everything.

any clue please?

Arturo

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

felix moreno  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #12 from felix moreno  ---
wich version of drivers and os using? Maybe was the not update drivers problem
with mesa.

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

[e-mail] changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #13 from [e-mail] ---
Is this really an issue? I have no issues starting diablo3.

I have done latest tries against wine 2.0 series.

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

Joe Russell  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |russell.josephrussell@gmail
                   |                            |.com

--- Comment #14 from Joe Russell  ---
Using wine-2.0-rc3 (Staging) and Diablo III has just updated to 2.4.3. 
Everything worked great until update.  When I try to run the game in 64 bit
after that I get the grey screen and the error creating d3d.  Click ok a couple
of times and it then gives you the option to retry/cancel and will do nothing. 
If you go to the battle.net app and go to game settings and change it to "Open
game with 32-bit version instead" it will open just fine...

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #15 from Joe Russell  ---
I should also mention that I am currently using i7 3770K and Geforce 680
graphics and reiterate that everything worked until the update to battle.net
2.4.3

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

Naf  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #16 from Naf  ---
Same Bug as have Joe Russell

Winehq 2.0-rc4
Ubuntu 16.04 64bit (latest updates)
Intel® Core™ i7-4510U CPU @ 2.00GHz × 4
GeForce 840M/PCIe/SSE2
Battle.net 1.6.0.8265 (2.9.2.5362)
Diablo 3 2.4.3.42934

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #17 from Naf  ---
Created attachment 56821
  --> https://bugs.winehq.org/attachment.cgi?id=56821
Diablo 3 Debug Log

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

Józef Kucia  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from Józef Kucia  ---
(In reply to Naf from comment #17)
> 2017.01.11 22:32:10.480508800	Closing Direct3D11 window.
> 2017.01.11 22:32:10.480657600	Opening Direct3D11 in 1920x1080 fullscreen mode.
> 2017.01.11 22:32:10.523861400	ShellCreateWindow: GfxWindowOpen: Failed
> 2017.01.11 22:32:10.524167600	ERROR: [D3D Error] Diablo III was unable to initialize D3D. Click OK to retry.

This seems to be a problem with recently added D3D11 renderer. It doesn't seem
to be related to the issue originally reported in this bug report. It would be
better to file a new bug report for problems related to D3D11 renderer.

[Bug 30993] diablo 3 d3d device error

https://bugs.winehq.org/show_bug.cgi?id=30993

--- Comment #19 from Naf  ---
(In reply to Józef Kucia from comment #18)
> This seems to be a problem with recently added D3D11 renderer. It doesn't
> seem to be related to the issue originally reported in this bug report. It
> would be better to file a new bug report for problems related to D3D11
> renderer.

Ok, Created - https://bugs.winehq.org/show_bug.cgi?id=42191

[Bug 30993] diablo 3 d3d device error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=30993

joaopa  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #20 from joaopa  ---
Does the bug still occur with wine-5.12?

[Bug 30993] diablo 3 d3d device error

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=30993

Maciej Stanczew  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #21 from Maciej Stanczew  ---
With Wine 6.12 both 32-bit (D3D9) and 64-bit (D3D11) game clients launch
correctly for me (although I'm using a dedicated AMD GPU, which is a completely
different setup). Could possibly be related to bug #45443.