dxvk: New World - Failed to create buffer view and crashing

So ever since the New World Call of the Wilds DLC update i’ve been having some nasty consistent crashes at around the 1 hour mark. The most noticeable crash is the game picture stops updating and then i get disconnected from the game, however the game does not crash even after waiting 10min. I’ve tried to look at the Proton Logs but i cant find anything among the millions of lines… I did however grep for err:, warn: and info: lines and found these DXVK errors at the bottom of the log It always starts with

D3D11: Cannot create texture

Then these

DxvkBufferView: Failed to create buffer view

Today i got a different error message but in the same ball park

DxvkImageView: Failed to create image view

So i wonder, is this a error message for the DXVK devs or the game devs that a texture is broken?

This is what i’ve tried:

  • I’ve tested both x11 and Wayland
  • I’ve tested both KDE and Gnome
  • I’ve tested Proton Experimental, GE-Proton 8-21, Proton 8.0-4 and Proton 7.0-6
  • I’ve tested DX11 and DX12
  • I’ve tested a bunch of launch options
  • I’ve reset the ShaderCache in steamapps/shadercache/1063730/DXVK_state_cache/
  • I’ve checked that i’m not running out of VRAM
  • I’ve deleted SteamLibrary/steamapps/compatdata/1063730/pfx/drive_c/users/steamuser/AppData/*/AGS as someone suggested for crashes
  • I’ve “Deleted all data and applications inside this wineprefix” via ProtonTricks
  • I’ve installed d3dcompiler_43 via ProtonTricks
  • I’ve installed d3dcompiler_47 via ProtonTricks (Fixes fixme:d3dcompiler:skip_u32_unknown in the logs)
  • I’ve installed dxvk via ProtonTricks
  • I’ve reinstalled New World from scratch
  • I’ve removed Mangohud and Gamemode from launch options
  • PROTON_USE_WINED3D=1 makes it “The computer fails to meet one or more of the minimum specifications in order to run” because its 1280 MB VRAM by default. Workaround to set VideoMemorySize to 11GB in Registry, however the rendering is messed up and not worth it.
  • I’ve tested vkd3d-proton via Protontricks
  • I’ve tested nvidia-open
  • I’ve tested PROTON_HIDE_NVIDIA_GPU=1
  • I’ve tested ENABLE_PROTON_NVAPI=1

The ONE thing that DID work is to play differently in one old area, the log file was calm and i did not crash for 2.5 hours. Which probably indicates a issue with a texture?

Software information

New World on any settings.

System information

Click for System information
  • Operating System: Arch Linux
  • KDE Plasma Version: 5.27.9
  • KDE Frameworks Version: 5.111.0
  • Qt Version: 5.15.11
  • Kernel Version: 6.5.8-arch1-1 (64-bit)
  • Graphics Platform: X11
  • Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
  • Memory: 31.3 GiB of RAM
  • Graphics Processor: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2
  • Manufacturer: ASUS
  • GPU: Nvidia 3080 ti
  • Driver: Proprietary and Open-Source kernel 535.113.01
  • Wine version: Proton 7.0-6, 8.0-4 and GE-Proton 8-20
  • DXVK version: No clue

Apitrace file(s)

  • Put a link here

For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace

Log files

The logs are TOO DAMN BIG (50mill lines and 5GB in 1 hour. Most of the log is flodded with these

9644.436:0134:0374:trace:unwind:dump_unwind_info     0xa: pushq %rdi

steam-1063730-err.log steam-1063730-info.log steam-1063730-err2.log

I currently have a 1.2GiB crash log file i can grep if anyone have something i can search for

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 18 (7 by maintainers)

Most upvoted comments

The raids are in the open world so yes, but i’ve not crashed while questing, so i think its specific to the raid area, i actually crashed twice in a very short time yesterday in Dreaded Landing/Tribunal without a raid party