Wine, D9VK, and Lutris Help Request

enorbet · 09-27-2019, 01:38 AM

I'm currently using Wine-Staging 4.16 and I very much want to incorporate d9vk in it. It seems there are two (2) ways to accomplish this and I have been unsuccessful with both.

1) Winetricks - dll install - now includes d9vk-master and several versions. I can't even get the zip file to download and unzip, despite an auto download of wine's own 7Zip. Originally it tried to do this in "Y:/" which as far as I can tell under ~/.wine/devices, doesn't exist. I even tried creating a symlink to an NTFS drive and winetricks still won't have it.

2) d9vk direct (github) - I installed meson and MInGW but can't find a slackbuild for glslang and it is a tad confusing how it is to be built from source.

Lutris is only currently important to me to verify that Wine or Steam are using d9vk so it's of secondary concern but I've installed all the dependencies listed at Slackbuilds.org but Lutris build fails.

So how is anyone getting these installed or is it that I'm using 14.2 with Pulseaudio removed? I don't see any error messages mentioning pulse, but I have nothing else to blame, and of course this has nothing to do with the more important glslang problem AFAIK.

mickski56 · 09-27-2019, 03:06 AM

Not sure what's going on with winetricks as I've never tried to install d9vk that way.

You could just download a binary release from https://github.com/Joshua-Ashton/d9vk/releases, unpack it somewhere and run "setup_dxvk.sh --help" to see what options to use. Compiling d9vk/dxvk requires a working mingw setup both 32 and 64 bit if you want 32 and 64 bit d9vk/dxvk.

Lutris don't know never tried it, but if you have a working d9vk/dxvk setup you will see logs of the form *_d3d9.log / *_d3d11.log in the game directory you are running the game from.

hth

dugan · 09-27-2019, 08:59 AM

I just download the binary tarball from the GitHub page and run the installer. I don't compile it.

garpu · 09-27-2019, 11:32 AM

Quote:

Originally Posted by dugan

I just download the binary tarball from the GitHub page and run the installer. I don't compile it.

Same here. You export the WINEPREFIX you want, and it puts it in the correct one, regardless of how the drives are mapped to WINE. (I think my home WINE thinks is "z:".) I don't bother with Lutris, either.

The one you want is the d9vk-some.number.tar.gz. Unzip it somewhere. On console, "export WINEPREFIX=/where/your/wineprefix/is" then in the d9vk directory, "setup_dxvk.sh install" It'll set up the necessary overrides, as well.

enorbet · 09-27-2019, 03:01 PM

Thanks all. I am making some progress at least. I think I was mistakenly using "d9vk-master.zip" instead of "d9vk-0.21.tgz" as that latter setup script actually works and completes.

Now the only problem I have is how to get rid of d3dcompiler et al since simply unchecking the boxes in "winetricks > install DLL or Component" apparently only installs and won't uninstall. Is it possible to selectively uninstall those now unwanted components or must I wipe a directory or even a whole install and start fresh?

garpu · 09-27-2019, 03:04 PM

Quote:

Originally Posted by enorbet

Thanks all. I am making some progress at least. I think I was mistakenly using "d9vk-master.zip" instead of "d9vk-0.21.tgz" as that latter setup script actually works and completes.

Now the only problem I have is how to get rid of d3dcompiler et al since simply unchecking the boxes in "winetricks > install DLL or Component" apparently only installs and won't uninstall. Is it possible to selectively uninstall those now unwanted components or must I wipe a directory or even a whole install and start fresh?

The setup script should handle that for you. I've never had to do it manually.

dugan · 09-27-2019, 03:05 PM

Just start a new prefix.

Code:

# When $HOME/.local/share/wineprefixes/mygame does NOT exist
export WINEPREFIX=$HOME/.local/share/wineprefixesmygame
winecfg # this creates a new prefix
# install dxvk with its installer
# install d9vk with its installer
# install Media Foundation stuff from z0z0z/mf-install if needed
# Install the game

This is all I do these days.

You can then set DXVK_HUD=1 to test if the D9VK passthrough to DXVK is working.

I'm planning to set up just such a prefix to run GOG Galaxy soon. GOG's offline installers aren't always up to date

enorbet · 09-27-2019, 03:34 PM

Quote:

Originally Posted by garpu

The setup script should handle that for you. I've never had to do it manually.

