WineHQ

World of Warcraft

World Of Warcraft Battle for Azeroth - With the Legion defeated, now is the time to try to heal the wound left by Sargeras, but the Horde and Alliance race to gather resources, and conquer the other side, before they can discover the true secret of the aftermath of the wound in Silithus.  Level cap to 120, 3 new races for each faction, new continents, battle grounds, and world PVP now. New pets, mounts and other achievements to be found. 

Application Details:

Version: 8.0
License: Retail
URL: http://www.worldofwarcraft.com
Votes: 0
Latest Rating: Platinum
Latest Wine Version Tested: 4.0-rc1-staging

Maintainers: About Maintainership

Test Results

Selected Test Results

What works

Testing DX12 with vkd3d wrapper, in wine 4.0 rc-1.  Battle.net app runs, able to install and run Twitch for addon updating, able to play all aspects of the game, including dungeons and raids.  Created a custom script to launch WoW, since the Battle.net app has issues launching the game.  It will update the game, which I have symlinked from my windows partition.  Wine is self compiled, as per the how to notes on this site.  Average of 50+ FPS in most areas, and patched swapchain.c to disable Vsync.  Script to download and patch Wine has the command to fix the file.  Not a workaround, as so much a bug fix, since mainline wow has vulkan frame locked at your monitor refresh rate.  

What does not

Workarounds

What was not tested

Nothing. Everything works.

Hardware tested

Graphics:

  • GPU: Nvidia
  • Driver: proprietary

Additional Comments

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentFedora 29 x86_64Dec 08 20184.0-rc1-stagingYes Yes NoPlatinumSteve Ebey 
ShowAntergos x86_64Nov 30 -00013.17-stagingYes Yes YesGoldkh 
ShowFedora 28 x86_64Sep 06 20183.15-stagingYes Yes YesGoldJosh R Raymond 
ShowArch Linux x86_64Aug 04 20183.13-stagingYes Yes YesSilverMartin Weinelt 
ShowantiX-17 "Heather Heyer" CoreJul 22 20183.13-stagingYes Yes NoPlatinumspaceman 

Known Bugs

Bug # Description Status Resolution Other apps affected
45349 Multiple applications and games crash due to missing support for 64-bit syscall thunks (StreetFighter V, World of Warcraft) STAGED View
46184 dx12 to vkd3d crashes wow, with a screen full of fixme RESOLVED FIXED View
46218 World of Warcraft A streaming error has occurred. (WOW51900322) - wine-staging NEW View

Show all bugs

HowTo / Notes

Fedora Compilation Instructions to build DX12 Vulkan wrapper and compile Wine to use DX12

I would recommend putting this in a directory of its own, such as wine-dirs or some other similar name, so that if needed, a simple rm -fr wine-dirs would eliminate everything, if you need to free up the space on your drive.  These steps work on my Fedora 28 distro. I use the latest gcc from the Fedora repositries, and I have installed all the dependencies that wine needs.  if you are running the fedora distro of wine, you can sudo dnf  builddep wine to download the dependencies, then do sudo dnf remove wine, so that when you compile, you do not cross versions and have to troubleshoot. copy and paste the text shown here, to a script file, and run it.  Go get some coffee, or watch tv, as dependent on your internet speed, the git repos may take time to download. 

clear
echo Cleanup and fresh download of repositories needed
rm -fr wine
rm -fr wine-staging
echo WineHQ Devel Source Git
git clone https://github.com/wine-mirror/wine.git
echo Unoffical Wine Staging Git
git clone https://github.com/wine-staging/wine-staging.git
cd wine-staging
echo Working in $(pwd)
./patches/patchinstall.sh DESTDIR="../wine" --all
cd ../wine
echo Working in $(pwd)
cd ~/wine-dirs
sed -i -e 's/MODE_FIFO/MODE_IMMEDIATE/' wine/dlls/dxgi/swapchain.c
cat wine/dlls/dxgi/swapchain.c | grep -i mode_IMMEDIATE
echo this is the end, if no errors were presented, then compile and enjoy

if you get problems with firewall, then most likely, you do not have gnu-tls installed. simply install that and rerun the script.


Build VKD3D Library

rm -fr vkd3d
git clone git://source.winehq.org/git/vkd3d.git
cd vkd3d
./autogen.sh
./configure --enable-demos --with-sysroot
make -j6
sudo make install
sudo ldconfig


Compiling for a WoW64 Shared Build per the Wine Wiki

These instructions assume all the build dependencies for 32 and 64 bit are properly installed.  If not, you must take the time to get them. Explaining that here would be beyond the scope of this example. Shown here is the compile script I use after running the download and patch in the other How-to shown on this site. Make sure to change bdver2 to native so that it detects your processor properly. also change the make -j6 to a different number, as per the number of cores you have. This does speed up compiling. 

echo Clean Start
rm -fr wine64-build
rm -fr wine32-build
echo Make Build Directories
mkdir wine64-build
mkdir wine32-build
cd wine64-build
../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --enable-win64 --without-gtk3 --with-vkd3d --with-vulkan --with-x
make -j6
cd ../wine32-build
PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --with-wine64=../wine64-build --without-gtk3 --with-vkd3d --with-vulkan --with-x
make -j6

If the compile is successful then the script shown below will uninstall any previous compiled version, and install the newest build.

cd wine32-build
sudo make uninstall
cd ../wine64-build
sudo make uninstall
cd ../wine32-build
sudo make install
cd ../wine64-build
sudo make install
cd ..
wineboot --update

Go set windows version to windows 10, so that the game will present the DX12 option, in the advanced settings, and then restart the game, and enjoy the WoW 8.0 Battle for Azeroth. You may also run Battle.net desktop app. Shown below is the script I use to run WoW.  To run Twitch, wine has to be set to Windows 7, but WoW has to be set to windows 10, to allow DX12.  The launch script takes care of that.  


Game Launch Script


#!/usr/bin/env bash
winetricks win10
env VKD3D_DEBUG=none WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 nice -20 wine64 '/home/steve/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe'
winetricks win7


WOW STREAMING ERRORS

As a reminder - this error has been popping up since the 7.3 patch.

There is a github repo with a "clean" Windows-version Cache-file set

github.com/1thumbbmcc/wowcache.git

There's a forum thread here at WineHQ about the error:

forum.winehq.org/viewtopic.php?f=8&t=30803s

and there are existing forum threads on both EU and US official WoW forums:

eu.battle.net/forums/en/wow/topic/17620271965

eu.battle.net/forums/en/wow/topic/17620282020

us.battle.net/forums/en/wow/topic/20765466460

As far as we can tell - some (not all) characters generate
unusable/unstable files in the Cache folder when playing under Wine on
Linux that result in the error/disconnect. Some players have reported
being able to play normally after just adding the Windows-version Cache
files (without first clearing the folder) but since 8.0 that hasn't been
the case for me - the error and disconnects persist unless I delete ALL
existing files in my Cache prior to extracting the .zip contents into
the folder. Also, subsequent clearing of the Cache folder (because of
conflicts with other patches/addons etc) has required once again
reloading the Windows-version Cache files or the error and disconnects
resume. This is just a workaround - the bug is obviously not fixed, but
it does allow you to resume play without the disconnects. Until Blizzard
corrects the actual file-creation problem I'll try to pop in here more
frequently to update and respond.

Comments

The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

Can not update the game from linux
by Simon Kristensen on Wednesday November 28th 2018, 10:09
I am dual booting ubuntu 18.04 / Windows 10

I have only installed Battle.net in my wine environment, and then located the World of Warcraft folder on my Windows partition.

I have an issue everytime there is an update to World of Warcraft. It detects that there is an update, and I press "Update". The progress bar says waiting, then initializing - and then it hangs there, until I get a popup saying "Oops error bla bla. try again".

So atm. I have to boot up in Windows, update the game and then reboot into Ubuntu, and then everything works fine.

Is anyone else experiencing the same problem. And is there a fix?
RE: Can not update the game from linux
by Steve Ebey on Wednesday November 28th 2018, 18:55
is your windows partition mounted read only? When you boot windows, did you disable fast shutdown and hibernation, so that linux can mount the partition as read-write instead of read only?
RE: Can not update the game from linux
by Lucas Pruvost on Thursday December 6th 2018, 3:52
I confirm, if anybody has problems while updating, this is certainly about your partition which is not correctly mounted.

Quickest way is to shutdown windows properly then remount your partition.
Solid black ground since Wine update on November the 13th
by Bebensucher on Thursday November 15th 2018, 10:18
Since i had a Wine update on Novmber the 13th the gound of nearly all areas in the game is a solid black.
Effects like flames are not shown properly, more like cubes.
Fps are worse than before.
Sometimes big solid green or blue triangles covering the seight.
Changing the graphic settings ingame seems not to have any influence.

Usually i start the game directly out-of-the-box, but now i tried vie PlayOnLinux older versions of Wine, but the problems stay.
It seems that a similiar issue is reported here: --> bugs.winehq.org/show_bug.cgi?id=46148

Ubuntu 18.04
Wine 3.20 (Staging)
ATI Mobility Radeon HD 5470 (yes i know, there is no driver support for this card after 14.04, but before the last Wine update it works fine)

Hope everything is easy to read and understand, my english is not very good.
RE: Solid black ground since Wine update on November the 13th
by Daouli on Saturday November 17th 2018, 6:41
I have the same issue, the ground of nearly all areas in the game is a solid black.
I I try to update the graphic driver and many others things but the problems stay.

