Diablo II

ok i managed to solve the problem by enabling dlss while running the sbo package lutirs and this solved the problem, no more blocky graphic glitches. Graphics run flawlessly although occasionally the game hangs on quitting. Still a major improvement.
Lutris really simplifies running this game. But for the rare hanging on quitting i would rate this game platinum now.

I'm running version 1.5.73090 of D2R (according to the Blizzard launcher).

The game was running real fine up until today. I even played today, but I did force kill the game as it didn't want to close. Then, I tried reopening it and I got a Blizzard crash window.

I tried reinstalling the game from scratch and I got the same behaviour. The error found in the file 'blz-log.txt' is:

```
3/18 15:15:50.157 [Prism/4] [:0]: prism: Error Invalid (0x887a0004): pm_dxgi::Instance::InitSwapChain: CreateSwapChainForHwnd Failed

3/18 15:15:50.159 [Render/4] [:0]: NVSDK_NGX_D3D12_Init failed, error code: -1160773631
```

The file `dxdiag.txt` showed:

```
------------------
System Information
------------------
Time of this report: 3/18/2023, 15:15:49
Machine name: LEVIATHAN
Operating System: Windows XP Professional
Language: French (Regional Setting: French)
System Manufacturer:
System Model:
BIOS:
Processor: AMD Ryzen 9 3900XT 12-Core Processor(24 CPUs), ~4775MHz
Memory: 32042MB RAM
Page File: 9914MB used, 46704MB available
Windows Dir: C:\windows
DirectX Version: DirectX 12
DX Setup Parameters: Not present
DxDiag Version:
```
Finally, I uploaded the file `Crash.txt` on a pastebin here: sprunge.us/AWwQjZ.

I tried the lutris' equivalent of this release:

github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton7-51-diablo_4_beta

and it did fix the issue. Thanks.

It's funny that you would use that particular wine variant as it was meant for diablo 4,
but if that works for you that's ok (although i don't know how stable it will be).

So basically looking for help to debug. No package mangement system or anything, just LFS based distro, building what I can from source, 64 bit and 32 bit.

I had to stop using
winetricks dxvk
as it would remove my dx12 support after it was applied

and without it, it launches and runs for awhile, so the plumbing looks mostly correct.

I built vkd3d from winehq(not -proton).
I also built vkd3d-proton, but doesn't look like when I compile wine it will use it.

wine-7.14 (Staging)
NVIDIA-Linux-x86_64-515.65.01.run
Vulkan Instance Version: 1.3.224


Any help appreciated, even if it is directing me to ask somewhere else.

lfs for me was an interesting exercise in just what it takes to do linux from scratch but i had more luck with slackware or linux mint not that you
wouldn't learn something from this sort of thing and maybe, MAYBE you could actually figure this out if you were a programmer or could code.

Thanks for your reply!
Yeah, the last time it was working I was using 6.19 staging and a very specific vkd3d-proton patch applied afterwords. I was trying and trying not to update, but something else made me want to.

I do program in c/c++ so maybe that can help, but I'm not sure. I have a pretty weird nvidia card, so maybe it's a bug within that. I launched d2r with default logging and saw no error message that would help. When it crashed it didn't appear to add any info to the logs.

Yeah, wine still follows the ./configure/make/make install paradigm, but the vulkan/vkd3d codebase uses meson and I have to create these weird links within subprojects pointing to official versions. Sometimes having to patch incorrectly generated Makefiles. Just a complete mess and I suppose they like it that way.

I am wondering if there is a better place to post this. I mean maybe I should even start at nvidia support? I am lost. Even if I knew it was a bug to be fixed in the future.

One thing I noticed is the black textures are completely gone, which made me fall back to NVIDIA-Linux-x86_64-470.129.06.run. Maybe I'll play around with other versions of nvidia drivers and see if there is any change.

So I fell back to
NVIDIA-Linux-x86_64-470.129.06
since that was the latest nvidia driver that was solid
and it appears to have cleared up the crash!
I didn't do an extended test on d2r
but wow used to insta-crash when dx12 was selected, which now it doesn't
NVIDIA-Linux-x86_64-470.129.06
causes me other issues(does not wake up from sleep, power management needs to be disabled)
so I tried
NVIDIA-Linux-x86_64-495.46
which is the current Latest New Feature Branch Version which wakes up correctly
and appears to run wow dx12 okay, so i will test d2r tonight
fingers crossed!