It doesn't. Not only does winetricks still show the boxes checked but "~/.wine/c_drive/windows/system32" still has all the dlls and components. I just searched for d3d and deleted everything with "9" in it, leaving "10" and "11" for now and the checkboxes are now empty. I then re-ran the d9vk setup script and once again it completed. I'm about to test it out.

Quote:

Originally Posted by dugan

Just start a new prefix.

Code:

# When $HOME/.local/share/wineprefixes/mygame does NOT exist
export WINEPREFIX=$HOME/.local/share/wineprefixesmygame
winecfg # this creates a new prefix
# install d9vk with its installer
# install dxvk with its installer
# install Media Foundation stuff from z0z0z/mf-install if needed
# Install the game

This is all I do these days.

I'm planning to set up just such a prefix to run GOG Galaxy soon. GOG's offline installers aren't always up to date

I have no "wineprefixes" folders anywhere anymore since I stopped using PlayonLinux and renamed "~/wine" to "~/.wine-old"

Is it, under such circumstances (only one version installed), incorrect to do "export WINEPREFIX=$HOME/.wine" ?

I use your "wine.Slackbuild" script, dugan, and have for a over a year now having grown fond of and accustomed to how it handles staging and other patches. It just wroks really great. That installs all the Media Foundation stuff too, right?

Lastly, regarding game code, my main interest, since all my other games run in Steam decently, is World of Warcraft 3.3.5a Wrath of the Lich King and it's config.wtf filre up until my trials with d9vk has this line

Code:

 SET gxApi "OpenGL"

If I change that to

Code:

 SET gxApi "D9VK"

the game, once launched, alters that line to

Code:

 SET gxApi "D3D9"

This is why I was wondering about Lutris. I've watched some tutorial vids in which Lutris was used to add the availability of the "D9VK" entry, but since I have yet to get it to work properly I don't know if that is optional or required in some games.

BTW Thanks again for your scripts and all your help here.

NOTE - FWIW I launch WOW with

Code:

  WINEDEBUG=-all __GL_THREADED_OPTIMIZATIONS=1 wine /mnt/HUGE_X/WinWOW/wow.exe renice -20

and hope the nvidia optimization line doesn't conflict with not using OpenGL

enorbet · 09-27-2019, 03:55 PM

Sorry this is so long but it appears that d9vk is activated despite the "D3D9" entry in Config.wtf ....

Code:

 archive Data\enUS\lichking-speech-enUS.MPQ opened