Ubuntu 18.04
wine 3.20
Nvidia GeForce GTX 960
RE: Solid black ground since Wine update on November the 13th
by User Unknown on Monday November 19th 2018, 17:12
Sounds like the same issue I am having after upgrading to 3.2 staging.
Ground is black-more importantly unable to see ground effects for debuff/dmg, lots of geometric shapes for animations, decline in fps from 30 to 17 [have not figured out how to compile yet via Steve's directions/suggestions], movement key lag increased [not a w key issue, have verified with several new keyboards bought from store using 3 brands].
-currently unplayable for me

Steps to reproduce issue:
Just upgraded to wine 3.20 staging

Current OS: Fedora 29 gnome 3.19
Graphics: GTX 1070

Read directions for reporting bug, and I don't understand. Which may be the reason there are not many bugs reported here. It may be clear for people who understand the process already, but not necessarily for those with zero experience and posting their first report. Too many caveats.

Good directions would be: directions/CLI command/output options or field
Post OS info [uname -a]: field box for user output
Post wine version: Drop down menu with versions
Post Graphics Card [lspci | grep -i --color 'vga\|3d\|2d']: field box for user output
....etc.

I really really want to be able to play games on Linux, but I really don't see this working right now. I'll wait another week to see if there is a workaround or fix, but am seriously considering just having a windows machine for gaming....but I really don't want to, with a bad passion. I hate what windows stands for today. Catch 22, users can't use games on linux, developers won't make games for linux because of small user base...sigh.
So Blizzard App works fine, HOTS but WoW.... Kinda...
by WineIsNotForDrinkDude on Thursday November 15th 2018, 3:54
Does anyone have any clue how to fix following?:

-When I open WoW from Blizzard App- Wow window is empty (shows only echo of desktop apps) but music plays normal, you just cant see content.

-When I open WoW with Wow.exe everything works perfectly, but I have to log-in every time (obviously).

So anyone know how to play WoW deployed from Blizzard App?

Wine 3.20 (staging) + dxvk 0.92
RE: So Blizzard App works fine, HOTS but WoW.... Kinda...
by User Unknown on Friday November 16th 2018, 10:14
It's a known problem with the launcher itself. The launcher has multiple issues, so it seems most people have just avoided this issue. Per other comments, they just use the launcher to update the game and use the exe to launch the game.
RE: So Blizzard App works fine, HOTS but WoW.... Kinda...
by WineIsNotForDrinkDude on Tuesday November 27th 2018, 1:33
Thanks!
Yeah, that's what I'm doing.
Also I use now PBA for increase in FPS. I think it gets me about 30-40% more FPS and since I have weak CPU (and WoW depends on CPU as it's engine is flawed and irreparable (as Blizz says)) it helps.

DXVK is getting me another ~25% FPS more. So it's not bad overall. Totally playable :D In crowded spaces I have ~25 FPS and 40 in less crowded areas- and I have GTX 1050ti.

On Windows I have far better FPS but CPU is still bottlenecking. Ex.:
Witcher 3 on Windows- 40 FPS on ultra (including hairworks)
WoW on Windows- on Ultra 15 FPS (on modern areas like from Legion and BfA)- I have to decrease Environment sliders- especially Environment Detail to let's say 7 and then I get 40 FPS.
RE: So Blizzard App works fine, HOTS but WoW.... Kinda...
by HeyCitizen on Sunday December 2nd 2018, 7:55
I have this problem as well. My workaround is to select the option in Battle.net app to close when WoW starts. As long as the Blizzard app is no longer running when WoW starts, the window draws normally.
Complete steps
by User Unknown on Saturday November 10th 2018, 19:02
Hi, Thanks for the How To's. But I'm not sure how to make the script you are talking about. I also don't understand how to compile. It sounds like you need to do that after doing the steps in the script? if someone could help that would be great for us who are trying to use linux, and stay away from win.

Using F29, wine 3.19, nvidia GTX1070.

The graphics card shows up when you go to settings>details>about

myemaildummyaccount@protonmail.com feel free to contact me if that would be easier.
RE: Complete steps
by User Unknown on Saturday November 10th 2018, 19:37
-----Steps to reproduce-----

#Installed F29
via USB Media Writer

#updated F29
ping 1.1.1.1 (verifies connection)
sudo dnf clean all
sudo dnf upgrade --refresh
reboot
ping 1.1.1.1 (verifies connection)
sudo dnf clean all
sudo dnf upgrade --refresh (if nothing to update then proceed on. Repeat upgrade until nothing else to do)

#Installed Nvidia GTX1070 driver
sudo dnf install fedora-workstation-repositories
sudo dnf config-manager --set-enabled rpmfusion-nonfree-nvidia-driver
sudo dnf install xorg-x11-drv-nvidia akmod-nvidia
shutdown now
#unplug power cord, then press power button to bleed remaining electrons
#replug power cord, then restart machine

#confirm using nvidia card and test performance (optional)
/sbin/lspci | grep -e VGA
#Output looks like:
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
sudo dnf install glmark2
glmark2

#Installed Wine 3.19
sudo dnf install wine
reboot

#Create generic prefix/directory without su
winecfg
OK
reboot

#Installed WOW
#download installer file from wow website
wine World-of-Warcraft-Setup.exe
#installs launcher (used to update game)
#then installs actual game

#Start WOW.exe instead of launcher - as suggested to avoid in game issues
wine ~/Programs (x86)/Wow.exe
#login to character
#logout and exit (used to create initial files in your game folder, one of which you replace in next step)

#Replaced Cache folder
Download zip folder from github.com/1thumbbmcc/wowcache.git
Extract here
Delete old ~/Programs (x86)/World of Warcraft/Cache folder
Replace folder by copy/pasting extracted folder in ~/Programs (x86)/World of Warcraft folder.

----------Steps to re-produce complete---------
RE: Complete steps
by spaceman on Monday November 19th 2018, 8:15
shutdown now
#unplug power cord, then press power button to bleed remaining electrons
#replug power cord, then restart machine

Speaking as a support engineer, each time I see this I wonder "Who told you to do that?" and smile. We usually just recommend that in long list of instructions to either a) waste some time before the user calls back or b) make doubly sure that the user has actually rebooted. They lie they don;t believe it makes any difference. But somehow shutting down and "discharging the PSU/Motherboard" will do something miraculous a reboot won't.

For the installation of software this really isn't required. The are some disagreements about whether it may be necessary when installing drivers, for example NVIDIA graphics drivers after blacklisting Nouveau, but in over twenty years I've never actually been able to find any value in doing it.
RE: Complete steps
by User Unknown on Monday November 19th 2018, 17:19
Thanks, I too have the same understanding. But I've left it in there because it doesn't hurt anything by doing it. And as you stated, in some rare occasions, maybe it would have some impact, such as in NVidia related issues (I did mention directions for installing a GTX1070). Because of this, I don't mind taking the extra time. Appreciate the comment, but unfortunately it doesn't address the issue in the original post.

Thanks.
RE: Complete steps
by User Unknown on Saturday November 10th 2018, 19:45
#Its the staging version
wine --version
wine-3.19 (Staging)
vkd3d works now for WoW with DX12
by Steve Ebey on Thursday October 18th 2018, 17:40
I have found the way to run wow with DX12 and it is good. vkd3d has matured to the point it will work with World of Warcraft, and give very similar performance to Windows 10 DX12. Also since it uses all wine dlls and no sideloaded dlls or modded dlls, the chance of bans and other incompatibility issues drops drastically. On my Fedora system I did sudo dnf install libvkd3d* to get the devel and header files, to compile wine with vkd3d support. I then went into WoW, in the system interface, under advanced and set DX12. Once that is done, exit and restart WoW, and as long as you have vulkan drivers installed, it will use them to do dx12. Enjoy.
RE: vkd3d works now for WoW with DX12
by Björn Bidar on Thursday October 18th 2018, 18:14
How did is compare to DXVK with d3dx11?
That will be interesting when multi threaded d3dx12 comes.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Saturday October 20th 2018, 9:32
I do not see DX12 as an option in WoW. I am not able to run any dx12 tests in wine with vkd3d either (GeeXLab Triangle or similar). I just fails.

So, this begs the question: What graphics adapter do you use and what driver?
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Saturday October 20th 2018, 11:27
I run GTX 970 and nvidia proprietary 410.66. I also self compiled, including the pba patches, and the fps are fairly close to the windows 10 dx12 version. if you compile without pba, then you will have lower fps. You must have the libvkd3d to add support for the dependencies that wine needs to compile. Once that is done, run it and set the api to dx12 in the system settings in game, under advanced. You have to exit and restart wow for the change to activate. The nvidia drivers have added a setting in the nvidia-settings software, to turn on the api info. Look under the OpenGL options and put a check mark in the api settings. it will show GL and the FPS in the upper left corner. Even though it shows GL the vkd3d is running, and the DX12 features are active.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Saturday October 20th 2018, 15:19
What does "it will show GL and the FPS in the upper left corner." mean?

If it means what i THINK it means, then you are not running vkd3d at all.

I have not tested the 410.66 driver yet, but from what i read at Phoronix: "includes a graphics API visual indicator for showing whether OpenGL/Vulkan is being used by a game/application"
So, if it reads "GL and the FPS" for you, it means nVidia is using OpenGL and not Vulkan. (Yes, vkd3d or DXVK IS using vulkan and not OpenGL).

That you also indicate having lower fps without pba patches means you are using wined3d (ie. d3d -> OpenGL).

Could you possibly paste whats in "/World of Warcraft/Logs/gx.log" file? Does it read something like "D3d12 Device Create" and such?
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Saturday October 20th 2018, 20:37
You are correct, the gx log shows it tries to run D3D12 device create, it fails, and reverts to DX11 and openGL. So, I have all the vkd3d dependencies, and I have an updated vulkan driver, which works with DXVK for DX11. What am I missing to make vkd3d work as it should?
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday October 21st 2018, 5:32
Guess you have the same problem as me (and possibly "everyone else"), that it does not work.

I have tried asking on the WineHQ forums if there is a feedback/bug report for this libvkd3d, cos i dont really know where to put feedback for this.
Try this:
git clone source.winehq.org/git/vkd3d.git
cd vkd3d
./autogen.sh
./configure --enable-demos
make && make check-TESTS

Check the test-suite.log for errors. I get amongst other fails that "Max supported feature level 0xb000", and that is DX11_0, but my GTX970 should support up to DX12_1. Probably just not mature yet, or working with AMD cards possibly? Dunno.. Not possible to give feedback to devs or get any reports from those.

PS. If you cant compile the source, you might be missing spirv-headers and/or SPIRV-Tools package or something like that.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Sunday October 21st 2018, 15:31
built and ran test, you are right, shows that I do not support DX12, in the feature output. Booted to windows, and saw that dx12 works fine. For now, I have reverted to using dxvk and dx11 in game. An ubuntu user claims to be running vkd3d with dx12 on ubuntu, so maybe something with fedora. Do a google search for vkd3d and you should find the post that claims vkd3d works with dx12 in World of Warcraft. Credit for making it work is given to Codeweavers, so maybe at some point, that will make it into mainstream wine for us to use.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Monday October 22nd 2018, 8:49
I use Ubuntu 18.04 and it does not work for me.
Not sure what driver this is supposed to work with tho, as for all i know it might be working with nouveau.. or AMD?
RE: vkd3d works now for WoW with DX12
by User Unknown on Friday November 16th 2018, 10:23
Do you have instructions for those that do not natively have the directions installed on our cerebral cortex? Would love to download and install this buff. Specifically, what do you mean "to compile wine with vk3d support"?

Thanks
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Friday November 16th 2018, 13:30
if you have the libvkd3d installed, then you can add --with-vkd3d as a configure option. If you do this you MUST have the vulkan drivers for linux installed as well. Now, having said that, so far, vkd3d does NOT appear to properly work with DX12 as of yet. The people who run Crossover, the paid commercial version of wine, they claim to have fixed the vkd3d libraries, to make it work. It is just not in main line of wine as of 3.20. i still use dxvk to run wine with DX11. Posted here is the command I use, for my specific processor, to compile wine myself, with vkd3d and vulkan support. be sure to pay attention to march and mtune and change both to native to compile for you so that you do not get the code specific to my processor. I run an AMD 6350 piledriver, which shares architecture with bulldozer version 2 (bdver2), per the amd cpu website.

clear
echo Clean Start
rm -fr wine64-build
rm -fr wine32-build
echo Make Build Directories
mkdir wine64-build
mkdir wine32-build
cd wine64-build
../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS DWINE_NO_DEBUG_MSGS' --enable-win64 --with-vkd3d --with-vulkan --without-gtk3
make -j6
cd ../wine32-build && PKG_CONFIG_PATH=/usr/lib/pkgconfig ../wine/configure CFLAGS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --with-wine64=../wine64-build --with-vkd3d --with-vulkan --without-gtk3 make -j6

Hope this helps. Good Luck.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday November 18th 2018, 10:38
As a comment to WoW running on DX12 with vkd3d, it IS actually working on my nVidia GTX970 after i added a patch for wine i got on IRC.
Kinda hard to do any benchmarks, cos it seems as vkd3d cant disable vsync just yet (perhaps?). ingame vsync is disabled, but does not take. Can do some more testing with this tho :)

So far vkd3d seems to support dx12 with Feature Level 11_0, so i guess any benefits from things like multithreaded rendering or whatnot that higher featurelevels give is not supported i guess.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Sunday November 18th 2018, 13:42
Can you share the patch, that allegedly causes dx12 to render to vulkan? What version of driver are you running? Do you have the api setting in the opengl section of your nvidia-settings, to show which api is running? Have you verified in the gx.log file in the logs folder in the world of warcraft directory, that dx12 is actually running? My gx.log shows dx11 fallback, with vkd3d.