Yeah i like using nvidia-470.74 series (if you read my other comments) and this also clears the graphical errors (blocky black textures particularly in act 2 far oasis)
and i have a comment in an existing post at nvidia's forums (forums.developer.nvidia.com/t/nvidia-495-44-regression-graphical-glitches-in-diablo-2-resurrected/193329)
concerning this very error. Of course your functionality may be a bit less with 470.74 but there you have it. I don't get it, what is nvidia's problem here anyway
this was an old post and the error still exists ?! Maybe they have bigger problems, who knows. These days everyone seems to be having a time of it for
some reason. Who can really blame them with a plethora of different linux flavors still i would like the matter to be acknowledged in a more timely manner
if possible.

Yeah, I've stumbled across a gpu vulkan status page via running vkconfig:
vulkan.gpuinfo.org/listreports.php
id Device Driver Api Vendor Type OS Version Platform
13539 NVIDIA TITAN X (Pascal) 472.12.0.0 1.2.175 NVIDIA discrete windows 7sp1 x86_64
So the last report recommends 472.12 for my card which isn't even kept in the nvidia archive.

When I updated the VulkanSDK version, the black textures went away on all of my nvidia driver version tests, but obviously introduced this crash bug which is much worse.

But this might be the end of the road for me. Building Vulkan and associated tools is a complete mess, probably by design.
Maybe I'll just wait and retry major new versions of nvidia/vulkan/vkd3d/wine/d2r.

Thanks for the replies!

well i have vulkan sdk 1.2.176.1 and you say the crash bug happened and the black textures went away when you updated your sdk but
i was wondering what version you were using ? Maybe we are getting some where on this.

I didn't save off my previous versions of libvulkan, but I saved off my earlier installed libvkd3d libs:

libvkd3d-shader.so.1.0.0
libvkd3d-utils.so.1.0.0
libvkd3d-utils.so.1.0.1
libvkd3d-utils.so.1.1.0
libvkd3d.so.1.0.0
libvkd3d.so.1.1.0
libvkd3d.so.1.2.0

now they are:

libvkd3d-shader.a
libvkd3d-shader.la
libvkd3d-shader.so -> libvkd3d-shader.so.1.2.0
libvkd3d-shader.so.1 -> libvkd3d-shader.so.1.2.0
libvkd3d-shader.so.1.2.0
libvkd3d-utils.a
libvkd3d-utils.la
libvkd3d-utils.so -> libvkd3d-utils.so.1.3.0
libvkd3d-utils.so.1 -> libvkd3d-utils.so.1.3.0
libvkd3d-utils.so.1.3.0
libvkd3d.a
libvkd3d.la
libvkd3d.so -> libvkd3d.so.1.4.0
libvkd3d.so.1 -> libvkd3d.so.1.4.0
libvkd3d.so.1.4.0

Not sure if this will help at all, but it's all I have. I don't even remember the providence of them as I would use precompiled binaries, and also doing try this and try that type of stuff. Then not breathing on it once it is working. One of the thing git seems to encourage is using the bleeding edge version of each component when "cloning", so it's not even tied to a specific version number.

Wine is also packaged with a version of vkd3d, I might try a build today if I can force it to build its internal version. Then try winetricks dxvk and/or installing vkd3d-proton afterwords.

I built wine 7.12 using it's bundled version of vkd3d, but got the same results, so it kinda looks like my issue is with vulkansdk and/or my nvidia titan x, so I will concentrate on that and hassle those folks if I can find a place. Building vulkansdk manually, especially if you do it piece-by-piece is one of the worst things you can go through(lol), so I will probably just give up for a long while. Here is the stdout of my last try with the latest versions of everything just in case:

