[Official] WINE info thread

Hello!

I've been using the following settings in Lutris: (after using the wine/DXVK standalone PoE Lutris script: lutris:path-of-exile-standalone-w-dxvk and changing some settings.)





Playing at max settings, only during lots of effects/spells the FPS dips, have not had any crashes in a long time.

The latest Proton Beta should be as good.

"

acylus wrote:

Anyone played with the new DXVK 0.80? Does it still need the poe dxvk hack?

Edit: Yep, still need the hack. Does anyone have a compiled copy of 0.80 with the patch?

I couldn't manage to patch dxvk even with

"

git apply --ignore-space-change --ignore-whitespace ../dxvk-poe-hack/pi peline.patch
git apply --reject --whitespace=fix ../dxvk-poe-hack/pipeline.patch

tried on multiple versions of dxvk.

seconding the request or maybe could someone try to contact the patch maintainer?

Yeah, the patch stopped applying correctly shortly after its most recent update. DXVK is just updated so frequently and the patch affects some of its main .cpp files. Just gotta keep jomihaka notified about it on github by submitting an issue I suppose.

"

Epi77444 wrote:

"

acylus wrote:

Anyone played with the new DXVK 0.80? Does it still need the poe dxvk hack?

Edit: Yep, still need the hack. Does anyone have a compiled copy of 0.80 with the patch?

I couldn't manage to patch dxvk even with

"

git apply --ignore-space-change --ignore-whitespace ../dxvk-poe-hack/pi peline.patch
git apply --reject --whitespace=fix ../dxvk-poe-hack/pipeline.patch

tried on multiple versions of dxvk.

seconding the request or maybe could someone try to contact the patch maintainer?

"if it works, don't update". DXVK 0.80 changed the way shaders are handled overall to minimize stuttering. The hack makes treats shaders in an asynchronous way which brought a lot of headaches for DXVK (something near dxvk 0.72 if I'm not mistaken). So on 0.80 ("big release number"), DXVK changed the way things are handled to minimize stutters overall and not use "this cheap hack".

Apparently 0.80 introduces less stuttering overall, but nothing will be as good as simply skipping some steps as the hack does.

You can probably read more about these changes on their github and stuff.

I'm going crazy trying to get this game working with dxvk. I've got it installed through lutris following the most recent install guide on here. When I start the game, it plays the gears video (with the dxvk hud showing so I think that means it should be working) but then I get a black screen with music playing. I'm not finding any useful information in the logs though so I have no idea what is stopping it. In the log, everything looks ok in the beginning, then I get a bunch of fixmes about fonts, then this:
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
At that point I need to go to a terminal to kill the process or it will sit there forever and every minute will show this:
0099:err:ntdll:RtlpWaitForCriticalSection section 0x1418e39c8 "?" wait timed out in thread 0099, blocked by 0098, retrying (60 sec)

d3d11.log only has this in it:
info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_1
info: D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_1
info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_1
info: D3D11CoreCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_1
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST
err: DxvkDevice: Command buffer submission failed: VK_ERROR_DEVICE_LOST

and dxgi.log has this:
info: Game: PathOfExile_x64.exe
info: DXVK: v0.81
warn: OpenVR: Failed to locate module
info: Enabled instance extensions:
info: VK_KHR_get_physical_device_properties2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: GeForce GTX 1080 Ti:
info: Driver: 396.54.0
info: Vulkan: 1.1.70
info: Memory Heap[0]:
info: Size: 11264 MiB
info: Flags: 0x1
info: Memory Type[7]: Property Flags = 0x1
info: Memory Type[8]: Property Flags = 0x1
info: Memory Heap[1]:
info: Size: 5990 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: Game: PathOfExile_x64.exe
info: DXVK: v0.81
warn: OpenVR: Failed to locate module
info: Enabled instance extensions:
info: VK_KHR_get_physical_device_properties2
info: VK_KHR_surface
info: VK_KHR_win32_surface
info: GeForce GTX 1080 Ti:
info: Driver: 396.54.0
info: Vulkan: 1.1.70
info: Memory Heap[0]:
info: Size: 11264 MiB
info: Flags: 0x1
info: Memory Type[7]: Property Flags = 0x1
info: Memory Type[8]: Property Flags = 0x1
info: Memory Heap[1]:
info: Size: 5990 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 device extensions:
info: VK_EXT_shader_viewport_index_layer
info: VK_EXT_vertex_attribute_divisor
info: VK_KHR_dedicated_allocation
info: VK_KHR_descriptor_update_template
info: VK_KHR_get_memory_requirements2
info: VK_KHR_image_format_list
info: VK_KHR_maintenance1
info: VK_KHR_maintenance2
info: VK_KHR_sampler_mirror_clamp_to_edge
info: VK_KHR_shader_draw_parameters
info: VK_KHR_swapchain
warn: DXVK: No state cache file found
warn: DXVK: Creating new state cache file
info: DXVK: Using 12 compiler threads
info: Enabled device extensions:
info: VK_EXT_shader_viewport_index_layer
info: VK_EXT_vertex_attribute_divisor
info: VK_KHR_dedicated_allocation
info: VK_KHR_descriptor_update_template
info: VK_KHR_get_memory_requirements2
info: VK_KHR_image_format_list
info: VK_KHR_maintenance1
info: VK_KHR_maintenance2
info: VK_KHR_sampler_mirror_clamp_to_edge
info: VK_KHR_shader_draw_parameters
info: VK_KHR_swapchain
info: DXVK: Read 0 valid state cache entries
info: DXVK: Using 12 compiler threads
warn: DXGI: MakeWindowAssociation: Ignoring flags
info: DxgiVkPresenter: Recreating swap chain:
Format: VK_FORMAT_B8G8R8A8_SRGB
Present mode: VK_PRESENT_MODE_FIFO_KHR
Buffer size: 2560x1440
err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST
err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST

Any clues? I've reinstalled twice and also tried this via steam/proton with the same results.

Anyone have alt+tab crash problem?

System: Host: a Kernel: 4.18.12-arch1-1-ARCH x86_64 bits: 64 Desktop: KDE Plasma 5.14.0 Distro: Arch Linux
Machine: Type: Laptop System: Dell product: XPS 15 9560 v: N/A serial: <root required>
Mobo: Dell model: 0YH90J v: A04 serial: <root required> UEFI: Dell v: 1.9.4 date: 04/23/2018
CPU: Topology: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP L2 cache: 6144 KiB
Speed: 1000 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 1001 2: 1000 3: 1000 4: 1000 5: 988
6: 1000 7: 1000 8: 1000
Graphics: Device-1: Intel driver: i915 v: kernel
Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] driver: N/A
Display: x11 server: X.Org 1.20.1 driver: modesetting unloaded: vesa resolution: 3840x2160~60Hz
OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.2.2