as far as vkd3d is concerned, I am agnostic, and will believe it when I see it for myself. Your help would be appreciated. Does the irc patch you used have to be compiled in, or does it patch the wine executable after compiling is done?
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Monday November 19th 2018, 4:07
@work atm, so dont have the patch here... Will post once i come home, but so far i can tell you my other details:

GPU: nVidia GTX970
Driver: nVidia 396.54.9 (latest beta with vulkan patches)
Wine: staging-3.20 w/aforementioned patch

Before compiling with this patch, the WoW/Logs/gx.log indicated "failed to create d3d12", and a fallback to d3d11. With patch the d3d12 device is created successfully.

Performance in crowded area is slightly below that of DXVK, but it seems vkd3d has no way of disabling vsync, so it caps (for me) at 60fps.

The nVidia 396.54.9 driver does not have this "api info" thing that 410+ drivers have... but its the driver that has the most up-to-date vulkan fixes, so for vulkan (dxvk/vkd3d) i would prefer using that.

Will post patch once i get home :)
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Monday November 19th 2018, 8:57
Put the patch here : github.com/SveSop/nVidia_vkd3d

Snippit from World of Warcraft/Logs/gx.log :
11/18 18:00:40.949 LogOpen
11/18 18:00:40.980 ConsoleDetectDetectHardware():
11/18 18:00:40.984 cpuIdx: 1
11/18 18:00:41.031 ConsoleDeviceInitialize(): hwDetect = 0, hwChanged = 0
11/18 18:00:41.096 D3d12 Device Create
11/18 18:00:41.099 Format 1920 x 1080 Fullscreen, ArgbX888, vsync 0
11/18 18:00:41.176 Taking Adapter 0 by name: Vendor Id 0x10de, Device Id 0x13c2
11/18 18:00:41.181 NVIDIA GeForce GTX 970
11/18 18:00:41.237 Detected NvAPI and checking if it's valid...
11/18 18:00:41.240 Caps:
11/18 18:00:41.244 Vendor ID: 10de
11/18 18:00:41.247 Device ID: 13c2
11/18 18:00:41.251 AFR Groups: 1/1
11/18 18:00:41.255 Feature Level: DX=3, GL=0, MTL=0
11/18 18:00:41.268 D3d12 Device Create Successful
11/18 18:00:41.304 CPU Processor Detection: 12 H/W threads
11/18 18:00:41.307 Memory Detection: 16748654592 bytes of physical memory available
11/18 18:00:41.311 Detected Graphics Defaults: 6 (CPU = 6, GPU = 7, MEM = 6)
11/18 18:00:41.325 Resample::CreateResources
11/18 18:00:41.479 RenderSettings::NotifyChanged
11/18 18:00:41.525 Liquid::CreateProceduralTextures
11/18 18:00:41.925 PortraitDeviceCreate
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Saturday November 24th 2018, 8:41
Got vkd3d working, sort of, with latest nvidia 415.18. I say sort of, because I compiled vkd3d from source, and apparently vkd3d 1.1 is not fully implemented. Going to remove it, and recompile wine 3.21 to see if the error in the bug report I added goes away.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Saturday November 24th 2018, 9:04
ok, libvkd3d 1.0 that ships with fedora 29 does not work, at all. Error #132, even with the earlier wine, and also the latest wine 3.21. If I use the git source for vkd3d and compile and install the library, it loads, and then crashes in certain areas of the game. To that end, I submitted the bug report, but may need to modify the information, to reflect that I used the compiled vkd3d and not the distro version.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Saturday November 24th 2018, 14:12
The distro versions are frightfully outdated for most i think.

I did not test vkd3d intensively, most cos of the "vsync always on" thing, and cos it kinda feels a wee bit lower performance than dxvk for now. And i did use the latest source from vkd3d git.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Saturday November 24th 2018, 15:50
so, you and I are in the same boat. I will be using dxvk, and as of a few hours ago, dxvk .93 is out. Have installed it, but not tested it yet. Will keep an eye also on wine-staging, to see if the vsync issue gets fixed and if vkd3d matures further. I am just glad I got it to run, albeit very briefly. Shows they are making progress.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday November 25th 2018, 7:01
I see they added that patch in 3.21, however i did not get WoW running with 3.21 alone, but had to change 1 line.

Not sure WHY 3.21 did not "end the expression" the same way as the previous patch, other than it is ofc slightly modified over the "hack patch".. but well.

Updated the patch on my github if you want to experiment more tho :)

PS. It is important that you check wow/Logs/gx.log after testing tho, cos if D3D12 Device Create fails, it will just fall back to D3D11 and you wont really be notified.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday November 25th 2018, 9:35
I jumped the gun on that one, cos im using wine-tkg from the lutris repo, and downloaded their wine-tkg-3.21 "release" source.. but apparently it seems to not be up to 3.21 really. (The commit link also points to 3.20 on their git).

Rebuilding from git, and 3.21 seemed to work, so the patch is included in 3.21 and WoW works with d3d12. (Save for any pending bugs ofc)

Sorry for the confusion :)
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Sunday November 25th 2018, 14:07
Ran for about 40 minutes in game, then crashed, and had a screen full of fixme, talking about ignoring multisample enabled. Not sure if that led to the crash or if that was just a side effect. I will also see what version of vkd3d library I compiled with, and let you know. I think it was 1.0 from the repo on fedora, but will double check. Since the vsync is ON the best I get is 60.00 fps. DXVK seems to honor the game vsync setting, but the vkd3d does not. I might make a bug report for that, if it is not fixed soon. I might also compile the latest vkd3d source, and see if that library works better and honors the games vsync setting. I am running version 1.1 from the most recent vkd3d git commit. When I revert to vkd3d library from fedora, I get the following.

fixme:d3d12_device_CreateHeap: iface 0x7e51d960, desc 0x25f8e0, riid {6b3b2502-6e51-45b3-90ee-9884265e8df3}, heap 0xf5dc0b0 stub!
ACCESS_VIOLATION : error 132: ERROR #132 (0x85100084) Fatal exception!
The instruction at "0x00000001403b5c5a" referenced memory at "0x0000000000000000".
The memory could not be "written".

not making a bug report, because once 1.1 is released to distros, the problem will go away, sort of. and they may even work on fixes for vsync and the multisample fixmes that I get. sorry if this is long winded, but wanted to give you as much information as I could to aid in your testing.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday November 25th 2018, 16:30
Thanks for testing :)

I would guess vsync might not be implemented yet. It was not implemented at the start with dxvk either, so vsync may be a thing not prioritized perhaps? I saw some notion about 4.0 code freeze for wine coming up soon, so this means "no new features" until 4.0 is out. If that means "vsync is a feature" or a "bug" remains to be seen :)

You could try to set export VKD3D_DEBUG="none" , so that most of those fixme's get weeded out. Having too many of them could slow things down tbh. Those "fixme's" are in general stuff that are not implemented, and there for info... and chances are some multisample bits are not implemented.

Still exciting tho :)
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Sunday November 25th 2018, 21:45
did the debug = none, and it ran about 50 minutes, before it crashed. back to running dxvk, .93 version. also, forgot to mention, I am running 415.18 from nvidia. the 396.54.09 did not work with vkd3d 1.0 or patch, or 1.1 on my system, but as soon as I went back to 415.18, I could load and run, for a little while with dx12. Hope they do fix the vsync issue. tried finding an environment variable for that, but no luck. if you know of one, please let me know. waiting patiently for the next update to wine. on a side note, why does the git server for the devel source only run at 1.7Meg per second. Takes almost 8 minutes, to download the repo for the source from winehq, thought it would be a faster download. My download speed from my isp it 1Gbps (1000Mbps), so I should be getting it fast, i would think.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Monday November 26th 2018, 8:34
You can try github.com/wine-mirror/wine if the WineHQ server is slow. Might depend on load and bandwidth allowed for the server.

I have not tried 415.18 driver yet, but i dont think i have played for an hour or more with d3d12 either, so cant say if a crash would happen for me.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Monday November 26th 2018, 10:29
If you could test for about an hour, just to see if your driver works better, I would appreciate that. Thank you for the link to wine-mirror as that downloads at around 50Mbps instead of 1.71Mbps.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Monday November 26th 2018, 14:45
I see there is a update to vkd3d today that fixes some multisample bits... So might be that fixes the "fixme" errors... Gonna rebuild the vkd3d library and see if i can test some.

PS. The formatting on this thread starts to get rather.. uhm.. crappy.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Monday November 26th 2018, 15:32
Hehe.. Soon there will be lines of 1 letter each :P

Anyway, built ed4f8749f25b289e392d00897afe43d8398ac861 from git, and gave it a go.

Working oki save for vsync always on.. And i crashed one time during the 40'ish or so minutes i played:
ERROR #132 (0x85100084) Fatal exception!

Program: C:\Program Files (x86)\World of Warcraft\Wow.exe
ProcessID: 8
Exception: 0x80000101 (unknown exception) at 00007f889f661e97

This is with nVidia 396.54.9 driver and wine-tkg-3.21 (ESYNC enabled) The wine version works fine with DXVK as i raided for around 4 hours last night without a hitch..
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Monday November 26th 2018, 18:01
Set the comment mode to flat, here in the appdb and it will put all the comments left justified. I have the latest vkd3d source, and get the same results as you, the multisample message persists. My wine 3.21 is self compiled to specifically match my own processor architecture. I get about 10 extra fps using the configure settings shown here in the how to. I love solving puzzles, and this appears to be a pretty good one.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Tuesday November 27th 2018, 22:20
I have had the game running for 2 hours, with dx12, after making the following modification to device.c in the /vkd3d/libs/vkd3d

if (dst_idx == dst_range_size)
{
assert(dst_idx == dst_range_size); # Original line 2009
}
if (dst_range_idx == dst_descriptor_range_count - 1)
{
assert(dst_range_idx == dst_descriptor_range_count - 1); #Original line 2010
}

After you modify the file, and save it, change to the vkd3d top level folder, run make, then sudo make install, then sudo ldconfig. After doing that, you can run DX12 in WoW, and you DO NOT have to recompile your wine, or if running a distro install, you do not have to reinstall it, since it modifies the libvkd3d that was used to build wine. Good luck, and let me know if you have questions.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Saturday December 1st 2018, 16:47
Posted a patch for vsync on github for you @Steve Ebey :)

Anyway, i got to test a bit tonight, and i was kinda thinking everything was fine and dandy with 415.18.02, after doing some dailies, couple of runs to Uldir++ and no issues. But when i got to "Vigil Hill" in Tiragarde Sound, i got the crash again.
To reproduce: Go to Loc: 57.5 / 64.5 without the patch you posted above, and see if you crash.

I logged back in, and crashed immediately. Ended up putting -d3d11 on my launcher, and move the character away a bit, and then log back in with d3d12. Was no problem until i move back to around that same spot. To ME it could seem as when some effect (there is fires and smoke around there) is in view, that crash happens. Might need to do some logging and see what i can find out, and possibly post a bug about it.

Recompiling vkd3d with the patch you posted, the crashing stopped.

Not that i am a coder at all, but putting a couple of if's in between all the other if's in that code SEEMS kinda hack'ish, so i guess there is some way to fix this in a more optimized way. Keep testing tho. Atleast WoW is pretty playable with d3d12 and vkd3d :)
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Saturday December 1st 2018, 17:09
Looked on the github link from your previous patch, could not find the vsync one, where do I need to look, and thank you for this.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday December 2nd 2018, 5:41
Posted it as a comment on the dxvk issue you posted.

Anyway.. added it to my github.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Sunday December 2nd 2018, 7:49
Thank you. I have added it, and built wine. vsync shows off now, but the fps is terrible. Going to try deleting the nvidia cache to see if that helps.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Sunday December 2nd 2018, 9:37
I did a comparison test with DXVK, and to me the fps was far from terrible tbh.
Graphics set to "7" ingame. Fly from Boralus Fort Daelin, and calculate average from 3 flights.
Min/Max/Avg fps:

VKD3D:
Boralus -> Fort Daelin
63/209/154
Fort Daelin -> Boralus
53/200/135

DXVK:
Boralus -> Fort Daelin
46/246/171
Fort Daelin -> Boralus
42/254/159

Not a HUGE difference tbh. I drop from around 60'ish down to 50 or so in town on a busy night tho.. so it is lower performance, but not terrible for me atleast.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Sunday December 2nd 2018, 13:02
made a novice mistake. I had been playing with the vkconfig that came with the latest vulkan sdk, and I had not reset it. Once I did that, my fps soared, and is almost the same fps that I tested in windows 10. I am ecstatic at the way it works and greatly appreciate all the efforts that everyone has made, to help me get this far. I want to let you know how grateful I am for the help you all have given me. I will install for 415.18.02 to see if I can get even more fps, but if not, I am going to enjoy playing wow, and also being able to run the battle.net app, to update wow with. Now I just need to figure out how to get Twitch working, and I can stop using windows completely.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Monday December 3rd 2018, 18:37
Nvidia 415.18.04 is the current beta driver, with fixes designed to improve compatibility with unity games, and by side effect, also increased the fps for me in pandarian zones.
RE: vkd3d works now for WoW with DX12
by Steve Ebey on Friday December 7th 2018, 7:09
Updates"
vkd3d incorporated a version of my fix, in the latest git pull, so the crashes have stopped. I updated my how to that is posted here, to reflect my current system build and to show people how to make a vkd3d library from the git source. I am also enjoying the fact that battle.net and wow can run from linux. I also succeeded in following the appdb setup for twitch client and can update my addons from linux.
RE: vkd3d works now for WoW with DX12
by Sveinar Søpler on Friday December 7th 2018, 10:19
Or one can use the wowaddonupdater python script from: github.com/kuhnerdm/wow-addon-updater for those that dont want to use Twitch :)

Quite a lot different on Ubuntu to make wine and/or vkd3d, but not that hard tbh. Considering setting up a "daily" ppa for ubuntu ppl and vkd3d, but well.. another project to maintain hehe.
your 3d accelerator card is not supported by World of Warcraft. For more information please see https://us.battle.net/support/en
by Sven Erik on Thursday October 4th 2018, 5:00
I get this error message when trying to start. But the game works on Windows on the same computer.

Using Trisquel 8 with the newest Linux-Libre kernel and Wine Staging
RE: your 3d accelerator card is not supported by World of Warcraft. For more information please see https://us.battle.net/suppor
by spaceman on Sunday October 14th 2018, 8:07
Yeah, I think we've all seen this, I certainly have when I haven't installed my graphics drivers correctly.
vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Pete on Friday September 21st 2018, 4:58
Nvidia GT710 with 396.54 driver
16Gb Ram
AMD FX6300
Wine-Staging 3.16

Vulkan installed and running ok natively (vulkaninfo and cube run fine).

Wont run wow with dxvk 0.70 or 0.72 and wont run cube or vulkaninfo in wine after installing VulkanSDK.

Not sure what the problem is but assuming its a configuration error somewhere.
Had same problem with staging 14. Purged wine and reinstalled to new prefix but same problem.

Any ideas ?
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Steve Ebey on Friday September 21st 2018, 6:36
After unzippping the dxvk zip file, did you change to the dxvk folder and run winetricks --force setup_dxvk.verb

it installs the dll files and puts the override in the registry.
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Pete on Friday September 21st 2018, 8:34
Yep, and checked everything installed ok. Got 5 overrides and the dll files copied to system32 and syswow64.
Does dxvk rely on vulkan working in wine as that seems to be a problem?

I copied a winevulkan.json file to c:\windows and set 2 registry keys for Khronos\Vulkan\Drivers also but that made no difference.

Running Mint 17.3
Vulkan 1,1,70 and latest nvidia driver 396.54.05 from ppa:graphics-drivers/ppa (tried the 380 version driver also but same problem)

vulkaninfo, cube and smoketest all run fine natively but wont run in wine with the windows sdk loaded giving error as title.
wow with dxvk gives an unsupported graphics card error (assume its related to title error)

Any other info you need or any suggestions?
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Steve Ebey on Friday September 21st 2018, 16:41
are you running staging? WoW requires some patches from staging, to load properly. I am not running any rpm based nvidia drivers, instead I get them from the nvidia.com site, and use dkms to update the kernel, so I do not have to worry about fedora updating video driver. I am running 396.54 with dxvk, on my GTX 970 4Gig Card. Shown here is my starting command line.

env DXVK_HUD="fps" LD_PRELOAD="libpthread.so.0 libGL.so.1" WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 nice -20 wine64 '/home/steve/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe'

Hope this helps
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Josh R Raymond on Monday October 1st 2018, 15:11
You don't want the windows vulkan sdk, you just need vulkan installed on the OS with a vulkan-compatible video driver (both of which you have). Make a fresh wineprefix and use winetricks to install dxvk into WINE. That's all you need to do. winetricks is updated for the newest version of dxvk(0.80) which runs great.

To get winetricks:
1. $ wget raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks
2. $ sudo chmod +x winetricks
3. $ WINEPREFIX=/path/to/fresh/prefix ./winetricks dxvk

Then start WoW with env WINEPREFIX=/path/to/prefix DXVK_HUD=fps DXVK_FAKE_DX10_SUPPORT=1 __GL_SYNC_TO_VBLANK=0 LD_PRELOAD="libpthread.so.0 libGL.so.1" WINEDEBUG=-all __GL_THREADED_OPTIMIZATION=1 wine "/path/to/Wow.exe"

Enjoy.
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Sveinar Søpler on Wednesday October 3rd 2018, 1:20
There is, or should not be, any reason to modify any .json file or any of that sort, as wine-3.17 implements the vulkan loader directly.

DXVK requires vulkan to work in windows (wine) tho, so make sure your linux drivers also have 32-bit libraries set up, as a 32-bit windows app requires linux 32-bit vulkan support.
If you cant run vulkan apps under wine in a clean prefix, you know its not DXVK causing you problems :)

There is both a 32-bit and 64-bit vkQuake version here: github.com/Novum/vkQuake/releases
You need some free version of Quake1 and then you can run the vkQuake version downloaded from the link above. Test both 32 and 64 bit version with nothing but a clean wine-3.17 prefix and it SHOULD come to life. If it works, you can install DXVK, and try Unigine Valley w/DX11 in the same prefix. If that fails, start digging through DXVK logs to figure out what stops :)
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Björn Bidar on Thursday October 4th 2018, 7:48
Wow itself is 64bit only and doesn't need 32bit libs.
So you can run wow without 32bit support (which is what I do currently).
Only that launcher is 32bit.
RE: vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
by Sveinar Søpler on Thursday October 4th 2018, 8:14
I too run WoW with a "pure 64 bit" compile... But i still need 32-bit support when patching as the Battle.net app is 32-bit.

Testing both 32 and 64 bit vkQuake was more for general troubleshooting with winevulkan support :)
Audio stuttering
by YaoMitachi on Saturday September 15th 2018, 13:04
Who else gets stuttering sound in the frame drops of the initial loading?
RE: Audio stuttering
by Josh R Raymond on Monday October 1st 2018, 15:17
I get odd audio glitches occasionally, simply changing your sound device in the in-game menu will resolve it.
RE: Audio stuttering
by spaceman on Tuesday October 16th 2018, 6:09
Repeatedly, after about 10 minutes has elapsed, and then again in another 10 minutes...
RE: Audio stuttering
by Josh R Raymond on Tuesday October 16th 2018, 7:25
Mine are rather rare, like.. Maybe once every 20 times I open the game, after I login to a took the audio will be glitchy, changing the sound device I game as stated above fixes it without it returning. Try installing xact with winetricks
dxvk ban?
by Jen on Thursday September 13th 2018, 19:26
I'm hearing that Overwatch players using dxvk are getting banned. Is it happening with WoW, as well? I haven't heard anything...

www.reddit.com/r/wine_gaming/comments/9fkuxx/overwatch_avoid_async_option_for_dxvk_banned_for/
RE: dxvk ban?
by John Porterfield on Saturday September 15th 2018, 9:06
Looks like blizzard is overturning bans for this.
RE: dxvk ban?
by Josh R Raymond on Monday October 1st 2018, 15:18
Confirmed not only is Blizzard overturning bans for this, but they are actively tuning the WARDEN program to not issue bans for use of dxvk in the first place.

Source: Just search the forums for "linux ban dxvk"
Several issues
by Daniel Ceregatti on Tuesday September 4th 2018, 18:06
* Adding all those compiler flags created binaries that generated illegal instructions for me. I had to omit them because of that. Just stick with `./configure --enabled-win64`, and you should be fine.
* I had to manually add a ton of deps. Watch the list at the end of what won't be compiled, and install the development libraries for all the things you want. I had to add a specific package to get OpenGL to be "supported". It didn't work "out of the box".
* There's a - missing before the D in one of your defines which should be corrected, should you choose to pursue using those flags.
* The patch error was there earlier today, then someone made a commit between the time I originally checked the code out and the time I tried it for the first time (git pull if you haven't). The patching works with no conflicts as of 4PM PST today.

Hoping this gets me beyond the "failed to create graphics context" that battle.net is reporting.
RE: Several issues
by Steve Ebey on Thursday September 6th 2018, 11:47
I would hope, as stated in the how to, that you changed bdver2 to native unless you run the exact same processor as me. if you are using dxvk, then use winecfg to make a specific entry for Battle net app, and remove the dll overrides for dxvk, that should fix the battle.net problem. Also the script in the how to has word wrapping that this website inserted, so you must manually remove the word wrap, and the ./configure options should work just fine.
./patches/patchinstall.sh: 1581: ./patches/patchinstall.sh: autoreconf: not found
by Sven Erik on Monday September 3rd 2018, 6:11
I tried following the guide one more time now, unfortunately I meet a problem at the same place as before. But I get a different error message:

"Applying /tmp/tmp.kIF8ZKVy5t
./patches/patchinstall.sh: 1581: ./patches/patchinstall.sh: autoreconf: not found
ERROR: 'autoreconf -f' failed."

Any idea what this might be Steve?
RE: ./patches/patchinstall.sh: 1581: ./patches/patchinstall.sh: autoreconf: not found
by Sven Erik on Monday September 3rd 2018, 6:27
After I installed a package called "dh-autoreconf" and executed the command once more I ended up with an error message that looks very similar to the one I encountered last time:

"error: patch failed: dlls/ws2_32/tests/sock.c:3601
error: dlls/ws2_32/tests/sock.c: patch does not apply
ERROR: Failed to apply patch, aborting!"
RE: ./patches/patchinstall.sh: 1581: ./patches/patchinstall.sh: autoreconf: not found
by Sven Erik on Monday September 3rd 2018, 6:28
Yup, it *is* the exact same error message as last time.
RE: ./patches/patchinstall.sh: 1581: ./patches/patchinstall.sh: autoreconf: not found
by Steve Ebey on Monday September 3rd 2018, 19:11
you need to do a fresh pull, after installing autoconf, it sounds like it tried to patch over a patched copy of wine.
In-game Shop
by Josh R Raymond on Monday August 27th 2018, 1:37
I've been unable to access the in-game shop since the update in oct that removed WinXP support. I use to have to set the winecfg to WindowsXP to use the shop, since now that won't run the game, I'm not sure what to do, the shop screen loads, but after awhile the loading icon dissapears and the blue screen just stays empty
ERROR: Failed to apply patch, aborting!
by Sven Erik on Sunday August 26th 2018, 8:44
I tried to follow the How To/Notes on how to build PBA staged Wine, in hopes that this would mitigate the "your 3d accelerator card is not supported by warcraft" error message I got when Launching WoW in Wine Staging.

It all went fine up until the point "./patches/patchinstall.sh DESTDIR="../wine" --all"

When I executed that command I get this error message:

"error: patch failed: dlls/ws2_32/tests/sock.c:3601
error: dlls/ws2_32/tests/sock.c: patch does not apply
ERROR: Failed to apply patch, aborting!"

Does anyone in here know what this mean?
RE: ERROR: Failed to apply patch, aborting!
by Steve Ebey on Sunday August 26th 2018, 17:21
sounds like staging has not been rebased against the latest version of the development repository.
RE: ERROR: Failed to apply patch, aborting!
by Sven Erik on Monday August 27th 2018, 7:11
Well if that the case, how did the person writing the How To/Notes make it work? :P
RE: ERROR: Failed to apply patch, aborting!
by Steve Ebey on Monday August 27th 2018, 7:21
When I wrote the how to, it did work. Wine staging is a work in progress, and there are numerous commits, where the wine-pba has to be rebased to apply properly, so this happens about once a month, and I just wait for pba to be rebased against the latest staging. Most of the time the rebase takes about 1 or 2 days, but in this case, staging has moved some of wined3d over to a different file, and pba can not find what needs to be patched.
RE: ERROR: Failed to apply patch, aborting!
by Sven Erik on Monday August 27th 2018, 7:45
I do not fully comprehend all this, but am I right to assume that what you are saying is that if I follow your How To sometimes it will work and sometimes it will not work, so it's worth a shot to try again after a day or two? :)
RE: ERROR: Failed to apply patch, aborting!
by Sven Erik on Monday August 27th 2018, 7:47
I re-read this reply now and I think I understand it better.

Am I correct to assume that what you are saying is that when you did it worked, but as of now it doesn't work, but possible it will work in some time?
RE: ERROR: Failed to apply patch, aborting!
by Steve Ebey on Monday August 27th 2018, 7:54
yes, the problem appears when I apply the pba patches, and Firer4t is the one who usually rebases to the most recent staging build. I can only assume that they are busy with work or family, and have not had the time to do it. My currently compiled and working version is
wine-3.14-161-g70fbfa2cb8 (Staging) so once the person known as Firer4t has a chance to rebase it, then it will work. For the time being, I just do the dxvk build, since I can run vulkan on my system. I have a gtx 970 that supports vulkan. pba is for those with older hardware that can not use vulkan.
RE: ERROR: Failed to apply patch, aborting!
by Sven Erik on Monday August 27th 2018, 7:56
I think I understand! :)

