A Shader visual bug. (Probably only on my side)

MaeinesenieaM

New member
What happens when you try to test Deadlock on a low-low-end graphics card?
This.
Deadlock-shader-notgood.png
more specifically, a GeForce GTX 550 TI stuck on an outdated NVIDIA driver due to loss in support. I don't know if is possible to fix this bug since it's probably only on my end for having such an outdated GPU, this bad boy can't even run Directx12 or Vulkan API's. but alas here is my bug report.
specs:
CPU: Intel® Core™ i5-2500K Processor;
OS: Windows 10;
GPU: GeForce GTX 550 TI (with a 391.35 driver);
VRAM: 1GB;
RAM: DDR3 10GB (don't question my methods);
MotherBoard: Asus P8B75-V;
 

Attachments

  • Deadlock-shader-ohheythiscarworks.png
    Deadlock-shader-ohheythiscarworks.png
    1.4 MB · Views: 4
  • Deadlock-shader-takeonme.png
    Deadlock-shader-takeonme.png
    1.7 MB · Views: 1
  • Deadlock-shader-atleasttheshopworks.png
    Deadlock-shader-atleasttheshopworks.png
    556.4 KB · Views: 3
But hey! Look at the bright side, I can somehow still play the game smoothly with a constant framerate. But that would require an immense amount of skill to pull off... right?
 
20240911193811_1.jpg
Well you're not the only one, :) NVidia gtx560, I ran the updates from nvidia and it didn't change anything.

Device name
Processor Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz 3.30 GHz
Installed RAM 8.00 GB (DDR3)
System type 64-bit operating system, x64-based processor
 
I have the same problem :(

Here is detailed information of my laptop:
CPU Vendor: Genuine Intel
CPU Brand: Intel(R) Core(TM) i7-4700HQ CPU @ 2.40GHz

Windows 10 (64 bit)

Driver: NVIDIA GeForce GTX 880M
DirectX Driver Name: nvldumd.dll
Driver Version: 25.21.14.2531
DirectX Driver Version: 25.21.14.2531
Driver Date: 4 9 2019
Desktop Color Depth: 32 bits per pixel
Monitor Refresh Rate: 60 Hz
DirectX Card: NVIDIA GeForce GTX 880M
Primary VRAM: 4095 MB

RAM: 16266 Mb

1422450_2.jpg
 
Back
Top