info:  Game: wow.exe
info:  DXVK: d9vk-0.21-lollihop
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
warn:  D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info:  GeForce GTX 1070 Ti:
info:    Driver: 430.50.0
info:    Vulkan: 1.1.99
info:    Memory Heap[0]: 
info:      Size: 8192 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5882 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:  Process set as DPI aware
info:  Game: wow.exe
info:  DXVK: d9vk-0.21-lollihop
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
warn:  D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info:  GeForce GTX 1070 Ti:
info:    Driver: 430.50.0
info:    Vulkan: 1.1.99
info:    Memory Heap[0]: 
info:      Size: 8192 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5882 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:  Process set as DPI aware
info:  Game: wow.exe
info:  DXVK: d9vk-0.21-lollihop
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
warn:  D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info:  GeForce GTX 1070 Ti:
info:    Driver: 430.50.0
info:    Vulkan: 1.1.99
info:    Memory Heap[0]: 
info:      Size: 8192 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5882 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:  Process set as DPI aware
info:  Device properties:
info:    Device name:     : GeForce GTX 1070 Ti
info:    Driver version   : 430.50.0
info:  Enabled device extensions:
info:    VK_EXT_conditional_rendering
info:    VK_EXT_depth_clip_enable
info:    VK_EXT_host_query_reset
info:    VK_EXT_shader_viewport_index_layer
info:    VK_EXT_transform_feedback
info:    VK_EXT_vertex_attribute_divisor
info:    VK_KHR_create_renderpass2
info:    VK_KHR_dedicated_allocation
info:    VK_KHR_depth_stencil_resolve
info:    VK_KHR_descriptor_update_template
info:    VK_KHR_draw_indirect_count
info:    VK_KHR_driver_properties
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:  Device features:
info:    robustBufferAccess                     : 1
info:    fullDrawIndexUint32                    : 1
info:    imageCubeArray                         : 1
info:    independentBlend                       : 1
info:    geometryShader                         : 1
info:    tessellationShader                     : 0
info:    sampleRateShading                      : 1
info:    dualSrcBlend                           : 0
info:    logicOp                                : 0
info:    multiDrawIndirect                      : 0
info:    drawIndirectFirstInstance              : 0
info:    depthClamp                             : 1
info:    depthBiasClamp                         : 1
info:    fillModeNonSolid                       : 1
info:    depthBounds                            : 0
info:    multiViewport                          : 1
info:    samplerAnisotropy                      : 1
info:    textureCompressionBC                   : 1
info:    occlusionQueryPrecise                  : 1
info:    pipelineStatisticsQuery                : 1
info:    vertexPipelineStoresAndAtomics         : 1
info:    fragmentStoresAndAtomics               : 0
info:    shaderImageGatherExtended              : 0
info:    shaderStorageImageExtendedFormats      : 1
info:    shaderStorageImageReadWithoutFormat    : 0
info:    shaderStorageImageWriteWithoutFormat   : 1
info:    shaderClipDistance                     : 1
info:    shaderCullDistance                     : 1
info:    shaderFloat64                          : 0
info:    shaderInt64                            : 0
info:    variableMultisampleRate                : 0
info:  VK_EXT_conditional_rendering
info:    conditionalRendering                   : 0
info:  VK_EXT_depth_clip_enable
info:    depthClipEnable                        : 1
info:  VK_EXT_host_query_reset
info:    hostQueryReset                         : 1
info:  VK_EXT_memory_priority
info:    memoryPriority                         : 0
info:  VK_EXT_shader_demote_to_helper_invocation
info:    shaderDemoteToHelperInvocation         : 0
info:  VK_EXT_transform_feedback
info:    transformFeedback                      : 0
info:    geometryStreams                        : 0
info:  VK_EXT_vertex_attribute_divisor
info:    vertexAttributeInstanceRateDivisor     : 1
info:    vertexAttributeInstanceRateZeroDivisor : 1
info:  Queue families:
info:    Graphics : 0
info:    Transfer : 1
info:  DXVK: Read 450 valid state cache entries
info:  DXVK: Using 2 compiler threads
info:  D3D9DeviceEx::ResetEx:
info:    Requested Presentation Parameters
info:      - Width:              1856
info:      - Height:             1044
info:      - Format:             D3D9Format::X8R8G8B8
info:      - Auto Depth Stencil: true
info:                  ^ Format: D3D9Format::D24X8
info:      - Windowed:           true
info:  Presenter: Actual swap chain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_UNORM
info:    Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
info:    Buffer size:  1856x1044
info:    Image count:  2
warn:  D3D9DeviceEx::SetRenderState: Unhandled render state D3DRS_POINTSIZE_MAX
warn:  D3D9DeviceEx::SetRenderState: Unhandled render state D3DRS_POINTSIZE_MIN
info:  Game: wow.exe
info:  DXVK: d9vk-0.21-lollihop
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
warn:  D3D9: VK_FORMAT_D16_UNORM_S8_UINT -> VK_FORMAT_D24_UNORM_S8_UINT
info:  GeForce GTX 1070 Ti:
info:    Driver: 430.50.0
info:    Vulkan: 1.1.99
info:    Memory Heap[0]: 
info:      Size: 8192 MiB
info:      Flags: 0x1
info:      Memory Type[7]: Property Flags = 0x1
info:      Memory Type[8]: Property Flags = 0x1
info:    Memory Heap[1]: 
info:      Size: 5882 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:  Process set as DPI aware
info:  Presenter: Actual swap chain properties:
info:    Format:       VK_FORMAT_B8G8R8A8_UNORM
info:    Present mode: VK_PRESENT_MODE_FIFO_KHR
info:    Buffer size:  1856x1044
info:    Image count:  3
warn:  D3D9DeviceEx::SetRenderState: Unhandled render state D3DRS_MULTISAMPLEANTIALIAS

but I am posting it all because something must still be very wrong since FPS is substantially lower than with OpenGL. Man! This is driving me nuts. I used to get better performance a few years ago with a much older version of wine that wasn't even -staging but it changed so slowly and incrementally that I have no clue as to whether it would run better on some older version but this is maddening. I have FPS capped at "60FPS" which is a trick I learned from old Quake 3 days in using a card capable of vastly higher FPS and capping it sdtill quite high but MUCH lower than max which makes for stability and fantastically smooth response. With OpenGL I sometimes drop to 35 FPS and with what is rightly or wrongly "D3D9" I drop to 20-25 sometimes. Grrrrr !!!