Thank you for taking your time to reply and being helpful.

Do you know if there is any way to be notified in some way when it is rebased?
RE: ERROR: Failed to apply patch, aborting!
by Steve Ebey on Monday August 27th 2018, 8:14
i check about 6 times a day, so when it patches properly, I will post here. I do not have any contact with Firer4t so I just try it often, and see what happens.
RE: ERROR: Failed to apply patch, aborting!
by Sven Erik on Monday August 27th 2018, 8:17
I understand :) thanks!
RE: ERROR: Failed to apply patch, aborting!
by Kosta on Wednesday August 29th 2018, 6:17
I have the almost same problem :
error: patch failed: dlls/wined3d/wined3d_private.h:3557
error: dlls/wined3d/wined3d_private.h: patch does not apply

When I try to patch. Did you find a way to make it work?
RE: ERROR: Failed to apply patch, aborting!
by Steve Ebey on Monday September 3rd 2018, 19:15
As of today, 09/03/2018, I have successfully patched wine with pba, and the new wine version is now 3.15 (Staging). I used the script, as detailed in the how to, and had no problems with either the staging patches, or the pba patches.
RE: ERROR: Failed to apply patch, aborting!
by Elijah Rum on Monday August 27th 2018, 17:19
could you please fix the howto then? CFLAGS environment variable should be applied to 'make' command, not 'configure', since these are compiler flags and have nothing to do with build configuration.
RE: ERROR: Failed to apply patch, aborting!
by Steve Ebey on Monday August 27th 2018, 22:03
Word wrap here may have given you the impression that cflags was part of its own line, instead of being part of the configure command, which passes the cflags to make.
RE: ERROR: Failed to apply patch, aborting!
by Elijah Rum on Tuesday August 28th 2018, 4:56
oh indeed seems you're right, sorry.
strange that they didn't applied when i tried to do that way and applied when given to make..
intel hd?
by Elijah Rum on Saturday August 25th 2018, 10:30
using mesa 18.3.0 build from git, wine-3.14, dxvk-0.70 on fedora 28
on intel hd 5500

