Topic: White Box / Missing FX bug

Home › Forums › The Abbey – Help & Support › White Box / Missing FX bug

These forums are closing and migrating to a new location! Please go to forums.darkestdungeon.com and create your account. Feel free to bring your posts over to this new forum.

Tagged: 

This topic contains 3 replies, has 3 voices, and was last updated by  gr00vus 2 years, 1 month ago.

  • Author
    Posts
  • June 20, 2017 at 4:13 pm #262803

    AmazingPotato
    Participant

    Hello!

    On some missions, graphic assets are replaced with a white box – sometimes it’s things like chests or the torch flame, other times it’s the background effect whenever a hero goes nuts or opens something. It doesn’t seem to affect one particular area either, as it’s happened in the Ruins, the Cove, all over.

    I thought I’d post here (got the game from GOG) although a Google search suggests maybe it’s a graphic card problem…? (mine’s updated) These are my specs –>

    Windows 7 Professional 64-bit service pack 1
    Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz (4 CPUs)
    Memory: 4096MB RAM
    Available OS Memory: 3672MB RAM
    DirectX 11
    Intel(R) HD Graphics 4000

    edit: it’s a Lenovo Thinkpad L430

    (I have zero other issues with running the game, which is brilliant, incidentally 😀 )

    June 23, 2017 at 4:35 pm #263089

    jjnether
    Participant

    I believe I’m having a similar problem. Other than a bit of lag, the rest of the game works wonderfully. However, during just the first mission in the courtyard, any special effects like when activating a curio quickly fills the screen with a white box. The white box quickly shrinks into nothing, then the game proceeds as normal. Below is my system info:

    Dell Vostro 3350
    Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.170512-0600)
    Memory: 8192MB RAM
    Display Card name: Intel(R) HD Graphics 3000
    Processor: Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (4 CPUs)
    DirectX Version: DirectX 11

    October 18, 2017 at 10:39 pm #326423

    gr00vus
    Participant

    I’m having the same problem. I’ve had the game for a year without this issue, but it has started occurring over the last few days. It seems to have started after I applied the latest Nvidia driver – version 387.92 released on October 8, 2017. Below are relevant system specs.

    Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.170913-0600)
    System Manufacturer: Gigabyte Technology Co., Ltd.
    System Model: GA-870A-UD3
    BIOS: Award Modular BIOS v6.00PG
    Processor: AMD Phenom(tm) II X4 965 Processor (4 CPUs), ~3.4GHz
    Memory: 16384MB RAM
    Available OS Memory: 16382MB RAM
    Page File: 4736MB used, 28024MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode
    —————
    Display Devices
    —————
    Card name: NVIDIA GeForce GTX 460
    Manufacturer: NVIDIA
    Chip type: GeForce GTX 460
    DAC type: Integrated RAMDAC
    Device Key: Enum\PCI\VEN_10DE&DEV_0E22&SUBSYS_34FC1458&REV_A1
    Display Memory: 4051 MB
    Dedicated Memory: 979 MB
    Shared Memory: 3071 MB
    Current Mode: 1920 x 1200 (32 bit) (59Hz)
    Monitor Name: SyncMaster 245T(Digital)
    Monitor Model: SyncMaster
    Monitor Id: SAM02F5
    Native Mode: 1920 x 1200(p) (59.950Hz)
    Output Type: DVI
    Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver File Version: 23.21.0013.8792 (English)
    Driver Version: 23.21.13.8792
    DDI Version: 11
    Driver Model: WDDM 1.1
    Driver Attributes: Final Retail
    Driver Date/Size: 10/6/2017 06:32:47, 18203456 bytes

    Any help would be appreciated as the game is now unplayable as is.

    October 22, 2017 at 1:38 pm #326474

    gr00vus
    Participant

    I rolled my Nvidia graphics driver back to version 385.41 from August and I no longer have this problem.

    Looks like the most recent two Nvidia driver releases for my cards are busted.

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)

The forum ‘The Abbey – Help & Support’ is closed to new topics and replies.