garpu · 09-27-2019, 04:42 PM

Don't use the winetricks installer for d9vk. d9vk (and dxvk) comes with its own setup installer script that will add the overrides for you. Make a completely new wineprefix like dugan suggested.

Are you trying to run WoW classic or a private server? If it's the actual binary from years ago, that's going to run for crap. The dx9 engine never ran very well, in my experience, and if you're on a private server, you're better off sticking with OpenGL.

If you're playing Classic, classic needs dxvk: https://appdb.winehq.org/objectManag...sion&iId=38181

enorbet · 09-27-2019, 04:58 PM

Sorry I wasn't clearer, garpu. I stopped trying to use winetricks to install d9vk and successfully got the d9vk setup script to work. I only subsequently opened winetricks to look for the conflicting d3d9 dlls and compiler. I manually deleted those from wine's windows/system32.

No I'm not at all interested in WoW Classic. IMHO near perfection was achieved in TBC and completely achieved around 3.3.5 with Ulduar. That seems to be the last build where Blizz did it from a strong influence of a labor of love. Ruby Sanctum and ICC still have decent gameplay but far less effort went into variation and imaginative graphics. After that it has been continually dumbed down to attract younger players in my view. Apparently bean counters had their way. Cata was a giant step down and they just lost me with the freaking pandas, but it all seems done "on the cheap" after ICC.

That said, thank you for noting that I may never achieve decent results through d9vk. It does cause me wonder why it ran better before with substantially weaker hardware so maybe I just have to bite the bullet and try numerous wine versions till I find the magic. <sigh> I really wanted to avoid reinstalling PlayOnLinux but it is the easiest way to manage multiple wine installs.

Hmmm maybe I'll first try the game in actual Windows and note the differences.

Firerat · 09-28-2019, 06:50 AM

so are you wanting to run a Wrath Client?
Because that runs fine with OpenGL

regards winetricks, you can just toggle things
or., just use the Command line and edit the .reg files in ~/.wineprefix/
or, do what everyone else does and just delete old prefixes

back to WoW 3.3.5a

it has two Graphics APIs
OpenGL and Direct3D 9

D9VK translates D3D9 api calls to Vulcan
WineD3D translates D3D9 to OpenGL

OpenGL, well that is OpenGL

if you have been fighting WoW setting the API to D3D9 you really suffer from a lack of understanding.

Code:

export __GL_THREADED_OPTIMIZATIONS=1
export __GL_YIELD="USLEEP"
export __GL_SYNC_TO_VBLANK=0
export WINEPREFIX=/path/to/.wineWoW-prefix
wine /path/to/games/WoW/Wow.exe -opengl

orbea · 09-28-2019, 08:44 AM

In case anyone is interested I made a SlackBuild for the winelib version of D9VK.

https://notabug.org/orbea/SlackBuild.../graphics/d9vk

And also DXVK.

https://notabug.org/orbea/SlackBuild.../graphics/dxvk

These likely won't build on 14.2 because of the older compilers unless someone can make a SBo compatible mingw build to use.

Personally I would suggest wine-nine-standalone for D3D9 support if your GPU supports it (radeonsi, r600, nouveau and iris), but D9VK seems to work here.

http://slackbuilds.org/repository/14...ne-standalone/

Firerat · 09-28-2019, 09:03 AM

Quote:

Originally Posted by orbea

Personally I would suggest wine-nine-standalone for D3D9 support if your GPU supports it (radeonsi, r600, nouveau and iris), but D9VK seems to work here.

http://slackbuilds.org/repository/14...ne-standalone/

I think it was deemed to have failed as the OP doesn't have a grasp of what is going on with the basics.

They were getting frustrated that wow 3.3.5a was resetting the gxAPI back to D3D9 from D9VK that they were manually adding.

I have no idea why they thought WoW was going to understand a translation API which was written long after It was.

no grasp of basics.

orbea · 09-28-2019, 09:11 AM

If I recall enorbet uses the nvidia proprietary drivers and doesn't have the ability of using wine-nine-standalone, but other people who read this thread might find it useful. My basic impression is that D9VK hasn't had nearly as much time to mature as wine-nine-standalone or DXVK, in the future it likely will become more viable. Also eventually D9VK might be merged into DXVK.