False alarm anyway. After additional stress testing for the last 3-4 hours. I still get artifacting and crashes at Shenk. For instance, I watched the wattage roll as high as 270 (from baseline roughly 140 at 1v) before the thermal throttling set in and the FPS tanked (then kernel fault client crash). That was with me running around like crazy throwing lighting fury during a Shenk storm with burning archers and quill rats all over the place, BC/BO and forts on me and merc, plus auras.
Anyway, itās way more stable at fixed voltage compared to dynamic power scaling, but not resolved. Looks like there are situations where there are just too many lighting/particle effects for a reasonable-to-good setup.
Maybe we should all go buy $10k gpus.
My issue with artifacting had nothing to do with overload; itās consistent with certain monster types (A2 and A4, especially). I can run a Necro with a full hoard (20+ summons) against a P8 army of Shenk and his minions with no issues. But show me a Maggot and half the screen disappears.
By the way, I failed to mention that I started experiencing these black squares in the throne room with my new machine, which operates on rtx 3080 ti. I didnāt have crashes like that on gtx 1070ā¦ Diablo is the only game that crashes like that, unfortunately.
1 Like
Same with me. I keep hoping that Blizzard/Nvidia will fix this before the 470 driver gets sunsetted.
1 Like
After switching back to a dual-boot with Windows 10, I tried the latest Nvidia drivers with D2Rā¦and all of my graphics issues are gone. I was even able to bump up the settings that Iād lowered on my Linux/Steam install.
I have the same problem and I use windows 10, will blizzard seriously leave the game like this?
1 Like
Same here! Has anyone had any success in getting rid of this?
I was able to resolve this by enabling DLSS option in the game menu for my Nvidia GPU. I upgraded proton to Proton GE 9-5, and I also switched from open dkms to proprietary dkms.
Enable DLSS looks like a working solution.
Iām having this exact problem as well. At first I thought it was because I was running Linux, but I see that people have been having this issue for many years on both Windows 10 and Windows 11, and all different nvidia driver versions.
Iām running CachyOS (arch linux btw), and nvidia driver version 560
Have the devs actually even looked at this problem? I feel like forum moderators are just telling people to update their drivers over and overā¦
Iāve started debugging the shaders. For maggots in the river of flame there is a NaN situation: y = log2(clamp(x, 0, 1)) will be -Infinity for x <= 0 and then y * 0 becomes NaN later on. On Linux with Lutris I can override the shaders, not sure how you would do that on Windows. Not even sure it is the same issue on Windows, but sure sounds like it.
EDIT: In my override I changed to log2(clamp(x, 0.00001, 1)) and the boxes are gone. This is in the main drawing pass before compositing. Iāll think about how I can make this available.
1 Like
How can you override it via lutris? There are some easy way or it is so advanced it will be impossible to explain here? hahaha
This issue is bugging me foreverā¦
This problem doesnāt seem OS-dependent. Might be more about the driver. Iām running under WINE/VKD3D in Linux, NVIDIA 565 driver, GTX 1050 4GB on Core i5-4590, at 1080p. Seems itās still not fixed, over three years later.
Blizzard and/or NVIDIA, and I donāt care who, figure out what the problem is AND FIX IT already!!! This is ridiculous! It mars the experience of an otherwise gorgeous game! If I wanted to switch to legacy mode I would just play the original release!
Edit: I just read MIJās post about it, and I guess I could do his shader override hack, assuming I can figure out how. I am using Lutris, so thereās that. But it would be nice if yāall at Blizzard cared about fixing issues instead of the USERS trying to come up with fixes for yāallās bugs!!! I also have this on my wifeās Windows 11 machine but I wouldnāt know how to effect the fix on that! She has a GT 1030 so maybe it wouldnāt even be an issue with such a low-end card.
Yet another edit: It seems that turning off (FXAA?) anti-aliasing seems to help. A lotā¦ as in, āso far so goodā (and of course you have to restart for it to take effect, but the problematic monsters didnāt spawn when I tried this, so itās not necessarily a definitive answer). This is a simple trick, but it seems silly to have to do, since any video card worth its salt can handle FXAA without much frame rate hit, but I guess Iām willing to make the trade-off of it not being jaggy-free in order to avoid the ugly, distracting and possibly epilepsy-inducing black boxes, which are arguably worse. I donāt know if MSAA or upscaling would help with the visual quality while avoiding the black boxes, but right now Iām running with AA off at 1080p, 100%, and it seems to be working well. Will update when I have had a chance to test things more.
wonāt work for people who donāt have Ampere or later. Pascal here.