Without dxvk works as usual - i get solid 25-30 fps in empty areas with crappy looking graphics - that's okay
with dxvk however, graphics look much better, both ingame fps counter and dxvk hub show 30-40 fps, but it feels much more laggy, than without dxvk.
any ideas why that's happening?
RE: intel hd?
by Steve Ebey on Saturday August 25th 2018, 16:16
could be the graphics cache with dxvk, since it renders much more. I usually have some lag after a driver change or a new compile of wine. The graphics rendering has to rebuild the cache. One way to help, is to take long taxi rides, from one end of the map to the other, over highly populated areas. Just remember you will have to do this when video driver or wine get upgraded.
RE: intel hd?
by Elijah Rum on Sunday August 26th 2018, 14:50
it might be, thank you.
what i noticed (rather strange) is that whilst in orgrimmar counter shows 25 fps max, it is waay more playable than in mulgore, where fps counter shows me up to 50 fps and is absolutely laggy.
i tried taking taxi rides for about half a continent (have only access to 20 level characters, since i don't really want to pay for a month until i rule this stuff out), didn't help. will google and maybe try something else, sigh.
without dxvk it all is much more playable, though fps get only up to 25-30 in empty areas, so would be neat to actually be able to get 50 there.
in the worst case i'll just wait until i get a hardware upgrade this winter.
RE: intel hd?
by Peter on Monday August 27th 2018, 7:54
It looks like DXVK+WoW has some sort of frame timing issue. If it's running at 60 FPS, everything is sunshine and roses.

If I turn off vsync and WoW's frame rate limiter, I get 80 FPS and the game runs terribly. It feels like 10 FPS. The mouse doesn't move properly. I set the framerate limiter to 60 and it feels much, much smoother.

Run through an area with fog or something and my framerate drops as expected, but DXVK's overlay says I'm still getting 45 FPS. It feels more like 10.

If I turn off compositing, WoW feels much smoother even though it claims to be running at the same frame rate.
RE: intel hd?
by Steve Ebey on Monday August 27th 2018, 8:17
are you also running intel hd driver? I run a gtx 970 with nvidia proprietary driver version 396.54. I am also running dxvk 0.70. Tell me what you have please, so I can see if the dxvk repo has any suggestions for it.
RE: intel hd?
by Elijah Rum on Monday August 27th 2018, 8:43
I'm using an intel i915 modeset drivers which come with the kernel i suppose.
could also try intel drivers from git probably. will do that in the evening.
RE: intel hd?
by Peter on Monday August 27th 2018, 9:52
I'm using a Radeon RX 470 video card. DXVK 0.70, kernel 4.19-rc1, Mesa 18.2.0-rc4, LLVM 7.0.0-rc2, KDE Plasma. Different hardware and software entirely, except for WoW and DXVK.

I play at 3840x2160 on that RX 470, so I often see frame rates under 60. The good frame rate + poor 'feel' thing is what I've been investigating this evening. Came here to see if anyone else noticed something similar.
RE: intel hd?
by Steve Ebey on Monday August 27th 2018, 11:34
Shown here is the command line I use to run the game:

env DXVK_HUD="fps" WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 nice -20 wine64 '/home/steve/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe'

My linux cmdline includes elevator=deadline in the grub so that I get faster hard drive access in WoW.

Hope this helps.
RE: intel hd?
by Elijah Rum on Monday August 27th 2018, 14:19
I managed to fix the stuff.
Had to turn off my system composer (which provides vertical sync) and enable vsync in game settings.
Works great!
Thanks to everybody!
RE: intel hd?
by Peter on Monday September 3rd 2018, 9:28
The vsync changes in DXVK 0.71 seem to have fixed this for me, so long as I turn on vsync or the built in frame rate limiter to keep WoW from going over 60 FPS.
Error WOW51900322
by Oscar Tango on Thursday August 23rd 2018, 5:17
Yes, this is about the "Streaming Error" disconnects, but since the original comment on that is fourteen replies deep (at this time), it seemed prudent to start fresh.
As a reminder - this error has been popping up since the 7.3 patch. There is a github repo with a "clean" Windows-version Cache-file set
github.com/1thumbbmcc/wowcache.git
There's a forum thread here at WineHQ about the error:
forum.winehq.org/viewtopic.php?f=8&t=30803s
and there are existing forum threads on both EU and US official WoW forums:
eu.battle.net/forums/en/wow/topic/17620271965
eu.battle.net/forums/en/wow/topic/17620282020
us.battle.net/forums/en/wow/topic/20765466460
As far as we can tell - some (not all) characters generate unusable/unstable files in the Cache folder when playing under Wine on Linux that result in the error/disconnect. Some players have reported being able to play normally after just adding the Windows-version Cache files (without first clearing the folder) but since 8.0 that hasn't been the case for me - the error and disconnects persist unless I delete ALL existing files in my Cache prior to extracting the .zip contents into the folder. Also, subsequent clearing of the Cache folder (because of conflicts with other patches/addons etc) has required once again reloading the Windows-version Cache files or the error and disconnects resume. This is just a workaround - the bug is obviously not fixed, but it does allow you to resume play without the disconnects. Until Blizzard corrects the actual file-creation problem I'll try to pop in here more frequently to update and respond.
RE: Error WOW51900322
by Steve Ebey on Tuesday August 28th 2018, 22:08
Thank you for this information, I am adding a separate HOW TO for this issue, so it is available to all who encounter this problem.

by schmock on Tuesday August 21st 2018, 10:40
^I'm on nixOS, but iirc I've had this on Arch aswell.
A 64-bit operating system is required to install and play World of Warcraft
by schmock on Tuesday August 21st 2018, 9:45
I'm getting the above error when trying to install WoW from the Battle.net launcher.

- Clean Wineprefix, no 32bit specified, so should be 64bit!
- winetricks corefonts vcrun2017
- winecfg: windows 10, dll overrides: msvcp140 vcruntime140

Anyone got an idea on how to fix this?

Greetings
RE: A 64-bit operating system is required to install and play World of Warcraft
by Björn Bidar on Tuesday August 21st 2018, 11:48
tried export WINEARCH=win64 before?. BTW vcrun2017 and corefonts are not needed.
RE: A 64-bit operating system is required to install and play World of Warcraft
by Josh R Raymond on Tuesday September 4th 2018, 1:47
With a fresh wine-prefix, either make sure you 'env WINEARCH=win64' before winetricks, or just open battle.net setup in a terminal with the command wine64 instead of just wine.

Corefonts *is* needed or text displayed on the bnet app will be fuzzy, askew or omitted in certain places.
DXVK and GeForce 560
by Mikkel Kromann on Sunday August 19th 2018, 14:09
Hi.

Perhaps someone here can confirm or reject my suspicion on my troubles with WoW and DXVK.

I have a an old GeForce 500 series GTX560 card (on Ubuntu 18.04 x64, with NVIDIA driver 390), and when I apply the DXVK I get "3D accelerator card not supported" when I launch WoW.
According to developer.nvidia.com/vulkan-driver this card and its driver does not support Vulkan.
Without completely understanding the link between Vulkan and DXVK, I suppose that I will never get DXVK running with my card, unless NVIDIA suddenly decides to have it Vulkan supported ...

Am I right or wrong in my suspicions?


thanks, Mikkel
PS: An interesting observation: Enabling only D3D10 from DXVK gives me a noticable performance increase.
Enabling anything else will lead to either strange artefacts related to lightning/particles or "3D acc. not supported".
RE: DXVK and GeForce 560
by Steve Ebey on Monday August 20th 2018, 12:02
if you can not use vulkan with your video driver, then dxvk is pointless. I would follow the how to here, and build the pba version of wine, since it patches the files, you will not need vulkan, or any dxvk variables to run the game, and still see decent performance.
wine-staging + VXDK - current issues
by Peter on Sunday August 12th 2018, 1:54
I've been using wine-staging 3.13 with DXVK 0.64 on archlinux for a couple of weeks and these are my current issues.

For reference, this is my setup:
OS: ArchLinux
Wine: Staging 3.13
DXVK: 0.64 (latest version available in AUR)
Graphics: GeForce GTX 1060 6GB
Drivers: Nvidia 396.45-7
RAM: 16GB RAM
Disc: SSD
Average FPS: 70 - 100

Issue #1: Mass FPS drops in certain zones of the game after "certain" conditions.
Details: I've noticed that these happen in places with special effects like fog/smoke, pillars of light and/or other kinds of graphics. A good example is when you kill sindragosa (ice crown citadel raid).

Issue #2: Unclickable items in the bags/chat.
Details: Sometimes this happens and I'm unable to click any item in the bag and chat. Actions mapped in the "action bars" work properly. I can't find out the pattern because it seems to happen randomly. A wow restart solves the issue.

Issue #3: 1-5 FPS in 40vs40 PvP (Tarren Mill Brawl)
Details: Currently this feature of the game is unplayable for me. I don't know how many FPS I would get playing on windows but my graphics card should be able to provide a bit more FPS than it currently does. I've even decreased the graphics to "1" for raid settings and nothing changed.
RE: wine-staging + VXDK - current issues
by Alberto on Sunday August 12th 2018, 3:58
For DXVK 0.64 install the 396.51 driver of Nvidia. Is recommended in the readme at DXVK github.

In Siege of Lordaeron (similar to Tarren Mill Brawl) I have 35-40 fps with GTX 1070 and graphics settings in game in "7" with some fields changed for me to up.
gentoo wine-staging and VXDK
by Chris on Saturday August 11th 2018, 16:37
Hi,

I use gentoo, and I don't understand what to do to use DXVK. So I have very poor FPS with wow.( 5-15).

I've installed lastest app-emulation/wine-staging-3.13-r1 with USE :
vulkan : Enable Vulkan drivers
and not with (should I ?) :
vkd3d : Use app-emulation/vkd3d to provide Direct3D 12 support

I start wow with :
export DXVK_FAKE_DX10_SUPPORT=1
export DXVK_HUD=1

But it doesn't change anything.
RE: gentoo wine-staging and VXDK
by Steve Ebey on Saturday August 11th 2018, 18:56
Step 1 - Download the latest release of dxvk. Link github.com/doitsujin/dxvk/releases and get the latest release zip file.
Step 2 - Extract the zip file.
Step 3 - Change to the dxvk x64 directory, you should see three files.
Step 4 - type env WINEPREFIX=~/.wine/yourprefix bash setup_dxvk.sh and hit the Enter key to run it. Should take 2 seconds.
Step 5 - env DXVK_HUD=fps,info DXVK_FAKE_DX10_SUPPORT=1 wine64 /your/path/to/wow.exe
Step 6 - Have mind blown by the fps you get in game, at or above windows fps even.

if you remove /yourprefix then it applies to your default prefix, and will be used by everything you run. If you want to use battle.net desktop app, you MUST run in a different prefix than what dxvk uses. or you can go to the dxvk/x64 directory and run env WINEPREFIX=~/.wine/yourprefix bash setup_dxvk.sh reset to remove the dxvk. Once you exit battle.net, rerun step 4 again, to turn it back on.

Hope this helps
RE: gentoo wine-staging and VXDK
by Chris on Saturday August 11th 2018, 21:22
Thanks for your answer, but what I don't understand is why have I to do this ? What does USE vulkan in gentoo wine-staging ebuild is used for ?
RE: gentoo wine-staging and VXDK
by Steve Ebey on Sunday August 12th 2018, 7:20
I do not know anything about gentoo. what is USE and why are you asking about ebuild? I compile wine myself, from source, so that i get the best results on my hardware. Upgrade your video driver to 396.51 and see if that helps.
Streaming error disconnect
by Are on Thursday August 9th 2018, 2:54
Has anyone else been having trouble with disconnects?
When I use certain addons or sometimes when i open UI elements like collection, communities and lfg tool i get disconnected with "A streaming error has occurred. (WOW5190022)
The help from blizz says this is due to firewall or antivirus. I use none of those.
Addons that make it crash for me are usually the ones who do big searches like auction house addons or transmog addons.
The addons i can do without, but getting disconnected randomly when i open UI elements is kinda annoying
RE: Streaming error disconnect
by evilny0 on Saturday August 11th 2018, 14:16
I have the same issue. Some addons completely prevent the game from loading (same kind of addons you mentionned), and some UI elements crash the game as soon as I open them (ex: skills panel). As a result, I can't play, since my bar addon changed for 8.0, and I can't place any skills in the default Blizzard bars since I can't open the UI...

The error I get is WOW51900322.
RE: Streaming error disconnect
by Björn Bidar on Saturday August 11th 2018, 14:39
Remove Addons.txt in WTF/$ACC/$SERVER/$CHAR to reset all enabled addons.
RE: Streaming error disconnect
by Are on Monday August 13th 2018, 5:37
I think his problem is that he can't even open spellbook because it disconnects him.

The problem persists even with reinstalling wow on a new prefix with 0 addons.
Addons only made it crash more often.
100% vanilla install still crashes randomly when i open UI elements
If i add a addon like allTheThings or Can I mog it? the game disconnects 1-2 seconds after logging into a character
If i use 0 addons it crashes sometimes when i open ui elements like lfg tool, talents, collections or communities

I tried running the game for a few hours not opening a single UI element and it never crashed, then i opened communities and instant d/c with streaming error
RE: Streaming error disconnect
by evilny0 on Monday August 13th 2018, 6:42
Ah, I wanted to try to reinstall in a new prefix... but if that doesn't change anything I won't try.

And yes, I could not open the spellbook, even with no addons enabled. It's kind of random though, because I finally managed to open it. I was able to fill Neutron bars with spells after enabling the addon. I tried to play with only a few addons enabled (Neutron, SUF, Prat, OmniCC), and as long as there is no loading screen, I don't get streaming errors. Most loading screens will trigger the streaming error though... doing war of thorns chapter 2 to get the mount was a pain, I got disconnected something like 20 times -_-

If I remember correctly, the "guild" UI is causing d/c also. When you say communities, I suppose that's the new name (I did not play for a long while) ? I noticed the UI was different before being disconnected.
RE: Streaming error disconnect
by Are on Tuesday August 14th 2018, 4:32
So here is what i've done that now seems to be working (so far at least)
1. i deleted my wow folder
2. i downloaded a clean copy from battle.net
3. i made a new prefix
4. i copied the new wow folder only to the new prefix
5. i launched wow via terminal

0 addons or changes on the prefix
This makes the game have some graphical glitches, but it doesn't disconnect me so far
Atleast from the past 2 hours i've played the bfa intro
RE: Streaming error disconnect
by evilny0 on Tuesday August 14th 2018, 4:50
If I understand right :

- You removed wow, but not bnet app
- You installed wow again, in the same prefix
- You copied the wow folder to a new prefix
- You start wow.exe directly in the new prefix

Which wine version are you running on the new prefix ?
RE: Streaming error disconnect
by Are on Tuesday August 14th 2018, 5:43
Yes that's correct
wine-3.13 (Staging)
RE: Streaming error disconnect
by Steve Ebey on Tuesday August 14th 2018, 7:41
What speed is your internet connection? Upload and Download speed please.
RE: Streaming error disconnect
by Are on Tuesday August 14th 2018, 8:17
Using testmy.net with 50 mb of data:
Download: 3.9 MB/s
Upload: 1.9 MB/s
RE: Streaming error disconnect
by Steve Ebey on Tuesday August 14th 2018, 11:02
you might consider testing with a different streamer, such as obs, to see if that helps. 1.9Mbps is a fairly low speed, so the stream may be taking all the bandwidth from wow and causing the realm server to think you are gone.
RE: Streaming error disconnect
by Are on Tuesday August 14th 2018, 14:17
This problem has nothing to do with livestreaming
RE: Streaming error disconnect
by Steve Ebey on Tuesday August 14th 2018, 15:35
ok, just thought since the subject said Streaming error disconnect, that it was caused by a Streaming error. What is the source of the error then, or are you just having bad luck with the game running in general?
RE: Streaming error disconnect
by evilny0 on Tuesday August 14th 2018, 18:48
We get disconnected from the game, and the error popup is "A streaming error has occurred. (WOW51900322)" (or something close). Blizzard help says this happens when the client can't access data, for example a firewall could be blocking the request.

We have no idea why it happens, although it seems to happen less without any addons. In my case, even without addons, it still happens from time to time when opening certain UI elements, or after a loading screen. I still need to try reinstalling the game in a clean prefix.
RE: Streaming error disconnect
by Björn Bidar on Tuesday August 14th 2018, 18:53
just mv the game no reinstall needed.,
RE: Streaming error disconnect
by Brian on Wednesday August 15th 2018, 15:34
I get it too, constantly. I've tried everything in this thread without any luck. I made it to "Magni's Encampment", where Magni Bronzebeard has a quest available, and every time I click him I get the error and disconnect. I can't really think of any more things to try, but I hope someone comes up with a solution.
RE: Streaming error disconnect
by Are on Thursday August 16th 2018, 5:13
Does it crash after you got the heart and try to accept the followup quest?
That's where it crashed every time for me so I just tried everything i could think of

Side note:
Do you have dxvk or any environment variables turned on in the prefix you tried a new install on?
RE: Streaming error disconnect (fixed for me)
by Brian on Thursday August 16th 2018, 14:00
Yes, that exactly where it crashes.
I do not have dxvk turned on, as it does not (as far as I know) work with Bumblebee/primusrun, which I use.

However, I stumbled upon a thread, from a couple of months ago, on the WoW forums which seems to have fixed it for me:

- I got a windows Cache directory from github.com/1thumbbmcc/wowcache ,
- Replaced my current Cache directory with that one.

Links:
us.battle.net/forums/en/wow/topic/20765466460?page=3
www.youtube.com/watch?v=hT4uxwHOdZM
RE: Streaming error disconnect (fixed for me)
by Steve Ebey on Thursday August 16th 2018, 15:01
DXVK will NOT cause issues, and it WILL give you much better performance. Anything that renders, does so through your driver, and as long as vulkan is installed, you will be fine.
RE: Streaming error disconnect (fixed for me)
by Brian on Thursday August 16th 2018, 17:03
My FPS have in fact been terrible since the expansion, so if you say DXVK should work, I'll give it another try.

The problem I was having with DXVK was that WOW (when trying to launch) would complain about the 3D/Graphics Accelerator not being supported, and that I should consult the system requirements for Wow. I don't have the exact error message at the moment though.

Also I found this, which made me believe that it had something to do with the fact that I'm using primusrun: github.com/Bumblebee-Project/Bumblebee/issues/769

If you have any suggestions please let me know.
RE: Streaming error disconnect (fixed for me)
by Steve Ebey on Thursday August 16th 2018, 17:46
since the developers of bumblebee choose to ignore vulkan, then you only have one choice, follow the how to, compile a pba copy of wine staging, and get decent fps in game. My how to note shown here should be complete, but read it first, and make sure you follow all the steps. Read it twice, just to make sure you get a good compile, then I am confident that you will be able to use wine, with no external files required, and even run the battle net launcher, to keep the game updated. If you have any problem running wow from wine at the command line, ask me, and I can make a shell script for you to use. do not use the battle net app to actually launch the game, as that will not give decent performance. just use it to keep your copy of wow updated.
RE: Streaming error disconnect (fixed for me)
by Brian on Friday August 17th 2018, 16:23
Thanks, that actually helped a lot.. Went from 20-40 FPS to 30-60 FPS.
RE: Streaming error disconnect (fixed for me)
by Steve Ebey on Friday August 17th 2018, 22:24
here is the complete command line I use in my script to start wow with.

env WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 nice -20 wine64 '/home/[username]/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe'

That single line runs wow from command line, and I can run until i get tired of playing, and have not touched windows 10 to run wow in almost 2 years now.
RE: Streaming error disconnect (fixed for me)
by Björn Bidar on Saturday August 18th 2018, 1:06
Me too playing wow on linux only since mop.
My script is similar except staging rt and more sogar to start the launcher and delete the cache every time I start wow:


APPNAME="World of Warcraft"
APPPATH='/home/bidar/.local/share/wineprefixes/wow64/drive_c/Program Files/World of Warcraft'
commands_s=( g l h e )
commands_l=( game launcher help end )
exe=( game launcher display_help kill_game )
_game=Wow.exe
_launcher="World of Warcraft Launcher.exe"
PREFIX=/home/bidar/.local/share/wineprefixes/wow64_dxvk
default_exe=$exe
#WINEPATH=$HOME/.wine-ver/wine_h.3.27
#_wine_args="explorer /desktop=Wow,3840x2160"
HELP_MSG="options: -g --game start $APPNAME
-l --launcher start $APPNAME launcher
-h --help print this help
-e --end $APPNAME"

# enable __GL_THREADED_OPTIMIZATION
export __GL_THREADED_OPTIMIZATION=1
export STAGING_WRITECOPY=1
export STAGING_RT_PRIORITY_SERVER=90
export __GL_SYNC_TO_VBLANK=0
#export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export STAGING_SHARED_MEMORY=1
#WDEBUG=+tid,seh,d3d9,d3d,d3d_shader
WDEBUG=fixme+all,err+all,fixme-win
WINE=wine64
LIBUSEAPP_LVL=2

game() {
WINE=wine64
rm -rf "Cache"
wine_args="$_wine_args" exec_exe $_game -d3d11
}

launcher()
{
rm -rf "Cache"
exec_exe "$_launcher"
}


kill_game()
{
pkill $_game
}
. /usr/lib/libuse/libuse
RE: Streaming error disconnect (fixed for me)
by Cody Rude on Thursday August 16th 2018, 15:45
This worked for me, thanks!
DXVK and CPU Performance
by el Arm on Thursday August 9th 2018, 0:02
Have finally got DXVK working and the difference is night and day for me. In 7.3 my CPU was always 100%, indicating a single core. In 8.0 it's been 200% suggesting WoW is now properly using two cores, but the feel, where it showed some of the following problems before, has degraded badly;
- jerkiness when turning corners making it hard to navigate at speed through doorways
- cannot clear keyboard buffer fast enough, so moving forward with W, will continue to move for seconds after you release
- framerate in Bloodymyst Isles 10-25 fps

After DXVK the CPU has dropped to a consistent 135%, the framerate in Bloodmyst 85-100 (capped) and it feels as smooth as glass! I'd decided to switch to Windows when BfA opened so this is a lifesaver, it feels like a whole new game.

If it helps anyone, my situtation;
Older AMD card (R9 280X, which is GCN 1.0 or Sea Island "si")
Ubuntu 16.04 (fully updated to 16.04.5)

Ubuntu LTS versions stick to the original installed kernel version (in this case 4.4) even though installing a direct 16.04.5 ISO will give a later kernel. Ubuntu kernel 4.4 does not contain the amdgpu driver (this supports Vulkan), only the radeon driver (which does not support Vulkan). To fix;
1. Install packages
linux-generic-hwe-16.04 (you will get the latest kernels, currently 4.15 which includes amdgpu)
xserver-xorg-hwe-16.04
2. Edit /etc/grub/default and add the following to GRUB_CMDLINE_LINUX_DEFAULT
radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1
or you can manually add them in the grub boot screen as a temporary test
3. Reboot, check amdgpu is in use
lspci -k | grep -A3 VGA
4. Check Vulkan is available
vulkan-smoketest
5. Install DXVK dlls into your wine prefix using the usual steps
Unable to install WoW, Battle.net complaining not using 64bit OS
by Aaron on Sunday August 5th 2018, 21:22
It's been awhile since I've installed World of Warcraft on Linux. I created a new 64bit wine prefix and installed the battle.net app. However, the battle.net app is complaining I'm not using a 64bit OS when I try to install WoW. I've verified multiple times that I have 32bit and 64 bit wine installed. I'm running Ubuntu 18.04 and have installed wine staging 3.13 from the repo here. Any help would be greatly appreciated.
RE: Unable to install WoW, Battle.net complaining not using 64bit OS
by Aaron on Tuesday August 7th 2018, 23:46
I copied over my install from Windows and that works.
RE: Unable to install WoW, Battle.net complaining not using 64bit OS
by el Arm on Wednesday August 8th 2018, 2:16
Not 100% certain it matters, but are you starting using the wine64 executable (i.e. /usr/bin/wine64) rather than wine?

I can't remember the last install I did either, on the odd occasion a WoW update breaks the launcher on wine I update on Windows and copy across.
RE: Unable to install WoW, Battle.net complaining not using 64bit OS
by Aaron on Wednesday August 8th 2018, 12:59
Yep was using the wine64 binary.

by Alberto on Wednesday August 1st 2018, 12:44
Steaps for install DXVK and play World of Warcraft (I do today)

0. My specs
openSUSE Leap 15
KDE Plasma 5.13.3
kernel 4.17.11
Nvidia GTX 1070 with propietary driver 396.45
wine-staging 3.13

1. Dependencies

Meson 0.43+
Ninja 1.8.2+
Glglang-devel 3.0+
Mingw32
Mingw64
Git

All necessary files of mingw32 and mingw64:

i+ | mingw32-binutils | GNU Binutils | paquete
i+ | mingw32-cpp | MinGW Windows C Preprocessor | paquete
i+ | mingw32-cross-binutils | GNU Binutils | paquete
i | mingw32-cross-breakpad-tools | An open-source multi-platform crash reporting system | paquete
i+ | mingw32-cross-cpp | MinGW Windows cross-C Preprocessor | paquete
i+ | mingw32-cross-gcc | MinGW Windows cross-compiler (GCC) for C | paquete
i+ | mingw32-cross-gcc-c++ | MinGW Windows cross-compiler for C++ | paquete
i | mingw32-filesystem | MinGW base filesystem and environment | paquete
i+ | mingw32-gcc | MinGW Windows compiler (GCC) for C | paquete
i+ | mingw32-gcc-c++ | MinGW Windows compiler for C++ | paquete
i | mingw32-headers | MinGW-w64 headers for Win32 and Win64 | paquete
i | mingw32-libgcc_s_sjlj1 | MinGW Windows compiler for C shared libraries | paquete
i | mingw32-libgmp10 | The GNU MP Library | paquete
i | mingw32-libmpc3 | MPC multiple-precision complex library | paquete
i | mingw32-libmpfr4 | MPFR multiple-precision floating-point computation shared library | paquete
i | mingw32-libwinpthread1 | A pthreads implementation for Windows | paquete
i | mingw32-runtime | MinGW-w64 runtime libraries for Win32 | paquete
i | mingw32-winpthreads-devel | Development files for mingw32-winpthreads | paquete
i | mingw32-zlib1 | Zlib compression library | paquete
i+ | mingw64-binutils | GNU Binutils | paquete
i+ | mingw64-cpp | MinGW Windows C Preprocessor | paquete
i+ | mingw64-cross-binutils | GNU Binutils | paquete
i | mingw64-cross-breakpad-tools | An open-source multi-platform crash reporting system | paquete
i+ | mingw64-cross-cpp | MinGW Windows cross-C Preprocessor | paquete
i+ | mingw64-cross-gcc | MinGW Windows cross-compiler (GCC) for C | paquete
i+ | mingw64-cross-gcc-c++ | MinGW Windows cross-compiler for C++ | paquete
i | mingw64-filesystem | MinGW base filesystem and environment | paquete
i+ | mingw64-gcc | MinGW Windows compiler (GCC) for C | paquete
i+ | mingw64-gcc-c++ | MinGW Windows compiler for C++ | paquete
i | mingw64-headers | MinGW-w64 headers for Win32 and Win64 | paquete
i | mingw64-libgcc_s_seh1 | MinGW Windows compiler for C shared libraries | paquete
i | mingw64-libgmp10 | The GNU MP Library | paquete
i | mingw64-libmpc3 | MPC multiple-precision complex library | paquete
i | mingw64-libmpfr4 | MPFR multiple-precision floating-point computation shared library | paquete
i | mingw64-libwinpthread1 | A pthreads implementation for Windows | paquete
i | mingw64-runtime | MinGW-w64 runtime libraries for Win64 | paquete
i | mingw64-winpthreads-devel | Development files for mingw64-winpthreads | paquete
i | mingw64-zlib1 | Zlib compression library | paquete


2. Installation (build in 64bits with 64bit wineprefix)

cd ~
WINEPREFIX=/home/-youruserdir-/.winedxvk winecfg
git clone github.com/doitsujin/dxvk.git
cd dxvk
WINEPREFIX=/home/-youruserdir-/.winedxvk meson --cross-file build-win64.txt --prefix /home/-youruserdir-/dxvk build.w64
cd build.w64
meson configure -Dbuildtype=release
ninja
ninja install
cd ../bin
WINEPREFIX=/home/-youruserdir-/.winedxvk bash setup_dxvk.sh


3. Play WoW

env DXVK_HUD=devinfo,fps DXVK_FAKE_DX10_SUPPORT=1 WINEDEBUG=-all WINEPREFIX=/home/-youruserdir-/.winedxvk wine64 "/home/-youruserdir-/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe"

If you don't want the HUD in upper left of the screen, remove DXVK_HUD=devinfo,fps from the line above.


4. Captures from my WoW (without and with DXVK)

Before:

i.imgur.com/kjIfH8H.png

i.imgur.com/oAJlhZs.png

After (with DXVK):

i.imgur.com/hBBg1vj.png

i.imgur.com/ejSh50j.png


5 Enjoy!
RE: Installation of dvxk
by Steve Ebey on Wednesday August 1st 2018, 17:56
Are the steps shown in your comment, after compiling, both 32 and 64 bit wine, like I have, so that people can use battle.net desktop application?

in the second picture of each set, you are in a dark area, so the fps are higher than when in populated areas. Where is the character at in the game, in the second picture of each screenshot you provided?
RE: Installation of dvxk
by Alberto on Wednesday August 1st 2018, 18:23
Is compiled for only 64bit.

To have 32bit you need to fo:
Making WINEPREFIX you can add WINEARCH=win32.
Change in line of the first meson 64bit for 32bit
And cd to build.w32 to do meson configure, ninja, etc.

But I can start both programs in 64bit build only.

First I do (with DXVK env):

env DXVK_HUD=devinfo,fps DXVK_FAKE_DX10_SUPPORT=1 WINEDEBUG=-all WINEPREFIX=/home/krovikan/.winedxvk wine64 "/home/krovikan/.wine/drive_c/Program Files (x86)/World of Warcraft/Wow.exe"

And second, to have Battle.net, I do (with normal WINEPREFIX):

__GL_THREADED_OPTIMIZATIONS=0 __GL_YIELD=NOTHING wine64 '/mnt/juegos/wine/drive_c/Program Files (x86)/Battle.net/Battle.net.exe'

I can have the two programs at the same time without penalties in fps in WoW.


The pictures number 1 (with and without DXVK) are in Dalaran, the most populated city. Try with a lot of render.

Without DXVK 18fps. With DXVK 58fps.

The pictures number 2 (with and without DXVK) are outside Dalaran (looking to Sargeras Tomb and a bit of Suramar). Try with a bit of render.

Without DXVK 22fps. With DXVK 121fps.

In Dark Shore (at Kalimdor and in the middle of a forest) with out DXVK runs at 33fps. With DXVK runs at 120fps.
RE: Installation of dvxk
by Steve Ebey on Wednesday August 1st 2018, 18:43
Would you screenshot your graphics settings from the system menu in game? Are you running DX12 when you are using DXVK?
RE: Installation of dvxk
by Alberto on Thursday August 2nd 2018, 5:51
This night (in 10h aprox) I'll take the screenshots of graphics settings.

In advance, in the API selector of the game I have only DX11 as option.
RE: Installation of dvxk
by Alberto on Thursday August 2nd 2018, 14:18
RE: Installation of dvxk
by Steve Ebey on Friday August 3rd 2018, 18:49
Tested DXVK and PBA. AMD FX 6300 6 core, 3.6Ghz, 16GB Ram, GTX 970 4Gig Ram, Fedora 28, kernel 4.16.15, Nvidia Proprietary 396.45.

DXVK - Dalaran, Nightborne Warrior, on her dragon - imgur.com/lWW6qqk

PBA - Dalaran, Nightborne Warrior, on her dragon - imgur.com/lWW6qqk

On second image, look in lower right corner, to see the fps. They are basically identical, so I will continue with PBA for now, until the Vulkan driver from nvidia shows more improvement.
Correction for PBA picture
by Steve Ebey on Friday August 3rd 2018, 18:53
PBA - Dalaran, Nightborne Warrior, on her dragon - imgur.com/qlBH6vV
RE: Installation of dvxk
by Alberto on Saturday August 4th 2018, 18:46
I don't put my specs. There they go:

Tested only DXVK version 0.63 in test submitted (now I have 0.64 with same results). Intel i5 6600K 4 core, 3,5Ghz, 32Gb RAM, GTX 1070 Strix 8GB VRAM, openSUSE Leap 15, kernel 4.17.12, Nvidia Propietary 396.45 in test submmited (now I have 396.51 with same results).
DXVK
by Alberto on Wednesday August 1st 2018, 4:29
Is not better a how to of DXVK instead PBA? (or together).

Seems that DXVK is better than PBA.
RE: DXVK
by Steve Ebey on Wednesday August 1st 2018, 7:01
My system based on Nvidia card, has lower vkmark scores, because nvidia has not made vulkan a priority in the drivers they use. They are getting better, but I still have to use immediate mode, instead of the default mailbox system that the vulkan drivers use. glmark2 with nvidia is over 1000 points higher on the test scores. If you want to do a how to for simple dxvk integration, then post in the comments, and I will be glad to create it for you.
Mouse Capture on Camera Spin
by Lennon on Saturday July 28th 2018, 12:32
This is my first post, so I apolgize if I'm not following protocol. I didn't see anything about how to contribute to these comment sections.

When I hold down right click to turn, my cursor is not being captured and reset to the center. Due to this, if my is towards the edge of my screen, the camera rotates wildly, whereas the center of the screen is more reasonable. My cursor is also not locked where it is right clicked at, so I can slowly move my mouse towards the edge of the screen, and as the game detects movement, my turning becomes faster and faster as my cursor is going to the edge of the screen.

I played around some and interestingly, opening the game directly gives me vastly different behaviour than through the launcher. The launcher behaviour is listed above, but directly calling the application I do not have the described cursor issues, but I do have a lot of artifacting and some input delay.

wine_version: wine 3.13 staging
os: fedora 28
gpu: Radeon R7 270X
drivers: Unknown
cpu: AMD R7 1700X
RE: Mouse Capture on Camera Spin
by Lennon on Monday August 6th 2018, 21:56
fixed today.
wow keeps telling me it cant start 3d acceleration
by johnbl on Saturday July 21st 2018, 21:32
tried wine 3.12, now using 3.13 this comes up in output

warn: DXGI: CheckInterfaceSupport: No D3D10 support
err: DXGI: CheckInterfaceSupport: Unsupported interface
err: 9b7e4c0f-342c-4106-a19f-4f2704f689f0
0176:fixme:d3d9:D3DPERF_SetOptions (0x1) : stub

and to answer other things

info: Game: Wow.exe
info: DXVK: v0.62
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 1050 Ti:
info: Driver: 396.24.10
info: Vulkan: 1.1.80

im used to problems with new patches, etc but i just got this going on my wifes pc, exactly the same setup as mine.
any help appreciated
RE: wow keeps telling me it cant start 3d acceleration
by Iridias on Sunday July 22nd 2018, 3:46
Looks like you're using DXVK without exporting the env-variable DXVK_FAKE_DX10_SUPPORT=1
You need to do that!
RE: wow keeps telling me it cant start 3d acceleration
by johnbl on Sunday July 22nd 2018, 9:22
dont wanna sound like a 'nix noob (i've been using linux for over 10yrs... there aint any clear descriptions on how to set
- DXVK_FAKE_DX10_SUPPORT=1
i found some instructions saying to
sudo -H gedit /etc/environment
then put what where???
any help appreciated!
RE: wow keeps telling me it cant start 3d acceleration
by Daylene Alford on Thursday July 26th 2018, 16:47
In Ubuntu

sudo gedit /etc/environment
Add DXVK_FAKE_DX10_SUPPORT=1 on a new line and save

Restart your computer or at least log out and back in.

You can check that it has been applied by typing printenv in a terminal.
RE: wow keeps telling me it cant start 3d acceleration
by Björn Bidar on Thursday July 26th 2018, 19:02
that can break other programs beter set it somwhere else like start script.
Removing/renaming d3d11.dll and dxgi.dll solves my rendering problems
by Are on Saturday July 21st 2018, 5:16
I have a to old gpu to use dxvk so i tried just renaming both the dll's with a .old suffix and so far it has removed all my green waters.
Most models are a light purple/pink glow until the textures loads in.
Particle effects don't work well. They show up as squares in different colours
Worth a try if your game is really broken and you can't use dxvk
Black screen at launch
by Foulques on Friday July 20th 2018, 4:13
Hello guys,

Config :
- wine 3.12 staging
- DXVK
- NVIDIA 396.24.10

Most of the time I cannot launch the game. Battle.net seems to work fine, but launching the game seems to be really random. One a the following "action" can happen :
- A popup message saying that there is no 3d acceleration (the game is not launching)
- Games launch but the screen is transparent/black with sound working
- Games launch and I can play without issue

Any idea how to fix those problems ?
RE: Black screen at launch
by Foulques on Friday July 20th 2018, 7:27
Fixed it myself.

For some reason "DXVK_FAKE_DX10_SUPPORT=1" was not correctly set. Launching the game directly, not from the launcher, seems to work flawlessly.
You have been disconnected BLZ51901016
by hereuspam on Friday July 20th 2018, 4:10
I keep getting this error, i tried the clean cache which is linked in the 7.3 section but no use, any solution for this?

I have tried deleting and downloading a fresh copy too. Any tips?
Extra terminal output
by ergo on Friday July 20th 2018, 3:52
Does anyone else see similar spam despite using WINEDEBUG=-all ?

D 08:39:25.001943 [blink] |connection=rpc|event=on_read_frame|length=12 (d:\buildserver\wow\7\work\shared-checkout\branches\wow-patch-8_0_1-branch-fastpatch-25\engine\source\wowvoice\wowvoiceproxy\src\voiceconnection.cpp:55)
D 08:39:32.004075 [blink] |connection=rpc|event=on_read_frame|length=12 (d:\buildserver\wow\7\work\shared-checkout\branches\wow-patch-8_0_1-branch-fastpatch-25\engine\source\wowvoice\wowvoiceproxy\src\voiceconnection.cpp:55)
...
Graphical Artifacts
by Steve Ebey on Thursday July 19th 2018, 8:27
Went into the system, advanced menu in game, set the graphics card to match my installed card. Rendering worked fine from that point forward.

Running self compiled wine-3.12-187-gd265dd88cd (Staging) with the acomminos pba patches. Compiled on Fedora 28, GTx 970, 16Gig ram, 6 core AMD fx 6300
RE: Graphical Artifacts
by Tim Ryan on Thursday July 19th 2018, 12:18
That seemed to help, but as soon as I took a flight and entered Azuna everything went bad again. Water and ground clutter turned bright blue and boxes around light sources. I'm using wine-pba-firerat-3.11-x86_64 from the lutris site.
RE: Graphical Artifacts
by Björn Bidar on Thursday July 19th 2018, 12:58
1st please use the reply button.
2nd:
just do
/run RestartGx();
ingame and you are fine until the bug gets triggred.
RE: Graphical Artifacts
by Tim Ryan on Thursday July 19th 2018, 13:16
I did use the Reply button. That's why it's indented and the RE:

Thanks. I'll try that next time I play.
RE: Graphical Artifacts
by Tim Ryan on Thursday July 19th 2018, 15:01
That did not help. It's weird sometime when I get in game it looks fine, other times everything is messed up, with many textures being the same solid color, mainly water, but also ground clutter and other seemingly random ones. Doing the /run RestartGx(); doesn't help. I'm using an old nVidia 570.
RE: Graphical Artifacts
by Steve Ebey on Thursday July 19th 2018, 16:23
I am running DX11 with acomminos pba, and wine 3.12 staging compiled on my system. I also compile with no debug, and do the complete shared build for both 32 and 64 bit, so I can run battlenet desktop app. used winetricks to install corefonts, and the battlenet app works better also. windows version in winecfg set to windows 10. Game set to fullscreen, by going into graphics, and hitting the recommended button. my registry also has xrandr=n and xvidmode=n in the X11 Driver registry key. When I compile my configure flags include --without-gtk3 and --with-x. Hope this helps people track down the issue. I logged to windows 10 and the problem was also there, so I wonder if it comes from blizzard, or DX12?
Plain wine rendering
by Chiro on Thursday July 19th 2018, 2:40
If wine on its own without DXVK or similiar projects produces errors, is there a log and a bug report?
Issues with DXVK
by Iridias on Wednesday July 18th 2018, 15:19
Update (it seems I can't edit the test-results):

After some more testing/playing around I found the following:
* hardware cursor seems to be gone / no longer supported (at least there is no checkbox in the preferences anymore)
* DXVK gives ~ twice the FPS but results in weird stuttering besides high FPS (have not tested with a fresh wine-prefix though)
* removing the old .wine folder or using a fresh prefix as well as (a precaution) deleting the cache and WTF folder of Wow seems to fix the issues with the pink graphical artifacts.
RE: Issues with DXVK
by Iridias on Wednesday July 18th 2018, 15:33
Update 2:
OK, the pink artifacts are gone, but now I have other rendering glitches
RE: Issues with DXVK
by Catryna on Tuesday August 21st 2018, 21:54
Just did the latest update to Wine staging. Everything works perfectly. No glitches, no graphics problems. Didn't use DXVK. Just wine staging and the DLLs from winetricks.
Back