wine : https://github.com/Tk-Glitch/PKGBUILDS/tree/master/wine-tkg-git with default configuration.
dxvk : 0.9 with poe hack patch
primusrun : https://github.com/felixdoerre/primus_vk

Games working perfectly although still lvl 2 :D. Not much of testing.

The problem is games crashing when alt+tab. So should manually kill client.

Thanks.

The async patch for DXVK got updated for 0.90. You’ll have to build it yourself though.

https://github.com/jomihaka/dxvk-poe-hack

First and foremost, can you play the game on DX9 mode? That will prove that you have 0 issues with Wine and other libraries.

If you can, your problem is probably related to Vulkan libraries. Make sure you have them installed in your machine. If you're on ubuntu, you can type "apt list *vulkan*" to see the names of everything that has vulkan in its name. Typically, people mention libraries like libvulkan1 and vulkan-icd-loader, if I'm not mistaken.

If you get other types of errors afterwards (WIC factory or Textured3d11 errors), that's probably Wine's fault.

If I disable DXVK in the runner settings, I can run the game in either dx9 or dx11. When I enable any version of DXVK it won't start. Is there a way to get more debugging information out of Lutris/DXVK? I'm running lutris -d to get info in the terminal window. Also, I can run Witcher 3 with DXVK so I'm not having a problem with DXVK in general.

"

LostJanitor wrote:

If I disable DXVK in the runner settings, I can run the game in either dx9 or dx11. When I enable any version of DXVK it won't start. Is there a way to get more debugging information out of Lutris/DXVK? I'm running lutris -d to get info in the terminal window. Also, I can run Witcher 3 with DXVK so I'm not having a problem with DXVK in general.

If you go to Lutris and Game menu, you can check "See last game's log" thing. There's also an option in the game settings to allow further logging, but I think you already have the necessary information.

If you look into DXVK issues (querying "DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST") it also happens with other people in other games and may be related to VSync.

My suggestions are:
- Test a few DXVK versions:
- - 0.61
- - 0.72
- - 0.80
- - 0.90 (<- if you can, having the latest drivers and Wine installed)

If all of those give the same error, try changing game settings going to the production_Config.ini file located in $WINEPREFIX/drive_c/users/YOURNAME/My Documents/My Games/Path of Exile

I suggest setting resolution to 1920x1080 (I had some trouble with different resolutions) or 800x600. Try making the game run on Windowed mode. Make all graphical settings minimal. Since you're able to run the game, you can even change these without dxvk and then launch it back.

I think you already resorted to this, but try updating your drivers to the latest beta version (contains some DXVK compatibility stuff)

If all of these fail, it may be recommended to go into the DXVK GitHub page and open an issue. It seems like valuable information for the project.