protonscr

Unravel: graphical erros

dxvkclosed bugneeds apitrace
doitsujin/dxvk#415 · opened 2018-06-03 by DanMan · updated 2018-06-05 · 7 comments · github
DDanMan 2018-06-03 github

Severe graphical errors in Unravel via EA Origin. It crashes without DXVK, so no trace file. If I run it at a higher resolution than 480p, it shifts the display off the screen, showing only part of the game. You can only see the options on the right because bringing them up dims the whole game down (normal). Otherwise it'd be an all white screen. Sound (and keyboard input) works though.

unravel

System information

  • Ubuntu 16.04 w/ Kernel 4.13.0-43 (HWE)
  • GPU: NV 970GTX
  • Driver: 384.130
  • Wine version: 3.9-staging
  • DXVK version: 0.53 (via Lutris v0.4.18)

Log files

  • d3d11.log:
info:  D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
info:  D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0
info:  D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_0
warn:  D3D11RasterizerState: Depth clamp not properly supported`
  • dxgi.log:
info:  Enabled instance extensions:
info:    VK_KHR_win32_surface
info:    VK_KHR_surface
info:  GeForce GTX 970:
info:    Driver: 384.130.0
info:    Vulkan: 1.0.49
info:    Memory Heap[0]: 
info:      Size: 4096 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5980 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[9]: Property Flags = 0x6
info:      Memory Type[10]: Property Flags = 0xe
info:  Enabled instance extensions:
info:    VK_KHR_win32_surface
info:    VK_KHR_surface
info:  GeForce GTX 970:
info:    Driver: 384.130.0
info:    Vulkan: 1.0.49
info:    Memory Heap[0]: 
info:      Size: 4096 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5980 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[9]: Property Flags = 0x6
info:      Memory Type[10]: Property Flags = 0xe
warn:  Vulkan extension VK_EXT_vertex_attribute_divisor not supported
warn:  Vulkan extension VK_KHR_maintenance2 not supported
info:  Enabled device extensions:
info:    VK_KHR_swapchain
info:    VK_KHR_shader_draw_parameters
info:    VK_KHR_descriptor_update_template
info:    VK_KHR_maintenance1
info:    VK_KHR_sampler_mirror_clamp_to_edge
info:  Enabled instance extensions:
info:    VK_KHR_win32_surface
info:    VK_KHR_surface
info:  GeForce GTX 970:
info:    Driver: 384.130.0
info:    Vulkan: 1.0.49
info:    Memory Heap[0]: 
info:      Size: 4096 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5980 MiB
info:      Flags: 0x0
info:      Memory Type[0]: Property Flags = 0x0
info:      Memory Type[1]: Property Flags = 0x0
info:      Memory Type[2]: Property Flags = 0x0
info:      Memory Type[3]: Property Flags = 0x0
info:      Memory Type[4]: Property Flags = 0x0
info:      Memory Type[5]: Property Flags = 0x0
info:      Memory Type[6]: Property Flags = 0x0
info:      Memory Type[9]: Property Flags = 0x6
info:      Memory Type[10]: Property Flags = 0xe
warn:  Vulkan extension VK_EXT_vertex_attribute_divisor not supported
warn:  Vulkan extension VK_KHR_maintenance2 not supported
info:  Enabled device extensions:
info:    VK_KHR_swapchain
info:    VK_KHR_shader_draw_parameters
info:    VK_KHR_descriptor_update_template
info:    VK_KHR_maintenance1
info:    VK_KHR_sampler_mirror_clamp_to_edge
warn:  DXGI: MakeWindowAssociation: Ignoring flags
info:  DxgiVkPresenter: Recreating swap chain: 
  Format:       VK_FORMAT_B8G8R8A8_UNORM
  Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
  Buffer size:  640x480
Eexolyte 2018-06-03 github

You should use the 396.24.02 drivers, everything older than that is known to have a lot of issues with dxvk. Version 396.24 may work as well, but it has issues with tessellation.

Ddoitsujin maintainer 2018-06-03 github

If apitrace doesn't work with wined3d, please create one on Windows if possible, and if even that doesn't work, make one with DXVK although it might not useful. I can't do anything without a trace file.

DDanMan 2018-06-03 github

Tracing doesn't seem to work on Windows 7 either since I always get: dxgitrace.dll was never used: application probably does not use this API but it certainly is a DX11 game according to its sys. req. I did copy the .dll into the game's folder, too, but maybe the command was wrong.

I'll try again on Linux w/o DXVK.

44ymen 2018-06-04 github

Here is the trace file. As far as I'm concerned, with the GTX 970 and 397.93 driver (on Windows 10) which contains the new Vulkan compiler from Nvidia. I do not have graphical issues with DXVK.

Ppingubot 2018-06-04 github

Looks nice and error free here on my gtx 970 on linux with driver 396.24.02 .

DDanMan 2018-06-05 github

Thanks for testing, people. Guess I should update my driver then. Sorry. :/

Ddoitsujin maintainer 2018-06-05 github

The apitrace replays fine on my end as well, so yeah, this should be fixed by updating to 396.24.02.

DLLs