Diablo IV - "GPU Not Supported"

[GarMr]

Every time I try to launch Diablo IV from Battle.net it gives me the "GPU Not Supported" window.

And I truly do not understand. This Battle.net and Diablo IV installation is without Lutris or Bottles.

Any help would be appreciated.

Please and Thank you.

[invisible kid]

I think d4 needs d3d12 and I think d3d12 needs vulkan/vkd3d. Do you have those installed? Lately with the blizzard stuff it seems better to give up and go lutris. Search for "Diablo IV" from the lutris installer and install it, it will modify your battle.net/wine configuration and launch battle.net where you can launch d4 from. Right now I am trying on vulkan/vkd3d/wine and d4 says "You need at least Windows 10 (version 1909). Unsupported OS Version (10.0.18362)"

[GarMr]

I think d4 needs d3d12 and I think d3d12 needs vulkan/vkd3d. Do you have those installed? Lately with the blizzard stuff it seems better to give up and go lutris. Search for "Diablo IV" from the lutris installer and install it, it will modify your battle.net/wine configuration and launch battle.net where you can launch d4 from. Right now I am trying on vulkan/vkd3d/wine and d4 says "You need at least Windows 10 (version 1909). Unsupported OS Version (10.0.18362)"

Go into winecfg and "use Wine x64 prefix and add /drive_c/ProgramData/Battle.net/Agent.exe to Windows 11 Version in winecfg i f you get the "No supported OS" error."

I just wanted to see if i was able to make it work without the assist or install of Lutris or Bottles. Can't give up now. So close!

And i do have the latest radeon-vulkan and mesa installed too. However, Is there a specific package for vkd3d (dx12)?

[invisible kid]

Thanks! Will try it. I think original vkd3d is by wine folks, and there is also the proton version that is forked from that I believe. I don't use debian, so I have to build from sources. Most things are the same, but some things are different. So I'm not much help there. I do know debian will usually have a package, and have it tweaked as necessary to run good. Also a lot of debian support and folks so someone might chime in. With nvidia I don't need to install mesa, but I don't think it would hurt either.

Hehe, I like the not giving up part! Actually, I gave up and installed Windows 10 on my ssd, but it wasn't roses there either lol, so still have both going, but am moving back to linux/wine. I am looking forward to trying the new wine version 9 when it rolls out.

[invisible kid]

Hey, been looking at this a bit more and looking at the winehq page that you mentioned. He says that you need to use the proton version of vkd3d, vkd3d-proton. So I think there are debian packages for that right? If not you would have to build it yourself. I have to build it, but before I can do that I need to build mingw(my current pre-compiled version doesn't include x86_64-w64-mingw32-widl) which is a bit of a chore and will take awhile.

[strengthslurp]

I think d4 needs d3d12 and I think d3d12 needs vulkan/vkd3dgeometry dash lite. Do you have those installed? Lately with the blizzard stuff it seems better to give up and go lutris. Search for "Diablo IV" from the lutris installer and install it, it will modify your battle.net/wine configuration and launch battle.net where you can launch d4 from. Right now I am trying on vulkan/vkd3d/wine and d4 says "You need at least Windows 10 (version 1909). Unsupported OS Version (10.0.18362)"

I didn't want to bother installing Lutris or Bottles if I didn't have to, so I set out to see if I could get it to function without their help. Just can't give up now. Wow, that was a close call!
As for my graphics card drivers, I'm using the most recent versions of both radeon-vulkan and mesa.

[invisible kid]

Yeah, I'm just waiting/hoping for a fix external to me. According to
https://appdb.winehq.org/objectManager. ... &iId=41136
someone is able to get the dx11 version working okay, but I'll wait for dx12.

But it looks there are a few new posts. Will check out later.

[ninadobrev]

Yeah, I'm just waiting/hoping for a fix external to me. According to
https://appdb.winehq.org/objectManager. ... &iId=41136 fnf
someone is able to get the dx11 version working okay, but I'll wait for dx12.

But it looks there are a few new posts. Will check out later.

I'm patiently waiting for a fix, but I'm curious about how long it typically takes for the release of a DX12 version in situations like this.

[invisible kid]

Blizzard stuff usually plays nicely with wine. As if they develop with wine in mind. D4 is the first case where I've seen them really lag. It seem as vkd3d-proton works with it, but I don't know why vkd3d-winehq isn't adopting the same changes. But I'm more of a wine guy than a proton guy, so it's just wait and see for me.

Sorry I wasn't really able to answer your question!

[jkfloris]

I'm not really following this thread. But vkd3d-proton can be installed with winetricks.

Code: Select all

winetricks vkd3d

[invisible kid]

Ah okay, thanks! Naming conventions threw me off I think. I will check this out next time I mess around with it.

Do you know if you are building from source if you need to still build vkd3d(-winehq)? Would the basic procedure be:

1. build/install vulkan from source
2. build/install vkd3d(-winehq) from source
3. build/install wine from source
4. create and configure new prefix
5. winetricks vkd3d(-proton)

Or would I skip step 2? Thanks to anyone for any input! I am thinking step 2 still needs to happen or wine won't have any vkd3d calls in the code?

[invisible kid]

I'm thinking you can only use that if you use a debian package. So I think the steps for me when building from source would be:

1. build/install 64 bit and 32 bit vulkan from source
2. build/install 64 bit and 32 bit vkd3d-winehq or vkd3d-proton from source
3. build/install 64 bit and 32 bit wine from source
4. create and configure new prefix

I think winetricks vkd3d might "break" this procedure. Not sure though. It's relatively difficult to get information on building since most people just use apt/debian. I have to build from source because prebuilt packages are expecting/demading a newer version of glibc than I have and that can be a little scary to update.

[larryellison12]

I'm thinking you can only use that if you use a debian package. So I think the steps for me when building from source would be:

1. build/install 64 bit and 32 bit vulkan from source geometry dash bloodbath
2. build/install 64 bit and 32 bit vkd3d-winehq or vkd3d-proton from source
3. build/install 64 bit and 32 bit wine from source
4. create and configure new prefix

I think winetricks vkd3d might "break" this procedure. Not sure though. It's relatively difficult to get information on building since most people just use apt/debian. I have to build from source because prebuilt packages are expecting/demading a newer version of glibc than I have and that can be a little scary to update.

What are the requirements when using the debian package? Can you share the version you have?

[invisible kid]

Hi!

First make sure dual architecture is in effect if you want it. Then, I think you would do an apt-get install for the vulkanlib, then you do a apt-get install for wine. Then I think you would do a winetricks vkd3d, and then a winetricks dxvk.

This is just by memory and may be outdated or just plain wrong. Plus no detail. Hope this can help in some way.

There is also this webpage that might be helpful:

https://wiki.debian.org/Wine