[0814/102305.939:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0
[0814/102306.543:ERROR:dxva_video_decode_accelerator_win.cc(1397)] DXVAVDA fatal error: could not Lo
adLibrary: msmpeg2vdec.dll: Module not found. (0x7E)
[0814/102306.694:ERROR:dxva_video_decode_accelerator_win.cc(1320)] DXVAVDA fatal error: Could not lo
ad msmpeg2vdec.dll: Module not found. (0x7E)
[0814/102308.979:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0
fixme:d3d12_device_get_vkd3d_queue Unhandled command list type 0x1.
fixme:d3d12_rtv_desc_create_rtv NULL resource RTV not implemented.
fixme:d3d12_dsv_desc_create_dsv NULL resource DSV not implemented.
fixme:d3d12_desc_create_sampler Ignoring border color {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}.
fixme:d3d12_desc_create_sampler Ignoring border color {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}.
fixme:d3d12_desc_create_sampler Ignoring border color {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 0.00000000e+00}.
fixme:d3d12_desc_create_sampler Ignoring border color {1.00000000e+00, 1.00000000e+00, 1.00000000e+00, 1.00000000e+00}.
fixme:d3d12_desc_create_sampler Ignoring border color {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}.
fixme:d3d12_desc_create_sampler Ignoring border color {0.00000000e+00, 0.00000000e+00, 0.00000000e+00, 1.00000000e+00}.
fixme:d3d12_desc_create_srv Unhandled view dimension 0x2.
fixme:d3d12_command_list_DiscardResource iface 000000000130B690, resource 000000000130B120, region 000000000041E320 stub!
fixme:vkd3d_dxbc_compiler_check_index_range Unhandled index range write mask 0x1 (0xf).
fixme:vkd3d_dxbc_compiler_emit_dcl_index_range Ignoring dcl_index_range 0x6 3.
fixme:vkd3d_dxbc_compiler_check_index_range Unhandled index range write mask 0x1 (0xf).
fixme:vkd3d_dxbc_compiler_emit_dcl_index_range Ignoring dcl_index_range 0x6 3.
fixme:vkd3d_dxbc_compiler_check_index_range Unhandled index range write mask 0x1 (0xf).
fixme:vkd3d_dxbc_compiler_emit_dcl_index_range Ignoring dcl_index_range 0x6 3.
fixme:vkd3d_dxbc_compiler_check_index_range Unhandled index range write mask 0x1 (0xf).
fixme:vkd3d_dxbc_compiler_emit_dcl_index_range Ignoring dcl_index_range 0x6 3.
fixme:vkd3d_dxbc_compiler_check_index_range Unhandled index range write mask 0x1 (0xf).
fixme:vkd3d_dxbc_compiler_emit_dcl_index_range Ignoring dcl_index_range 0x6 3.
fixme:vkd3d_dxbc_compiler_check_index_range Unhandled index range write mask 0x1 (0xf).
fixme:vkd3d_dxbc_compiler_emit_dcl_index_range Ignoring dcl_index_range 0x6 3.
[0814/102407.216:ERROR:mf_video_decoder.cc(747)] Unsupported codec by MfVideoDecoder: 6
[0814/102506.890:ERROR:dxva_video_decode_accelerator_win.cc(1397)] DXVAVDA fatal error: could not Lo
adLibrary: msmpeg2vdec.dll: Module not found. (0x7E)

Backing out of the indent...

Found something interesting.
I was able to straighten out some configuration issues via vkconfig.
And I noticed you have to leave it running to override settings if it is configured that way.
I also notice that if I run it as my main user instead of root, it has some Steam settings in there.
And the khronos validation layer is the only one that is set to be forced on.
So I leave it up and running and launch battle.net and then d2r.
And notice warnings that since a debug version was built it will degrade performance.
And it brought it down to like 5 fps.
But the black box textures are back. Although a wee bit different in shape from last time.
So I went back and built release versions.
And it still degrades performance by roughly half or so.
I left it running for like 30 mins and it didn't crash.
But that could just be due to not hitting race conditions because of the slowdown.
Investigation continues...

Actually i was asking about your vulkan-sdk version because if you match the vulkan-sdk version to the driver version this just might stabilize things!
If you look at the chart you were referring to (vulkan.gpuinfo.org/listreports.php) you can see the matched versioning. This is may be why the blocky black textures
went away for me in d2r. I am using Slackware 15 64 bit multilib so i have a certain version of vulkan-sdk which is how i was able to notice the match.
Also i was wondering what sort of lfs flavor linux you were using out of curiosity.

Yes! I am following same path. I may try building vulkansdk 1.2.176.1, but I am going to hold off on that for now. I have other things that I have to do first. So I am going to leave current set up for a bit. I'm just using LFS/BLFS 8.3 as the main starting point, but they don't support multi-arch and vulkan, so you have to kinda go it on your own for that stuff.

hmm i tried upgrading my vulkan sdk (vulkan-sdk-1.3.204.0-x86_64-1.txz) to go with my more up to date nvidia 515.57 and still no luck with d2 res, i
still get the stupid blocky artifacts. I feel i am close but maybe i missed something. however i was not able to do the 32 bit multilib.
It's funny that something seems to go wrong after nvidia-470.74. I don't get it i am pretty sure that nvidia knows or maybe doesn't care
or perhaps can't fix it.

Yeah, it's hard to nail down. When I build new vanilla versions of everything the black boxes completely go away. They go away with every nvidia driver i have tried, even the 515 ones. In my testing, VKD3D-proton seems to add the black boxes and gets rid of the crashing issue. But I think it's easy for me to get misguided here. Debian seems really good on picking the versions that work together well and setting up configurations. Building from source you use different packages(VKD3D-winehq vs. VKD3D-proton) so it's a bit like touching an elephant and only describing a portion of the process. I can see nvidia/vulkan/vkd3d kinda fighting over who's problem it is.

I just confirmed upon downgrading to 470.74 from nvidia 515.57 the blocky graphics artifacts
are gone. I guess newer isn�t always better at least in this case.
with these older (and in this case better) drivers i would have to say the game runs with a gold status.

It works fine, but the loading time of the game is like - attion here it comes - hell, takes up to 8 minutes to start the game, but then it works flawlessl.

That shouldn't be happening. It loads up fully to the character selection screen in under 20 seconds for me.

yeah it may not be a big deal not having full lobby channel functionality but some people like this. Using steam proton can give more full functionality in that regard
as well as perhaps more stability. Such as in the Arch Linux x86_64 entry which is what i am now using. I recommend using stable steam and not beta. Also
i am using proton-ge series which seems to be working out well too.

what lobby channel functionality is missing? there may be some functionality i just didn't realize even existed since i havn't ran d2r much outside of my current setup

note, i was kind of on the fence about whether to rate this platinum or gold, but the definition of gold really seemed to be based needed "with workarounds", and i didn't use any workarounds, so i figured it was closer to platinum since playing the game seemed flawless to me.

i am wondering if there is an easy fix/missing package that would get the lobby images to show up...

well it is working quite well but as i was saying using proton in steam makes all the avatars of peoples characters show up, i wouldn't know why this is, i have used the latest wine-staging with a shell script
and i do not get full functionality as i have said also speech to text does not work. so i would not rate it platinum per say unless you would get full functionality as in windows.
Still it is quite use able so still that is a win. If Blizzard would release a linux client that MIGHT help and it would be a challenge for blizzard considering the many linux variants so i
wouldn't hold your breath for one.

I have also tried to run this on my laptop (integrated nvidia graphics gtx896m) and the game starts ok from the battle.net app but hangs and
crashes on login to bnet. The difference also being i am running on slackware 15 multilib 64 bit. My laptop is an optimus laptop and i have the graphics
set up right from what i can see so i don't get what is happening. I do have some out put in a log file so maybe some one can make something out of it.

Problem: Black screen as described here.
appdb.winehq.org/objectManager.php?sClass=version&iId=40193&iTestingId=110986
> black screen with the cursor being seen and able to move around.

Workaround:
github.com/HansKristian-Work/vkd3d-proton/issues/625#issuecomment-926244808

My test results and setup description:
appdb.winehq.org/objectManager.php?sClass=version&iId=40193&iTestingId=111193

Update:
Played through the whole game (5 acts, normal difficulty) as sorceress.
Played alone and with 2 players in multiplayer.
Detail level on very high.
-> No issues at all!