World Of Warcraft Legion
Following recent events in the Broken Isles, a link has been created between Azeroth and Kil'jaeden's homeworld of Argus, bringing the Burning Legion closer than ever to destroying Azeroth. In order to stop them once and for all, Illidan and Velen are taking the war directly to the surface of Argus, where they hope to join forces with Alleria, Turalyon, and the Army of the Light to launch an all-out assault on the Legion's primary base of operations.
Application Details:
| Version: | 7.3 |
| License: | Retail |
| URL: | http://www.worldofwarcraft.com |
| Votes: | Marked as obsolete |
| Latest Rating: | Gold |
| Latest Wine Version Tested: | 3.11-staging |
Maintainers: About Maintainership
What works
Works out of box in default 64-bit PREFIX, I set my Windows version to Windows 10.
Gameplay elements:
Login
Character creation
Questing
Farming
Raids (uncluding LFR)
PvP (World, Battleground and Arena)
Dungeons (including Mythic+)
Pet Battles
Blizzard Shop
Battle.net chat functionality
Addons
Architectural elements:
64-bit
d3d11
Various graphical settings work without issues
SSAA, FXAA
What does not
Workarounds
Do not use MSAA or CMAA...
What was not tested
Voice chat
Streaming
OpenGL (no longer supported)
32-bit
Hardware tested
Graphics:
Additional Comments
AMD FX-8350 Black Edition
16GB RAM
Sabertooth 990FX r1
Nvidia Geforce 1050 Ti
Kernel: 4.9.87-antix.1-amd64-smp GNU/Linux
Nvidia 396.24
DE: Xfce 4.12.2
| Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
| Show | Fedora 28 x86_64 | Jul 08 2018 | 3.11-staging | Yes | Yes | Yes | Gold | Sean Rhone (Espionage724) | |
| Current | antiX-17 "Heather Heyer" Core | May 28 2018 | 3.9-staging | Yes | Yes | Yes | Gold | spaceman | |
| Show | antiX-17 "Heather Heyer" Core | Mar 08 2018 | 3.3 | Yes | Yes | Yes | Gold | spaceman | |
| Show | Arch Linux x86_64 | Jan 18 2018 | 3.0-staging | Yes | Yes | Yes | Gold | d3rrial | |
| Show | KDE Neon 5.11.4 | Jan 05 2018 | 2.21-staging | Yes | Yes | Yes | Gold | Jay Greenfield |
| Bug # | Description | Status | Resolution | Other apps affected |
| 11674 | Dual-core unsupported in WoW and SC2 | STAGED | View | |
| 29168 | Multiple games and applications need realtime updates to KSYSTEM_TIME members in KUSER_SHARED_DATA (Star Wars: The Old Republic game client, Blizzard games, GO 1.4+ runtime) | STAGED | View | |
| 35461 | Synergy server causes mouseover events to fail in World of Warcraft | NEW | View | |
| 37942 | World of Warcraft (7.x.x) hangs: 100% CPU usage | UNCONFIRMED | View | |
| 41167 | HLSL shader parsing failed | REOPENED | View | |
| 42065 | WOW 7.1 spams fixme:d3d_draw:draw_primitive_arrays Start instance (VALUE) not supported. | UNCONFIRMED | View | |
| 42805 | World of Warcrafft 64 bit client freezes or glitches after some time | UNCONFIRMED | View | |
| 43417 | World of Warcraft leaks memory in both 64 and 32 bit modes. | UNCONFIRMED | View | |
| 43768 | WOW crash game | UNCONFIRMED | View | |
| 43857 | WoW PTR 7.3.2 crashes on startup | UNCONFIRMED | View | |
| 44650 | Multiple Blizzard games need dxgi and d3d11 dlls mapped without hole between two LOAD segments (Diablo III v2. 6. 1. 49286+, World of Warcraft, Overwatch) | STAGED | View | |
| 45101 | Mouse cursor not displaying correctly in Hearthstone | UNCONFIRMED | View | |
| 45349 | Multiple applications and games crash due to missing support for 64-bit syscall thunks (StreetFighter V, World of Warcraft) | STAGED | View |
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-dirs
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
export LD_LIBRARY_PATH=/usr/local/lib
env VKD3D_DEBUG="none" WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 wine64 '/home/steve/.wine/drive_c/Program Files (x86)/World of Warcraft/_retail_/Wow.exe' -d3d12 &>/dev/null
winetricks win7
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.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Kevin Grittner on Tuesday November 13th 2018, 17:36
I have a screenshot, and will file a bug so I can post if if that will help.
by DeeDee Ranged on Saturday November 24th 2018, 7:33
Waiting for wine-staging 3.21 to see if it has been resolved.
by RecursiveProgrammer on Friday July 20th 2018, 18:02
1) My screen was incredibly choppy (even on the lowest settings). Things were substantially better after I used winetricks to install:
corefonts
ie8
( linuxconfig.org/how-to-play-world-of-warcraft-on-linux-with-wine )
I mention this to hopefully help remind myself if I have to re-install world of warcraft, at a later date. If someone can point me in the proper direction of how to install those two programs through wine, I can write a script and at least post it here in the comments.
2) I believe it might be useful to note, in the scripts provided on this page, to add a comment that you should run wine in 64 bit mode (it was not obvious to me and I ended up running wine and it made a 32-bit .wine container (which becomes a problem as blizzard phases out 32-bit)). (The scripts are in BASH, as I am sure I am using some Bash specific scripting...maybe...)
The script I run to install the blizzard client is (hopefully, this gets executed only once):
export WINEARCH=win64
mywinedirectory="/home/username/wine-dirs/wine32-build/"
myclientdownload="/home/username/Downloads/World-of-Warcraft-Setup.exe"
${mywinedirectory}/wine "${myclientdownload}"
The script I run to run world of warcraft is (which, if all works well, gets executed a lot...):
export WINEARCH=win64
mywinedirectory="/home/username/wine-dirs/wine32-build/"
mywowinstalldirectory="/home/username/.wine/drive_c/Program Files (x86)/World of Warcraft/"
${mywinedirectory}/wine "${mywowinstalldirectory}/Wow.exe"
by Romain "Artefact2" D. on Wednesday July 18th 2018, 6:39
I am having great success using dxvk (nvidia driver 396.24.10). Here is my full launch command:
`firejail --whitelist=~/.local/wine/wow2 --env=DXVK_FAKE_DX10_SUPPORT=1 --env=DXVK_HUD=1 --env=WINEPREFIX=$HOME/.local/wine/wow2 wine Wow.exe`
Here is a screenshot: framapic.org/Bo6Nhxs0VBmz/gej9O0mjWULu.jpg
by Iridias on Wednesday July 18th 2018, 7:47
I submitted a corresponding test-result for the new version: appdb.winehq.org/objectManager.php?sClass=version&iId=36961
by Steve Ebey on Tuesday July 10th 2018, 10:29
by Sean Rhone (Espionage724) on Saturday July 7th 2018, 3:48
by Steve Ebey on Saturday July 7th 2018, 7:07
by Sean Rhone (Espionage724) on Sunday July 8th 2018, 1:17
by Steve Ebey on Sunday July 8th 2018, 7:27
by Steve Ebey on Saturday June 30th 2018, 19:56
compilation terminated.
In file included from ../../../wine/dlls/xaudio2_7/xaudio_dll.c:26:
../../../wine/dlls/xaudio2_7/xaudio_private.h:33:10: fatal error: libavcodec/avcodec.h: No such file or directory
#include
anyone know why this is happening.
by Sean Rhone (Espionage724) on Saturday July 7th 2018, 3:52
by Oscar Tango on Thursday June 28th 2018, 1:36
github.com/1thumbbmcc/wowcache.git
The Blizzard Warcraft Forums thread that precipitated this is here:
us.battle.net/forums/en/wow/topic/20765466460
Hope this helps.
by Shaun on Thursday June 28th 2018, 2:31
Regards
by Kevin Grittner on Thursday June 28th 2018, 10:15
Thanks!
by Atonner on Saturday June 30th 2018, 7:21
by Kevin Grittner on Wednesday June 27th 2018, 15:41
World of Warcraft Version 7.3.5 (26899) (Release x64)
Jun 21 2018
I've been running WoW under wine for years with few problems or quirks. Today it has become unusable due to $SUBJECT error. Some toons get it about a second after the character gets into the game; others only get it when opening certain dialogs (like the toy box or transmogrification window).
As I have been for some time, I am running wine as Windows 10 with defaults except that Graphics has only the "Emulate a virtual desktop" box checked with size set to 3840 x 1600 (the native resolution of my monitor), and the Staging tab has the first checkbox (Enable CSMT) checked.
I tried the Blizzard suggestion for streaming errors of renaming three directories under the WoW directory, with no joy.
If I run WoW from a shell rather than using the launcher I see a lot of lines like this:
002f:fixme:d3d11:d3d11_immediate_context_Map Ignoring map_flags 0x100000.
Once I get the error it seems to switch to spewing this instead:
002f:fixme:ntdll:NtQueryDirectoryObject multiple entries not implemented
Anyone else seeing this?
Any suggested workarounds or additional information I should provide?
by Steve Ebey on Wednesday June 27th 2018, 16:23
by GIGI on Wednesday June 27th 2018, 23:46
See this comment and following:
eu.battle.net/forums/en/wow/topic/17620282020#post-12
also there's a similar thread on the us.forums of Battle.net.
by Oscar Tango on Thursday June 28th 2018, 8:04
The zipped cache file in the repo may not work if you're not using a dual 64/32 build of Wine, as the game continued to give the "Streaming Error" for another user who was running a stand-alone 64 build. He subsequently flushed, migrated to Lutris and rebuilt Wine as shown here and was able to return to normal play, even with AddOns running.
Those users that have a 64/32 have reported no further issues once their original Cache folder is cleared, and the replacement "Windows-version" files are introduced. This is apparently a server-side glitch, which began for most of us after the 7.3.5 Patch was implemented on 2018 June 16. I have confirmed that subsequent Cache-folder clearing will cause the "Streaming Error" to manifest again, but that the replacement still works (as of 1300 UTC 2018 June 28).
by Chiro on Sunday June 24th 2018, 3:51
I cannot get past the login screen with wine. I get immediately disconnected with "BLZ51901015"
It works with the same connection under windows 10 for me just fine.
by Björn Bidar on Sunday June 24th 2018, 10:42
by RecursiveProgrammer on Sunday June 24th 2018, 15:51
Then I logged in...and it updated.
Now I get: BLZBNTBTS0000005C. I removed my .wine folder and re-downloaded the download application from blizzard, but I still get that error (the application says that it is downloading new files, get to about the second period, then, after a while, that error comes up.
I am on Antergos, and I have ran the attached scripts, on this page. Everything worked fine, before their update. I would have reported it sooner, but I figure it may just be my system (I have not tried looking for solutions to the displayed error messages on the terminal).
I also tried it on the AUR provided versions of wine, same thing.
The last set of messages in the terminal is:
```
Object moved
Object moved to here.
GIF89aÇ    ,D;00cb:err:ole:CoCreateInstanceEx apartment not initialised
00cb:err:ntdll:NtQueryInformationToken Unhandled Token Information class 24!
00cb:fixme:ver:GetCurrentPackageId (0x33fe14 (nil)): stub
00cd:fixme:kerberos:kerberos_SpInstanceInit 65536,0x7d3593a0,(nil): stub
00cd:fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
00cd:fixme:wbemprox:client_security_SetBlanket 0x7d2d882c, 0x175418, 10, 0, (null), 3, 3, (nil), 0x00000000
00cd:fixme:wbemprox:client_security_Release 0x7d2d882c
00cd:fixme:wbemprox:enum_class_object_Next timeout not supported
00cd:err:ntdll:NtQueryInformationToken Unhandled Token Information class 24!
00d2:fixme:ver:GetCurrentPackageId (0x1c3fe9c (nil)): stub
00d0:fixme:dbghelp:elf_search_auxv can't find symbol in module
```
So there is my two cents :-)
by Björn Bidar on Sunday June 24th 2018, 16:44
If you want you can try my build (wine-staging-pba-git):
thaodan.de/home/bidar/home-thaodan/x86_64/
by RecursiveProgrammer on Sunday June 24th 2018, 17:02
I just updated and (I think) opengl updated and it started to work :-)
I did not pay enough attention to when I was updating to correlate the error with an update.
by Atonner on Saturday June 30th 2018, 7:20
by Steve Ebey on Saturday June 23rd 2018, 9:13
by Sveinar Søpler on Sunday June 24th 2018, 10:57
When it comes to PBA, the "master" git of PBA is not updated since 3.7, but i have a rebased set that works with wine-staging-3.11, and so do "Firerat" on GIT (Just look on the forks). Patching that (3.11) on current wine-3,11 without staging was successful it seems, with quite a few offsets and a couple of fuzz'es tho. Did not try to compile, but can't see why it would not work :)
by malic on Wednesday June 13th 2018, 23:37
Clear WINEPREFIX
When I try the installer from the battle.net website, I have an error that it cannot create directory C:\ProgramData\Battle.net\Agent.
If I create that directory manually, it's the same.
Rights on directory tree are fine (per umask).
Any idea ?
by spaceman on Monday May 28th 2018, 10:59
Re-pba, will that work with other games, i.e. Final Fantasy XIV which runs on DX9?
by Steve Ebey on Monday May 28th 2018, 12:27
by hereuspam on Wednesday May 16th 2018, 8:20
fatal: repository 'github.com/wine-staging.git/' not found
Does anyone have a proper link?
by Steve Ebey on Wednesday May 16th 2018, 8:24
by Steve Ebey on Wednesday May 16th 2018, 8:32
by hereuspam on Wednesday May 16th 2018, 9:03
Cloning into 'wine-staging'...
remote: Not Found
fatal: repository 'github.com/wine-staging.git/' not found
git clone github.com/wine-staging.git
Cloning into 'wine-staging'...
fatal: remote error:
Repository not found.
Tried with both git and https, my network is fine, nothing is being blocked, i can clone the other 2 repo's. Is the link right? should it be github.com//wine-staging.git?
by hereuspam on Wednesday May 16th 2018, 9:05
by Steve Ebey on Wednesday May 16th 2018, 15:34
by Alberto on Thursday May 17th 2018, 3:42
by Steve Ebey on Thursday May 17th 2018, 6:30
by Alberto on Thursday May 17th 2018, 6:44
Finally, make install in wine64-build and other make install in wine32-build. Is right?
by Atonner on Saturday May 19th 2018, 19:54
by Steve Ebey on Sunday May 20th 2018, 7:50
by Atonner on Sunday May 20th 2018, 21:10
by Leopard Blanc on Monday May 14th 2018, 8:23
Windows Version is "Windows 10" with no native DLL whatsoever.
applications: imgur.com/a/2pJMumN
libraries: imgur.com/iHje9Lt
by spaceman on Wednesday May 16th 2018, 4:10
by Leopard Blanc on Monday May 14th 2018, 8:12
me@mycomp:~$ /opt/wine-staging/bin/wine64 --version
wine-3.8 (Staging)
Graphics Processor: GeForce GTX 1060 6GB
NVIDIA Driver Version: 390.48
Every setting identical except for DirectX:
DX9: imgur.com/a/kCf2yHz (FPS: 100.0)
DX11: imgur.com/a/0L2jfNe (FPS: 11.5)
So basically, the game is unplayable with DX11, but plays normal with DX9.
With or without ElvUI makes no difference.
There's no other addon installed.
Any clue ?
by Steve Ebey on Monday May 14th 2018, 9:50
by Iridias on Monday May 14th 2018, 16:02
On my system I've encountered a massive performance-regression with 3.8
With 3.7 I have like 50 - 60 FPS and with 3.8 it dropped to like 15 - 20 FPS (in the same region)!
Game is set to use DX11
My System:
GPU: AMD Vega 64
CPU: Core i7 6700
Drivers:
Mesa 18.0.1
AMDGPU (Kernel 4.15)
by Leopard Blanc on Tuesday May 15th 2018, 2:19
I now have the same performance with DX9 and DX11.
So, with the exact same settings, I go from 100 FPS with wine-staging 3.7/DX11 to 10 FPS with wine-staging 3.8/DX11.
It feels more like a bug really...
by Alberto on Tuesday May 15th 2018, 4:00
3.8 eats CPU and slow down FPS a lot. Is unplayble with 4fps. To play nice revert to 3.7.
by db14 on Tuesday May 15th 2018, 16:11
Ubuntu 17.10 x64
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
winehq-staging : Depends: wine-staging (= 3.7.0~artful)
E: Unable to correct problems, you have held broken packages.
Now I'm stuck with an unplayable wine version :|
by Alberto on Tuesday May 15th 2018, 16:20
But I rollbacked to wine 3.7 thanks to snapshots of BTRFS.
If I have a lot of updates of programs, I update first all except wine-staging.
Close the updater program and reopen again for only update wine, thus I have a snapshot with only wine changes to easy rollback if was necessary. ;-)
by Steve Ebey on Tuesday May 15th 2018, 16:53
Current Timetest fp bench - dalaran broken shore to shipwreck cove - 4/141/52 and return 9/109/49
3.7 Staging Timetest fp bench - dalaran broken shore to shipwreck cove - 1.5/126/51 and return 11/99/48
3.7 Staging on Argus, doing emissary quests for Argussian Reach. 34-50fps solo questing Frost DK killing void tainted krokul mobs
wine-3.8-39-g09bf88092d (Staging) on Argus, doing emmissary quests for Argussian Reach 59-70Fps solo questing Frost DK killing void tainted krokul mobs
after every single compile that I do, and installing both 32 and 64 bit, so I can run battle net app, I do wineboot --update to make sure that the prefix is clean. I download and compile my own wine, so if you are using packaged wine, might be a problem with a dependency in the package.
my compile script that I use is shown here
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-x
make -j24
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-x
make -j24
hope this helps
by Björn Bidar on Tuesday May 15th 2018, 17:44
by Steve Ebey on Wednesday May 16th 2018, 8:18
by Björn Bidar on Wednesday May 16th 2018, 8:22
I already build wine for myself but with pacman:
github.com/Thaodan/thaopkgs/blob/master/wine-staging-git/PKGBUILD
by hereuspam on Thursday May 17th 2018, 0:14
PKG_CONFIG_PATH=/usr/bin/pkgconf ../wine/configure CFLAGS='-march=native -mtune=native -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --with-wine64=../wine64-build --without-gtk3 --with-x
..
..
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries
Im on fedora 26, can you please help a newb?
by Steve Ebey on Thursday May 17th 2018, 6:34
by Atonner on Saturday May 19th 2018, 20:12
F26 has internal wine and you can add both winehq and winehq-staging repos manually
For the record, I'm going to suggest that the build notes be updated, a number of folks seem to have been confused at the make install step:
make install gets run in the 64 bit build directory.
if not installing, run the binary from the 64 bit build directory.
I run a parallel install and have my path modified in my WoW shell start scripts.
by Steve Ebey on Sunday May 20th 2018, 7:54
by Alberto on Sunday May 20th 2018, 9:13
by Steve Ebey on Sunday May 20th 2018, 13:28
by Leopard Blanc on Wednesday May 16th 2018, 1:59
If yes, you should have somewhere in your /etc/apt/sources.list (or /etc/apt/sources.list.d/*) something like:
deb dl.winehq.org/wine-builds/debian/ artful main
If you've done (and redone) all this, then type in a terminal:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install winehq-staging=3.7.0~artful wine-staging=3.7.0~artful wine-staging-amd64=3.7.0~artful wine-staging-i386=3.7.0~artful
Confirm and it should downgrade your wine version.
Note that by every upgrade it will give you the latest wine version. To prevent this, type:
sudo apt-mark hold winehq-staging
Your wine version will be frozen, as long as you do not unhold it (you'll have to do it if version 3.9.0 solves this problem...).
by DeeDee Ranged on Thursday May 17th 2018, 1:06
sudo ln -s /var/lib/synaptic/preferences /etc/apt/preferences.d/99pinned.
This will also pin/lock it systemwide.
by DeeDee Ranged on Wednesday May 16th 2018, 12:18
dl.winehq.org/wine-builds/ubuntu/pool/main/
Depending if your running Ubuntu 64 or 32 bits. For 64 bits you need the following packages:
winehq-staging_3.7.0~artful_amd64.deb
wine-staging_3.7.0~artful_amd64.deb
wine-staging-amd64_3.7.0~artful_amd64.deb
wine-staging-i386_3.7.0~artful_i386.deb
Before installing remove/purge all the wine-staging 3.8 packages, then in the directory where you downloaded the wine-staging packages install in a terminal
3.7 packages with sudo dpkg -i wine*. That should do the trick.
Usually before I can downgrade I have to purge winehq-staging and wine-staging_3.x.x~artful_amd64 and then I can downgrade the other 2 packages.
I run Debian but in this case it doesn't matter ;)
Hope this helps.
by Dox on Sunday May 6th 2018, 15:59
Mouse cursor issues are annoying. Would love to find a fix for it, but don't have time right now to look into it. Hoping someone here will have already fixed it.
by Steve Ebey on Sunday May 6th 2018, 17:51
by Xantek on Saturday May 5th 2018, 12:30
by Björn Bidar on Saturday May 5th 2018, 13:00
Just download it somewhere and run
export WINE_PATH=
usenew wow.exe
For more see:
github.com/Thaodan/usenew/blob/master/doc/usenew.org
by Björn Bidar on Saturday May 5th 2018, 13:04
by Xantek on Saturday May 5th 2018, 13:19
by Sveinar Søpler on Sunday May 6th 2018, 15:22
Where did you install wine-staging-pba-3.7? :) Lets for example sake say you installed that in "/home/xantek/wine-pba-3.7" And you downloaded battle.net.exe (or whatever the installer is called), and you want your battle.net wineprefix to be "/home/xantek/Battle.net"
The command to run battle.net.exe with the correct prefix and wine version should be:
env WINE="/home/xantek/wine-pba-3.7/bin/wine" WINEPREFIX="/home/xantek/Battle.net" battle.net.exe
The wine folder structure should then be under your /home/xantek/Battle.net/drive_c/ , so after install you treat that folder as the C: drive in windows.
Hopefully a bit explanatory, or else i would rather recommend you use something like Lutris or Playonlinux to manage your wine versions and wine prefixes as it simplifies this process :)
PS. Compiling wine yourself is not that hard, and running wow or other 64 bit games is just as well done with ONLY 64 bit wine, but to run installers and winecfg or whatever to set things up, you NEED the 32 bit wine and it must be cross compiled for your distro. One of the more popular distro's like Ubuntu has a rather tedious compile method for 32-bit, explained here: wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu
by Xantek on Monday May 7th 2018, 16:04
Intel i5 2500k @3.3GHz
16 GB ram DDR3 1600 MHz
Nvidia GTX1070
What do you think, should I have more FPS? I know, that WoW really likes to use CPU, but I don't remember having this low FPS using Windows...
by Sveinar Søpler on Tuesday May 8th 2018, 8:26
Been very long since i ran wow in windows myself, so i dont know, but there are 1 main factor that wine relies on really, and that is CPU speed. More or less raw clock speed i guess.. Aswell ofc graphics card tho, but you rarely are able to tax the graphics card more than 30-40% (even in windows) unless you enable MSAA or similar tho.
I have a old i7, but it runs 4.2 GHz core, and for wine that is actually better than 3.3GHz even tho the cpu is newer.
In Dalaran on busy nights i guess i have around 50'ish fps with PBA patchset.. sometimes dip lower, and facing a wall 200+ fps.. really depends. Thing is that with more ppl/effects++ the CPU load goes up, and the gpu load goes down :)
I use graphics setting "7" on a 1080p display. "Custom" settings in /WTF/Config.wtf:
SET timingMethod "2"
SET processAffinityMask "255"
SET worldPreloadNonCritical "0"
SET gxTextureCacheSize "3070"
SET M2Faster "3"
SET timingModeOverride "2"
Thats with a GTX970 4GB card.
Custom settings for my wineprefix:
export WINEDEBUG="-all"
export __GL_SHADER_DISK_CACHE_PATH="$HOME/.nv/WoW"
export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SYNC_TO_VBLANK=0
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
export PULSE_LATENCY_MSEC=30
(I put this in my wow script that i use to launch wow)
Oh.. and lastly: Once you get wow up and running, it will take some time building the shader cache, both for nVidia and WoW.. thus you may experience random stutters the first couple of hours of play until it smoothens out. This may also happen when there is a new wine version/drivers and/or wow patch :)
by Xantek on Tuesday May 8th 2018, 10:18
by Sveinar Søpler on Tuesday May 8th 2018, 10:37
by Steve Ebey on Sunday April 29th 2018, 9:03
by spaceman on Sunday April 29th 2018, 10:59
It's less painfully now I use BigWigs and not DBM.
by Steve Ebey on Sunday April 29th 2018, 12:58
by Chiro on Sunday April 29th 2018, 12:59
by Steve Ebey on Sunday April 29th 2018, 13:08
by Gibbo on Monday April 30th 2018, 2:03
by Sveinar Søpler on Tuesday May 1st 2018, 9:08
by Steve Ebey on Wednesday April 11th 2018, 20:59
by Atonner on Saturday April 21st 2018, 7:31
If the *game* launch dies with this I've found that I have to kill off the running wine server. (I've found that even if I'm launching the game directly and I get this, wineserver can be left running for several minutes after the game dies)
I've not seen this for launching Battle Net Client unless you're missing the TLS libraries.
by Tim Ryan on Wednesday April 25th 2018, 9:29
by Sveinar Søpler on Tuesday May 1st 2018, 9:11
Just thinking if it was not triggering dx10 stuff, maybe DXVK could be used....
by Chiro on Tuesday May 1st 2018, 9:14
by Sveinar Søpler on Tuesday May 1st 2018, 15:47
by Chiro on Sunday June 24th 2018, 3:02
Quite a few games work that way.
Also you could try DXUP github.com/Joshua-Ashton/dxup alongside DXVK
by d3rrial on Wednesday April 4th 2018, 13:58
by Björn Bidar on Wednesday April 4th 2018, 14:00
by d3rrial on Wednesday April 4th 2018, 14:03
I was reading the original blog post and it was talking a bit about d3d9 architecture, but didn't mention this improving performance for d3d11 :)
by Simon Kristensen on Sunday April 1st 2018, 3:02
../wine-pba/patches/0001-wined3d.patch:87: trailing whitespace.
../wine-pba/patches/0001-wined3d.patch:1241: trailing whitespace.
../wine-pba/patches/0001-wined3d.patch:1522: trailing whitespace.
error: patch failed: dlls/wined3d/buffer.c:28
error: dlls/wined3d/buffer.c: patch does not apply
error: dlls/wined3d/buffer_heap.c: already exists in working directory
error: patch failed: dlls/wined3d/context.c:4956
error: dlls/wined3d/context.c: patch does not apply
error: patch failed: dlls/wined3d/cs.c:73
error: dlls/wined3d/cs.c: patch does not apply
error: patch failed: dlls/wined3d/device.c:840
error: dlls/wined3d/device.c: patch does not apply
error: patch failed: dlls/wined3d/directx.c:111
error: dlls/wined3d/directx.c: patch does not apply
error: patch failed: dlls/wined3d/Makefile.in:6
error: dlls/wined3d/Makefile.in: patch does not apply
error: patch failed: dlls/wined3d/resource.c:340
error: dlls/wined3d/resource.c: patch does not apply
error: patch failed: dlls/wined3d/state.c:4797
error: dlls/wined3d/state.c: patch does not apply
error: patch failed: dlls/wined3d/texture.c:2096
error: dlls/wined3d/texture.c: patch does not apply
error: patch failed: dlls/wined3d/utils.c:6321
error: dlls/wined3d/utils.c: patch does not apply
error: patch failed: dlls/wined3d/wined3d_gl.h:44
error: dlls/wined3d/wined3d_gl.h: patch does not apply
error: patch failed: dlls/wined3d/wined3d_private.h:75
error: dlls/wined3d/wined3d_private.h: patch does not apply
Can someone help a noob?
by Steve Ebey on Sunday April 1st 2018, 9:01
by Steve Ebey on Sunday April 1st 2018, 9:19
good luck
by Simon Kristensen on Sunday April 1st 2018, 11:31
I first built the wine source 3.5 from git repository, with ./configure , then make, then make install. Then I tried to to 'make uninstall', then 'make clean'. Something went wrong I don't remember what. Then I simply deleted folder, and cloned again, following your steps carefully.
by Steve Ebey on Sunday April 1st 2018, 16:52
by Simon Kristensen on Monday April 2nd 2018, 12:55
But I am curious about how you symlinked to your windows10 partition. I am also dual-booting with win10, and currently WoW is installed on both partitions.
I have two ssd disks. One running ext4 and the other ntfs for windows. I don't know where to start, can you throw a link or something where I can read up on how to do this kind of sorcery? :)
by Simon Kristensen on Tuesday April 3rd 2018, 12:09
by David Eriksson on Saturday March 17th 2018, 13:55
by Atonner on Friday March 16th 2018, 15:58
Fedora 26, AMD 8350 8 core, 16 Gig ram, Nvidia 970GTX 390.25 (4 Gig ddr5)
In wine staging 2.9x I was seeing (with all the tweaks and tuning) about 20 to 32 FPS on average throughout Broken Isles and Argus.
In wine staging 3.3 I was seeing (after removing a couple of tweaks and adding a couple of others) 12 to 18 FPS on average in Broken Isles and Argus.
(Pretty much anywhere else in Wow was only ever 2 or 5 FPS better)
With self built wine 3.3 + staging patches + pba patches...... Holy CRAP!!!
Ran a full run with my main in Argus doing *all* the dailies = 48 to 65 FPS on average, with post zoning taking about 35 to 50 seconds to clear (I've the long zoning fix in Config.wtf) - on entering a zone I'm seeing 8 to 25 FPS, but about one minute after the zone load is done and I'm back up to 35 in *really busy* areas and from 60 up in quiet areas.
pulled wine 3.3 stable
pulled staging patches
pulled pba
unpacked 3.3 stable, used the patch apply script in staging, manually patched the pba patches - all good.
built the patched wine following Shared WoW64 options and with bugger all compiler tweaks. - Installed (in /opt/wine-staging-pba using the prefix= configure option)
I'm stunned .... I've not seen framerates like this since Blizz killed off openGL support - YAY!!!!
-- So -- zoning into Dalaran (new) I'm getting 32 to 45 FPS after the zone load is completed, 8 to 15 when I land. I do get "hiccups" in response while on the landing spot - and for the first 30 to 50 seconds in any new zone. I' was in a cave in Argus (the one with all the imps and imp mothers) and while running back down the fel cascade had a couple of screen tearing events. Other than that I see no issues with this bundle - I did watch memory usage, and it rose continuously to 3.8Gb for the Wow process and 1.3Gb for the wineserver process (over almost 90 minutes), but that was the cap.
One point, if you build all this yourself, you need to get the wine-gecko msi packs and put them in /path/to/wine/share/wine/gecko in order for the battle net client to work.
by hereuspam on Wednesday May 16th 2018, 23:54
by Atonner on Saturday May 19th 2018, 20:57
CAVEATS:
1) I run a dual install of wine - I have standard winehq staging install **AND** a unique install for playing WOW.
Most folks will not need to do this - I have both due to another application I need to run that is unrelated to gaming.
2) I use scriptlets to run both battlenet and WoW correctly using the wine-staging-pba binary. In those scriptlets I modify the path by prefixing my wine staging pba binary directory before my normal path.
3) the URIs in the build script -- I do not seem to have the posting-fu to get the URIs to come out correctly for CUT AND PASTE.
4) Read the FIX statements - the below *work for me*
I do *not* have all the dependencies for wine build installed (but I've been building wine manually on occasion for years) - but as Steve indicates dnf will install the dependencies.
*this is my BUILD script*
FIX -march and -mtune options for YOUR CPU.
FIX WORKDIR to a path suitable for you. (or create ${HOME}/wow/wine3.3-pba )
FIX WPREFIX to /usr if you will not be dual mode installing wine (i.e. both using a repo source install AND this manual build install)
____________________________________________begin build script___________________________________________________
export COPTS='-march=bdver2 -mtune=bdver2 -O3 -fPIC -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS'
export WPREFIX=/opt/wine-staging-pba
export WORKDIR=${HOME}/wow/wine3.3-pba
cd ${WORKDIR}
rm -fr wine 2>/dev/null
rm -fr wine-staging 2>/dev/null
rm -fr wine-pba 2>/dev/null
# Below URI is git://
git clone source.winehq.org/git/wine.git > /dev/null 2>&1 && echo "Cloned wine git" || echo "FAILED clone of wine git"
# Below URI is https://
git clone github.com/wine-staging/wine-staging.git >/dev/null 2>&1 && echo "Cloned wine staging git" || echo "FAILED clone of wine staging git"
# Below URI is https://
git clone github.com/goldpaw/wine-pba.git >/dev/null 2>&1 && echo "Cloned wine PBA patches git" || echo "FAILED clone of wine PBA patches git"
cd ${WORKDIR}/wine-staging
./patches/patchinstall.sh DESTDIR="../wine" --all >/dev/null 2>&1 && echo "Patched to wine-staging" || echo "FAILED to patch to wine-staging"
cd ${WORKDIR}/wine
git apply ../wine-pba/patches/* >/dev/null 2>&1 && echo "Patched to wine-staging-pba" || echo "FAILED to patch to wine-staging-pba"
cd ${WORKDIR}
rm -rf wine_build_64 2>/dev/null
mkdir wine_build_64
cd ${WORKDIR}/wine_build_64
../wine/configure CFLAGS="${COPTS}" --enable-win64 --prefix=${WPREFIX} >> scripted.configue.log 2>&1
make >> scripted.make.log 2>&1
cd ${WORKDIR}
rm -rf wine_build_32
mkdir wine_build_32
cd ${WORKDIR}/wine_build_32
../wine/configure CFLAGS="${COPTS}" --with-wine64=../wine_build_64 --prefix=${WPREFIX} >> scripted.configure.log 2>&1
make >> scripted.make.log 2>&1
cd ${WORKDIR}/wine_buld_64
sudo make install
__________________________________________________end build script__________________________________________________
my BNET launcher:
FIX the path statement if needed,
FIX the path to world of warcraft launcher.
__________________________ begin Bnet.launch.sh _________________________________________________
#!/bin/bash
echo "Killing off old instances"
wineserver -k
wineserver -k
echo -n "5 "
# this line can be removed if you don't dual install wine
export PATH=/opt/wine-staging-pba/bin:${PATH}
# this line can be removed if you don't dual install wine
export WINEPREFIX=$HOME/.wine-staging-pba
export WINEDEBUG=-all
# below no longer supported in nvidia
# export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SYNC_TO_VBLANK=0
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
export STAGING_RT_PRIORITY_SERVER=90
echo -n "4 "
winetricks glsl=enabled > /dev/null 2>&1
echo -n "3 "
winetricks videomemorysize=4096 > /dev/null 2>&1
echo -n "2 "
winetricks vsm=3 > /dev/null 2>&1
echo -n "1 "
winetricks gsm=3 > /dev/null 2>&1
echo "GO!"
# MODIFY THE PATH TO World of Warcraft Launcher.exe !!!!!!!!!!
wine64 /opt/windows/Games/World\ of\ Warcraft/World\ of\ Warcraft\ Launcher.exe &
echo "Launched!"
____________________________________ end BNET launcher script _________________________________________
My Warcraft launcher script:
__________________________________ begin Warcraft_launch.sh _______________________________________________
#!/bin/bash
echo "Kill off old instances"
wineserver -k
wineserver -k
echo -n "5 "
# this line can be removed if you don't dual install wine
export PATH=/opt/wine-staging-pba/bin:${PATH}
# this line can be removed if you don't dual install wine
export WINEPREFIX=$HOME/.wine-staging-pba
export WINEDEBUG=-all
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
# no longer supported in nvidia
#export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SYNC_TO_VBLANK=0
export STAGING_RT_PRIORITY_SERVER=90
echo -n "4 "
winetricks glsl=enabled > /dev/null 2>&1
echo -n "3 "
winetricks videomemorysize=4096 > /dev/null 2>&1
echo -n "2 "
winetricks vsm=3 > /dev/null 2>&1
echo -n "1 "
winetricks gsm=3 > /dev/null 2>&1
echo "GO!"
# FIX YOUR PATH TO Wow-64.exe
/wine64 /opt/windows/Games/World\ of\ Warcraft/Wow-64.exe -d3d11 &
echo "Launched .....!"
by godson on Thursday March 8th 2018, 6:35
However, when I launch World of Warcraft I get the old game initialization failed error and the mouse cursor then defaults and sticks to the top left corner of my screen. I can zoom out and close down the world of warcraft window OK to put that right again though.
Any ideas? I thought that having CSMT enabled got rid of the initialization error.
by Steve Ebey on Thursday March 8th 2018, 8:06
CSMT is simply to try to get more speed from the video driver, but with the pba patch, I personally do not see that much of a change in FPS. I am very pleased with pba and the FPS is almost triple what I had in 2.18 staging.
by godson on Thursday March 8th 2018, 8:33
by godson on Thursday March 8th 2018, 8:41
Clearly it's just me doing something wrong here but worth having a mention of in case anybody else is being hit by the same thing.
I have no dll overrides, using windows 7 as standard, set to DX11 windowed. battle.net opens, the wow launcher opens but the game just won't go past the play screen
by Danny on Thursday March 8th 2018, 9:41
by Sveinar Søpler on Thursday March 8th 2018, 10:38
So the correct order of things would be: download wine-3.3 -> download & patch wine-staging-3.3 -> patch wine-staging-3.3 with pba patches. -> compile.
Recommend running wow either from a script or from Lutris as a "standalone" .exe rather than try to run it from the battle.net launcher...
by spaceman on Thursday March 8th 2018, 12:14
Warcraft works out of the box with 3.3 staging. No dll overrides, no additonal components. Have you tried launching WoW without the cursed launcher?
wine '/${YOUR FULL PATH}/Games/World of Warcraft/Wow-64.exe' -dx11
Performance as good as it's been since Blizzard's DRM updates to their client.
by spaceman on Thursday March 8th 2018, 12:17
by godson on Tuesday March 13th 2018, 6:02
I got tied up in knots with this but thankfully got a result in the end.
Firstly I removed everything and started again, tried to install battle.net using the Lutris install link - it installed but errored - I believe this perhaps was an Nvidia driver issue though as going back to 3.84 again made it work.
I then installed WoW from the Lutris installer and again errored at couldn't install Battle.net, then wouldn't load because it couldn't find battle.net.
To get around this I copied the battle.net install directory across to the program files x86 directory in World of Warcraft.
Net result is MUCH smoother gameplay, occasional FPS drops randomly but where I would only get 15-30 FPS before I am seeing 60fps pretty stable now and drops to 20-22 for a second or so every now and again.
by godson on Friday March 9th 2018, 9:05
I did manage to load up the game yesterday for a short while but the fps for me was much lower than 2.21. Clearly something has gone amiss so I will try again on a fresh install of Lutris and see if that clears issues up.
by Dox on Wednesday March 7th 2018, 12:03
Here is a direct link: lutris.net/games/world-of-warcraft/
Enjoy,
Dox
by Stein Erik Svendheim on Thursday March 8th 2018, 3:07
Here's a screenshot from Stormwind with the settings I use. FPS counter at the bottom:
www.dropbox.com/s/0ujxvmuosjtrzpn/wowsettings.png?dl=0
Stormwind has of course been more crowded than this from time to time, but consider me impressed anyhow.
Outside the big cities, it's basically 60fps all the time, except the Legion areas, which drops to 30-40.
CSMT enabled
Nvidia 1070 with 390.25 driver.
by Danny on Thursday March 8th 2018, 5:49
Thanks for this build Dox.
by Björn Bidar on Tuesday March 13th 2018, 4:31
With the PBA patches and the client crashes. Have you an idea why exactly?
Also there are the shader cache patches that are sadly no longer compatible with wine 3.3
by Dox on Tuesday March 13th 2018, 5:37
Also there seem to be some issues now with the Blizzard App in general that it crashes when you click anywhere in the "browser" window. No clue about that, happens from Staging 2.18 to 3.3.
I have no clue what shader cache patches, but if you talk about the one in Staging that wasn't accepted, it is inferior to the Nvidia / mesa solution, except for perhaps very specific cases.
by Sveinar Søpler on Thursday March 15th 2018, 7:18
Other than that, i can recommend using a own cache folder for wow... atleast if you play more than just 1 game, as the nVidia cache have somewhat of a limitation when it comes to size, and it will start to overwrite itself and cause stuttering the next time you start the game.
export __GL_SHADER_DISK_CACHE_PATH=/home/yourname/.nv/WoW
The default is just $HOME/.nv , and if you play different games or use different GL applications, nVidia driver will start overwriting when it gets "full". Having a separate folder for WoW alone, will lessen the chance of overwriting from running other games/graphical apps.
HOWEVER, if you change wine-versions, or upgrade drivers++ this will cause nVidia to generate the cache again most likely.
The WoW "Cache" folder in your install directory also has loads of textures and stuff cached.. if you upgrade wine, or drivers this will also most likely be overwritten. Sometimes this can create errors and problems along the way, so i tend to clear out both my $HOME/.nv/WoW folder + wow_installed_folder/Cache folder each time i do a wine upgrade (ie. switching from wine-staging-pba-3.2 -> wine-staging-pba-3.3). Bare in mind that it will take quite a while playing to get "everything" cached.. So the first time entering a zone/raid/instance after doing this, it will stutter...
You can use as many __GL_SHADER_DISK_CACHE_PATH's you like (and i guess place them wherever your user has write access).
by Dox on Thursday March 15th 2018, 9:39
The WoW cache folder I clear when there is a WoW patch (sometimes). This can fix some errors sometimes. But I definitely do not do this on a Wine version / Nvidia version switch.
by Sveinar Søpler on Monday March 5th 2018, 13:48
Having low fps to start with, 2-3-4 fps change from a average of 40, is up to 10%. That is actually a LOT. If a new driver comes along that gives ppl 10% increase in 3DMark, the "gamers" go wild... Having "bad luck" while doing a /timetest 1 run in wow can easily be up towards that.. so in reality, doing benchmarks in wow is not a reliable method... atleast not for comparing minor changes. Sure it is easy when you do a run and get 20-24 fps, and with another setting you get 40-45 fps.. cos thats a 100% increase... But doing a tweak that normally would just get you 1-2 fps, there is no way to measure this reliable in wow.
So why is this?
I have a theory about this tho.. but more than welcome other ideas or methods to tests. My theory is basically this:
We know wow (or any kind of mmo) rely on syncronizing data between client server.. and this seeing something move or a spell cast would mean You -> server -> other person -> server -> you. So how does this work? What if the "other person" is on a crappy dialup or whatever with 500ms? Well.. the server i guess does loads of things to compensate this, but this WILL sometimes mean the server stops stuff happening to catch up. Now in theory this should perhaps not have anything to say on how well your local machine renders its graphics.. you should still be able to have 200+fps, even if you wait on data from others.. right?
Well.. i dont think so. There are numerous examples of mmo's with sub-par graphics that are really laggy.. So there HAS to be something more to it than just "local client" and "random data", and i do believe that any mmo depends on traffic and server load more than just client. One such example i guess we have all experienced playing wow.. the "OMGZ LAGGZZZ" sometimes happening.. sometimes this wont hamper your fps, but other times everything just goes crashing down... aswell as horrible ping to the server makes for poor fps ingame. There is a correlation there :)
Now, thats well and fine, cos most of you guys already knew this... but what wow does that not many (or any?) other mmo's do, is that they do not have a "single zone server".. there are many, and you get bounced back and forth between them.. Dont remember when this happened exactly, but it was around the time where cross-realm stuff and zone scaling and all that stuff started happening. Where if you are at a different point in a quest chain or a different level, you cant even see ppl in your group until you are at the same spot in the chain. This means that when i log on, i can be online on server #124 of the zone Dalaran, while my pal "joe" can be online in Dalaran at the same time, but on server #89.. and basically we are NOT on the same server, and cant even see eachother... until we group, and we both get put on server #43...
In other words.. there are not two times you log on, where you are on the same server. If one server is having more load/latency/ping = less fps, thus rendering our last benchmark run invalid. I use "server" here as the actual hardware running the zone, and not your "realm".. just to be clear. Think of it like when you log on to facebook.com. Its not 1 server feeding the "world", although from the users perspective you are on 1 server :) Blizzard HQ has several serverparks, all interconnected.
Loads of text.. probably mostly jibberish.. but atleast a theory of why you can log on, test something, log off, change NOTHING, and come back to a slightly different testresult.
Only way imo to test graphics performance in wow would either a: get a offline benchmark client with the graphics engine, or b: set up your own private server.
Thoughts?
by Jon on Tuesday March 6th 2018, 1:18
by Sveinar Søpler on Tuesday March 6th 2018, 8:37
I would prefer to run something like that purely "in-house", so not to risk any troubles that way.
by hirschhornsalz on Tuesday March 6th 2018, 6:57
I would propose: Disable vsync, disable frame limiters, select 10 as detail level, rendering 100%, no antialias.
Stand at the flight master in Dalaran (Legion), enter /timetest 1 in the chat, choose Meredil as flight destination.
by Sveinar Søpler on Tuesday March 6th 2018, 8:35
It does not matter what flight path you take, cos the comparison in itself is not to benchmark my system against yours really.. its to test variances when changing wine versions and/or ingame settings and stuff like SET M2Faster "3" and minor tweaks, that could gain you 0.5, perhaps 1 fps. Minor.. but every fps counts, especially when you do not have too many :)
by Dox on Wednesday March 7th 2018, 11:46
Any testing in raids will be purely subjective, but "gamer feeling" should be enough for that. It isn't perfect, but it is good enough.
by Jon on Friday March 2nd 2018, 21:41
It occurs to me that this is actually technically a very simple problem to solve. The hard part is just getting everyone to agree on the solution. So, I'd like to propose a simple WoW benchmark method that gives more predictable results, is easy to replicate, and focuses on performance bottlenecks rather than absurdly useless peak framerate scores generated with your nose stuck in the corner of a small room in an unpopulated zone.
The most important thing about this benchmark methodology is that we give it a name so that everyone who knows about it can agree on what it is and therefore how to do it. In order to distinguish this benchmarking method from other future benchmarks, we need to use a name with sufficient verbosity.
I propose we name this benchmark "The Horde Bank New Dalaran Benchmark" and it works as follows:
1) Go to to "new" Dalaran (no spoilers for those who don't know where that is!)
2) Go to the "Horde Bank" (the one nearest to Windrunner's Sanctuary)
3) Position your character at the middle of the lowest step of the bank's stairs, at the point in the very center
4) Zoom the camera in as far as you can while still keeping your whole character visible above your primary ActionBars
5) Aim the camera towards The Violet Citadel so that, on screen, your character's head is positioned between the pillars at the foot of it's main staircase.
6) Mouse over the red "?" on the ActionBar to see the current framerate (brace yourself for disappointment if you had previously been under the illusion you get decent performance from WoW in wine)
Now, I know this is still not perfect, and the framerate can be affected by how crowded the street is, but it only seems to actually move it by a couple FPS.
(I'm getting 11 FPS right now using this method on Ultra settings with wine-staging 2.21.)
by Sveinar Søpler on Sunday March 4th 2018, 7:52
1. As you pointed out.. it CAN depend on how crowded the street is
2. Camera zoom "keep above primary actionbar" and stuff like that, works if you use the standard blizzard ui. I have a custom one, and im sure many have. Thus MY primary action bars MAY be in a totally different spot than yours. Zooming camera IN all the way will ofc negate that difference, cos you can only get IN max and look from a 1st person perspective.
3. Get the angle wrong = may change your fps by a lot.
4. Is there a "ultra" setting? There are many.. but the slider has numbers. It seems as the default usable setting in dx11 is "7", and some say this was what was max quality last expansion. Better to use that number.
Static fps viewing is imo not too useful for a "benchmark". The "timedemo 1" option in wow is created for a reason. I would rather propose a standarized benchmark consist of a set flight-path using timedemo 1. You will get listed min/max/avg fps that way. I did a whole lot of them a while back, and doing 3 of them, adding the numbers and dividing by 3, thus creating a "average" for those 3 runs.
Be aware that also there camera viewpoint would play a role, aswell as "looking around while flying", so the rules would be something like : Zoom IN to 1st person, do NOT move mouse/camera while flying.
There is a reason why benchmarks such as the Unigine ones, or 3dmark ones follow a set script each time they are run :)
by spaceman on Monday February 26th 2018, 18:08
Pet Battles also work I can confirm, I will let you know if they stop. ;D
MSAA produces a black screen regardless of setting - replicated (antiX-17 Linux Core)
CMAA produces edges on geometry that are visible through some 2D UI objects - I experienced this effect with Xfce 4 so it's apparently not DE related.
Keep us posted on how to with 3.x...staging is discontinued and frankly, World of Warcraft and Heroes of the Storm have appalling performance. Battle.net is so flaky, breathe and it crashes.
by Steve Ebey on Monday February 26th 2018, 19:11
by Steve Ebey on Saturday February 24th 2018, 22:21
by Björn Bidar on Sunday February 25th 2018, 3:29
I do raids with wine but heroic and mythic.
Except the ground texture issue it works fine.
You may look at github.com/acomminos/wine-pba.
PS: I hope you package wine proper, If you do this you dont need symlinks.
by Sveinar Søpler on Sunday February 25th 2018, 10:54
Seems like you run with DX9 then? No problem, until they (blizzard) kill that option completely tho :)
by Björn Bidar on Sunday February 25th 2018, 11:49
by Steve Ebey on Sunday February 25th 2018, 13:31
by Sveinar Søpler on Sunday February 25th 2018, 11:11
Havent payed much attention to the staging git of late (been busy fiddling with dxvk hehe). Patched and compiling as we speak :)
by Björn Bidar on Sunday February 25th 2018, 11:48
by Chiro on Sunday February 25th 2018, 11:52
WoW requires DX 10.1 in DX11 mode, so DXVK has nothing to offer.
by Sveinar Søpler on Sunday February 25th 2018, 13:33
err: DxgiAdapter::CheckInterfaceSupport: No D3D10 support
Might change with wow 8.0 (or whatever Battle of Azeroth will be versioned) when they get rid of d3d9 completely, and possibly rewrite something tho...
by Chiro on Sunday February 25th 2018, 13:59
by Dox on Saturday February 24th 2018, 7:50
I'm using the patches now, DX11 doesn't work yet, but DX9 does. You have to start WoW directly and bypassing Blizzard App because of this. Using "-d3d9" as command line argument.
DX9 on Staging 2.21 runs faster then DX9 on my WoW2.0 branch:
Staging 2.21 DX11: 42 fps (CSMT disabled since it lowers fps)
Staging 3.2 DX11: 18 fps (CSMT disabled since it lowered fps)
Staging 2.21 DX9: 48 fps (CSMT disabled since it lowers fps)
Staging 2.0 DX9: 82 fps (CSMT enabled)
Staging 2.21 PBA / DX9: 90 fps (CSMT enabled)
DX11 support is incoming in the coming days.
by Björn Bidar on Saturday February 24th 2018, 11:08
I really need something like this because that bottleneck hits me really hard compared to the power of my GPU (1080ti).
Maybe this makes 4k better playable.
by godson on Monday February 26th 2018, 11:43
by Sveinar Søpler on Tuesday February 27th 2018, 10:56
Used wine-git with wine-staging-git
Wine-Staging thread compare - Valley:
csmt=1, threaded=1 - 77.2 fps
csmt=0, threaded=1 - 63.4 fps
csmt=1, threaded=0 - 70.7 fps
csmt=0, threaded=0 - 54.7 fps
wine-vulkan-3.2 w/dxvk
dxvk does not use csmt from wined3d, nor do "GL" conversion, so GL_THREADED_OPTIMIZATION had no impact (i did test, but same fps +/- 0.1 fps within margin of error)
csmt=N, threaded=N - 82.5 fps
dxvk do have some issues with reflection/lighting with my GTX970 tho, so not "perfect" atm.
by Sveinar Søpler on Monday March 5th 2018, 13:17
Test was to fly from Felblaze Ingress Crimson Thicket, so that you fly by the edge of Suramar city. I zoomed the camera full in (1st person), and did not move anything while doing /timetest 1. To make sure textures and shaders were loaded and cached, i flew back and forth before doing the timetest.
Results are: min/max/average
Felblaze Ingress -> Crimson Thicket
wine-staging-2.18
csmt=1, gl_thread=1 - 24.5/68.5/44.4
csmt=1, gl_thread=0 - 20.6/58.9/36.8
csmt=0, gl_thread=1 - 26.6/66.7/43.1
csmt=0, gl_thread=0 - 15.8/49.0/29.5
wine-staging-3.3
csmt=1, gl_thread=1 - 14.8/35.9/22.0
csmt=1, gl_thread=0 - 19.8/51.3/31.8
csmt=0, gl_thread=1 - 14.6/35.1/21.8
csmt=0, gl_thread=0 - 16.2/50.4/30.7
Crimson Thicket -> Felblaze Ingress
wine-staging-2.18
csmt=1, gl_thread=1 - 21.7/56.9/42.6
csmt=1, gl_thread=0 - 19.6/45.6/34.1
csmt=0, gl_thread=1 - 24.3/54.9/40.7
csmt=0, gl_thread=0 - 15.7/36.4/27.0
wine-staging-3.3
csmt=1, gl_thread=1 - 13.9/27.7/20.5
csmt=1, gl_thread=0 - 17.0/40.0/27.2
csmt=0, gl_thread=1 - 14.3/27.5/20.4
csmt=0, gl_thread=0 - 8.2/38.3/26.4
It seems as __GL_THREADED_OPTIMIZATIONS= has a negative impact on the wine-3.3 source for some reason and csmt having less impact on 3.3 than 2.18. If this has to do with me using a custom kernel with PDS cpu scheduler or not, i dont know.
What seems clear is that there is a rather big degradation in performance using 3.3 at this time. It will be fun to see what can come of this PBA patching tho, as i think DXVK is further from working with wow than PBA mostly due to wow depending on non-supported DX10. DX10 also being a thing not really well supported with wine in general i guess...
I'll pop up a new thread regarding my theories around wow benchmarking and timetest.
by Chiro on Monday March 5th 2018, 14:05
Instead, figure out the patch that introduced the regression in vanilla wine.
by Sveinar Søpler on Monday March 5th 2018, 15:29
So.. you want to dig through several hundreds of patches to figure out which one created slower D3D11 performance from 2.21 -> 3.2? I would not think it is a "1 patch deal" either :)
Saw the same when "correctness" was done for 2.x with csmt. 2.0 DX9 performed massively better than 2.1 with its new csmt. 3.x i guess introduces several more changes, even tho it halves performance. WineHQ devs i guess do not optimize code for performance, atleast not at this stage.
by Chiro on Tuesday March 6th 2018, 0:35
Takes time but you don't have to try all permutations for a few hundred patches
by Sveinar Søpler on Tuesday March 6th 2018, 8:41
You are more than welcome to do that, and just tell me and others what patch makes this slowdown, but I wont spend countless hours trying to reverse-patch wine-staging-3.3 back to wine-staging-2.21 to figure that out :)
by Sveinar Søpler on Tuesday March 6th 2018, 9:55
Ran Unigine Valley benchmark DX11:
wine-staging-2.18:
78.6 fps (3290)
wine-staging-3.3:
77.0 fps (3222)
wine-pba-3.3:
92.5 fps (3872)
Native OpenGL:
85.1 fps (3558)
wine-pba-3.3 BEATS native Linux OpenGL performance! Wow... (not as in World of Warcraft... but WOW! ) Now we are cooking! :)
by Steve Ebey on Tuesday March 6th 2018, 10:02
by Sveinar Søpler on Tuesday March 6th 2018, 12:40
Downloads 4 patches. Patch with : patch -p1 < 0001...... and so on for the 4 patches. Works with wine-staging-3.3 : github.com/wine-staging/wine-staging/releases
by Steve Ebey on Wednesday March 7th 2018, 7:33
git clone wine 3.3 from winehq devel source
git clone wine 3.3 staging
apply staging patches to wine
git clone wine pba
apply pba patches to wine
configure --enable-win64
make
install
is that the correct order?
by Sveinar Søpler on Wednesday March 7th 2018, 10:03
So to make sure its working, you should download the 3.3 RELEASE source from: www.winehq.org/announce/3.3
Then download the wine-staging-release from: github.com/wine-staging/wine-staging/releases
Then follow what you write from pba clone :)
Tbh, i would not configure wine as a systemwide option, but rather (especially when using experimental code) use a installprefix and then use that to run wine. Easiest option to switch wine versions would be something like Lutris or Playonlinux.... but can do that via a script aswell. I posted a usable script you can adapt to your needs here: forum.winehq.org/viewtopic.php?f=8&t=30176 (Adapt this ofc to wow)
wine should then be configured with:
./configure --enable-win64 --prefix=/home/steve/wine-staging-pba-3.3
Replace ofc "steve" with whatever username your user have.. and by all means, call "wine-staging-pba-3.3" what you want.. The point being that your install would then be in that folder... and you can reference that as you see fit, instead of doing a system wide install incase things break and you need wine for some other program :)
by hirschhornsalz on Wednesday March 7th 2018, 10:48
From my history:
git clone source.winehq.org/git/wine.git
cd wine
git checkout tags/wine-3.3
cd ..
git clone github.com/wine-staging/wine-staging.git
cd wine-staging
git checkout tags/v3.3
cd patches
./patchinstall.sh DESTDIR=../../wine --all
patch -p1 < ../wine-pba/patches/0001-wined3d-Initial-implementation-of-a-persistent-mappe.patch
patch -p1 < ../wine-pba/patches/0002-wined3d-Add-support-for-backing-dynamic-wined3d_buff.patch
patch -p1 < ../wine-pba/patches/0003-wined3d-Use-ARB_multi_bind-to-speed-up-UBO-updates.patch
cd ..
cd ..
mkdir wine32-build
mkdir wine64-build
export CFLAGS="-O3 march=native"
cd wine64-build
../wine/configure --enable-win64 && make -j16
cd ../wine32-build
../wine/configure --with-wine64=../wine64-build/ && make -j16
I have only looked at it for a short time and it seems fast, but I haven't done any measurements.
by Sveinar Søpler on Wednesday March 7th 2018, 14:42
Compared from my earlier bencies, i did timetest 1 from Felblaze Ingress Crimson Thicket.
wine-staging-2.18
Felblaze -> Crimson: 44.4 avg fps
Crimson -> Felblaze: 42.6 avg fps
wine-staging-pba-3.3
Felblaze -> Crimson: 73 avg fps
Crimson -> Felblaze: 68.3 avg fps
Huge increase.
Btw. Any reason you don't patch:
0004-wined3d-Use-GL_CLIENT_STORAGE_BIT-for-persistent-map.patch
0005-wined3d-Experimental-support-for-persistent-buffer-t.patch
0005 i guess is mostly trying to fix overwatch.. so i guess its not needed for wow... Question should perhaps be: Does it hurt? :)
by hirschhornsalz on Thursday March 8th 2018, 16:03
by Simon Kristensen on Saturday February 24th 2018, 6:56
When I try to start with -d3d11 - the game wont start. It crashes instantly with the error message: World of Warcraft was unable to start up 3D acceleration
I have tried repairing game files. Deleting cache WTF and interface folders. Reinstalled wine. Tried different wine versions., 2.18 staging and 2.21 staging.
-d3d9 works fine, but no go with -d3d11
by Steve Ebey on Saturday February 24th 2018, 22:14
by Simon Kristensen on Sunday February 25th 2018, 12:57
by Yuki on Sunday February 25th 2018, 20:26
wined3d_dll_init The GLSL shader backend has been disabled
so I take enabling it that way is not the full deal..
by Yuki on Monday February 26th 2018, 16:40
by Tom B on Tuesday February 20th 2018, 16:57
I've been trying various things and made some interesting discoveries:
1. Going from "Windows 7" to "Windows 10" in winecfg nearly doubles the framerate
2. Surprisingly, setting __GL_THREADED_OPTIMIZATIONS=0 instead of =1 gives a 50% performance increase (and I'm not a 32 thread CPU so I'd expect it to have helped!)
3. Setting __GL_YIELD=NOTHING grants about ~5% fps improvement over __GL_YIELD= and about 10% over __GL_YIELD=USLEEP
4. Couldn't test FBO vs Backbuffer, Backbuffer causes odd graphics on the character select screen and I couldn't get past the loading screen
5. mesa_glthread=true had no effect (didn't expect it to on the nvidia driver but was worth a try)
6. Most in-game settings made little to no difference. The only one that had any noticeable effect on performance was view distance.
YMMV and obviously GPU vendor/driver will have an effect. But doing those two things took me from 15fps to 43 on a Threadripper 1950x/980ti with nvidia 390.25 driver at 3840x2160. These drivers alone gave me worse performance than earlier ones, there's a detailed thread over at nvidia devtalk.
by spaceman on Wednesday February 21st 2018, 10:43
by Tom B on Wednesday February 21st 2018, 14:25
__GL_THREADED_OPTIMIZATIONS=0 __GL_YIELD=NOTHING wine Wow-64.exe
The results will probably be completely different if you're not using nvidia but I was surprised that __GL_THREADED_OPTIMIZATIONS=1 gave a performance hit.
by Sveinar Søpler on Thursday February 22nd 2018, 9:19
Not really tested that much with __GL_YIELD, but some performance may be gained perhaps. I use a 4.15 kernel with PDS cpu scheduler, and i have a wild immagination that the "yield" part does not have that much to say.. Dunno.
I get better performance with __GL_THREADED_OPTIMIZATIONS=1, but i do not use a Threadripper, so could be something there too. :)
FPS in WoW is kinda impossible to meassure tho, but i guess if you were able to stand at a totally deserted place, or to a "taxi" benchmark from a non-populated place it can be used. I have several spots in dalaran i have 80+ fps, but in the middle of the landingspot on a busy saturday evening, its down to 25'ish... :) (WoW graphics settings to "7")
Still worth a test for those who want tho :)
I did find some performance increase with the config.wtf settings:
SET timingMethod "2"
SET worldPreloadNonCritical "0"
SET M2Faster "3"
SET timingModeOverride "2"
But as "per normal" in wow.. a "performance increase" is hovering around +/- 1'ish % for a setting. Unless you do something terribly wrong.. like setting WINEDEBUG=+all or something :P
by Tom B on Sunday February 25th 2018, 16:49
I've been having a lot of issues with the 390.25 driver as detailed here: devtalk.nvidia.com/default/topic/1029484/linux/-linux-mint-18-3-numerous-performance-amp-rendering-issues-on-390-25/2 so that might have something to do with it. I haven't tried WoW with an earlier driver, other games definitely worked better with the earlier driver, though.
I should have mentioned my methodology. I'm running at 4k, DX11 with mostly high settings. (View distance 7, seems to be the happy medium). I have an alt in Netherstorm which is practically devoid of other players, so I was just walking around one of the towns there.
Annoyingly, -opengl, which I was using a few years ago to play flawlessly, runs at a constant 60fps but has all sorts of texture corruption which makes it unplayable.
I'm very keen to see what happens when DXVK supports DX10 and we can use it with WoW. Might be the answer we're looking for.
by Sveinar Søpler on Monday February 26th 2018, 8:18
Could be graphics engine dependant perhaps. Not too many benchmarks that work too well on wine, so kinda hard to check. No benchmark using Warcraft engine either.
Benchmarking in WoW is kinda "impossible", cos a small variable makes a huge impact. I have tried to do "average" tests with looooooong flights and timedemo 1, and found very little difference.. when i tested. Ofc could be worth doing another round of tests tho. Changing settings like CSMT or other, and logging in to measure fps just by a "quick look" is kinda hard, cos if you are unlucky some random entity walks nearby and wham, those 2-3 fps you thought you gained... had nothing to do with it.
I have not really seen a 100% change (from 20 -> 40 fps) by ANY change in wine. Changing to windows 7, xp, 10.. no real change for me... but have not tried this with a clean prefix each time tho... so might be something there. I do have a old crappy cpu with DDR3 ram, so having GTX970 i guess i'm so cpu limited that nothing makes changes? Dunno... Get 25-30'ish fps in front of the "portal spot" in dalaran (where you land when you HS), but gets really close to 20 in a busy saturday. Several spots in Dala hits 70+ fps, and usually 40-60+ fps doing world quests... However if there are loads of ppl around, like when doing the portal weekly's i have dips in the low 20'ies when things are going on. DX11 wow gfx settings to "7" @1080p
Oh, and when it comes to wow in particular, even tho it theoretically supports multi-threading, it is more or less just two threads. Wine occupy more threads with CSMT, but even tho you see load on other threads it is not doing other than moving between threads so that looks like it is "real" multithreading. This means, especially for wow - core clock > threads. Ie. it is better with a 4.5GHz 4 core cpu, than a 3.5GHz 16 core. Wine does ofc not "help" this situation either... its kinda making the problem a tad worse.
by El.Finito on Tuesday February 20th 2018, 0:58
BUT, one tiny but unbelieable annoying thing is the follow... sometimes i run my Game-Character with A-W-S-D, sometimes just with the Mouse, Left and Right Click, And the Movement Method with the Mouse stops running the Character often, i still have hold my Mouse Keys but the Chararcter stops running. I´ve already changed my Mouse with a other, a New one.
By solving this last Problem for me, i would give WOW on LM 18.3 Platinum State but this apparent tiny Problem is so annoying that i thing about a System Change back to Windows, but i dont want it, i hate the Stone-Age Systems from Microsoft.
by spaceman on Wednesday February 21st 2018, 10:41
by Steve Ebey on Wednesday February 21st 2018, 16:27
by El.Finito on Wednesday February 21st 2018, 23:32
Has anyone a Idea how i can solve my Mouse Problem as i´ve written?
by Missy CHapman on Thursday February 15th 2018, 14:06
by Steve Ebey on Thursday February 15th 2018, 17:09
by Missy CHapman on Thursday February 15th 2018, 17:43
by Steve Ebey on Friday February 16th 2018, 8:22
by Sveinar Søpler on Saturday February 17th 2018, 7:43
by Sveinar Søpler on Saturday February 17th 2018, 15:50
www.wine-staging.com/news/2018-02-17-future-wine-staging.html
Now.. hopefully that does not mean wine will never have DRM support, or what is needed for games like World of Warcraft, but for now, there will not be a "quick fix" other than run existing wine-staging.
And as i said in my last post, DX11 works oki on wine-staging-2.18 in wow... and since i dont remember names or threads i answer here and there, DX9 in wow is bugged, and will NOT be fixed (missing ground effects) as DX9 will be gone come next expansion. My fear ofc would be that next expac - ie. World of Warcraft 8.0 - Battle for Azeroth some time in september, with changed graphics engine will be broken for wine-staging, and if wine-dev has not caught up, that sound you just heard was the fat lady singing...
by spaceman on Wednesday February 21st 2018, 14:02
by Simon Kristensen on Thursday February 8th 2018, 12:21
by Winkey on Sunday February 4th 2018, 10:11
by Simon Kristensen on Sunday February 4th 2018, 2:26
1-5 seconds after I login to a character. I am running -d3d9 but I really don't know if I'm running 32 or 64bit, as the checkbox option simply disappeared from Battle.net app.
The whole computer freezes, I can move my mouse cursor, but I can't do any inputs and I'll have to hold my power button.
If I try d3d11, the computer freezes already at opening WoW. Same happens when I run "wine Wow.exe or Wow-64.exe".
I can create a new character and run around for about 5min, then computer freeze again.
by Sveinar Søpler on Sunday February 4th 2018, 6:20
So, just to get the facts:
1. You are using a AMD card with Oibaf gallium nine (MESA) driver?
2. You are using wine-staging-nine 2.20?
3. You have not gotten a new kernel or gfx drivers of late?
There was a patch to the wow client when bringing the 7.3.5 version, where you would get a message about DX9 soon to be dropped. I have not tried with the dx9 option in quite a long while as it is bugged in missing some ground textures/effects that really fu**s you up in raids (standing in flames you cant see). So as of 7.3.5 i would say DX11 is the "only" way to play wow.
That and that they are dropping DX9 altogether the next patch + no longer supporting XP (This happened a while back tho).
Not the greatest of news tho, but wine-staging-2.20 (regular one) + "normal" AMD drivers should work. gallium-nine + wow at this point COULD be sketchy tbh.
by Simon Kristensen on Sunday February 4th 2018, 7:47
by Sveinar Søpler on Monday February 5th 2018, 2:23
What if you press CTRL-ALT-F1, will you get to terminal then? There you could do a "killall wineserver" and see if CTRL-ALT-F7 wakes up the desktop again.
Other tests might be if you run a openssh server or something, if you can connect in to the machine remotely and there do a "killall wineserver". If that does not work, nor CTRL-ALT-F1 or anything of that matter it might be some instability somewhere else.
Have you tested any native Linux gfx benchmarks to see if that is stable? Unigine Heaven/Valley/Superposition? Those tax the GPU rather well, and if you get a crash there aswell it could be a troublesome powersupply/hardware fault of some sort (if you are 100% sure no drivers/kernel/whatever has been updated).
by Simon Kristensen on Monday February 5th 2018, 9:29
[31.404401] [drm:dce_V8_0_afmt_setmode[amdgpu]] *ERROR* Couldn't read SADS: 0
[372.980820] [drm:dce_V8_0_afmt_setmode[amdgpu]] *ERROR* Couldn't read SADS: 0
But I am not able to type anything or go back to CTRL ALT F7 . Here the computer just freeze for good!
I have not tested any benchmarks, but I am able to play Heroes of The Storm on High graphics settings. And wow also runs perfectly on Windows 10, so no powersupply/hardware fault I think.
And I repeat I have played WoW on ubuntu for a whole week with no troubles at all. It just stopped working from one hour to another. I remember installing some Ethereum (crypto valuta) mining software, which I quickly uninstalled again, to make sure that didn't cause the problem for some reason.
by Sveinar Søpler on Monday February 5th 2018, 10:12
A: You changed the kernel
B: You changed the drivers
Very strange that it would "suddenly happen" tho, unless some sort of update has happened.
As i said previously, it is very strange that wine would hard-lock your machine like that in itself. That you cannot switch to terminal and type commands indicates something has gone horribly wrong (as indicated by those drm: [amdgpu] lines. Without being any sort of expert, my honest oppinion is that your computer is crashing because of some underlying problem with the AMD drivers.
What Ubuntu version and kernel are you running? 4.15 kernel is brand spanking new with quite a lot of amdgpu fixes from what i gather (and possible bugs ofc). Seeing as you dont have those issues in windows, i agree that it would probably not indicate a hardware fault, but more likely a driver malfunction of sorts.
by Simon Kristensen on Tuesday February 6th 2018, 9:57
After a reboot and another try, it froze just as I entered the world on my character, like before the kernel upgrade.
Think I will try out the 4.15.0 kernel later today. Btw thank you for all your help :)
by Sveinar Søpler on Tuesday February 6th 2018, 14:57
When you start it, it just runs in a loop even if you dont do the "benchmark" thing, so the GPU is tested. Do that with the Linux version first.. if you hard crash there you know for sure its not wine related :)
If it runs for 10+ minutes without problems with the Linux native client, you install it under wine and do the same.. if that hard-crashes after 2 minutes like things do in wow.. i would try the non-nine version of wine to see if it is some bug there perhaps?
benchmark.unigine.com/valley
"Superposition" is the newest and are OpenGL/DX11, so it would probably not work at all with wine-staging-nine version in "directX mode" + that the gui is rather bugged under wine.
by Simon Kristensen on Thursday February 8th 2018, 11:55
by Simon Kristensen on Thursday February 8th 2018, 12:22
by Simon Kristensen on Thursday February 8th 2018, 13:25
by Sveinar Søpler on Friday February 9th 2018, 8:00
Atleast under DirectX11 you get to see ground flames/patches/whatever that is missing in DX9... safer for your fellow raiders to not have to battlerez you 3 times every bossfight :)
by Björn Bidar on Friday February 9th 2018, 8:07
The missing ground textures are workaroundable by moving with the grp or with the boss that you attacking.
Even Argus HC works without issues.
by Sveinar Søpler on Friday February 9th 2018, 8:19
Its not WORSE than dx11, but its not really better either tbh. So, id rather run DX11 w/wine-staging-2.18, than DX9 with wine-staging-2.18 (or 2.20/21 for that matter). If it is very little to be gained by using dx9, id rather see the ground textures, even tho i probably should move around with the group anyway. Usually have 30-40'ish frames in raids, but with mass fights like the big weekly portal bosses where you have 40 ppl bombing the boss with spelleffects and whatnot, i do not have 40 fps. Seeing how ppl complain about the lag in the raidchat more or less leads me to believe that not EVERYONE of them are running wine either :D
wine-staging-git vs. wine-staging-2.21 "release" is the same. I (and others) have found wine-staging-2.18 to perform just a smidge better for wow 7.3.x in DX11 mode.
by Sveinar Søpler on Saturday February 3rd 2018, 7:16
Anyway, a box now pops up with "survey.exe has crashed". Is this some sort of data collection thing from blizzard in the gearing up towards switching to DX12 and the new Battle for Azeroth expac?
Also a couple of weeks now my battle.net client window is more or less bonkers when it comes to wow.. cant do the "repair" function or stuff like that. (Screenshot: ibb.co/eizkOm )
by Sveinar Søpler on Monday February 5th 2018, 10:38
Tried to install in a fresh prefix with both staging and 3.0 and 3.1 wine.. same buggy window for me... hmm..
by spaceman on Tuesday February 6th 2018, 10:04
Battle.net is not a great place wine-wise at the moment.
by Sveinar Søpler on Tuesday February 6th 2018, 15:00
That + battle.net generating loads of logs under your user profile regarding.. well.. loads of stuff.
by Winkey on Thursday February 1st 2018, 20:19
Deleting WTF, Cache and Interface did not help. Repair option at launcher did not help. Using no addons anymore.
Because of that I tried DirectX 11. Error still is there.
2) DirectX 11 brings another problem: The whole 3D world is very dark including player names and their health bars. The game interface itself has normal brightness.
Perhaps the fglrx driver of ubuntu 14.04 is too old?
So I switched back to DirectX 9.
wine-staging 2.21
ubuntu 14.04 32bit
using fglrx-updates graphics driver
Radeon HD 6670
by Björn Bidar on Friday February 2nd 2018, 0:07
Name : wine-staging-git
Version : 2.21.r0.g53290d2ec4-2
maybe its an issue not specific too wine or to your GPU driver.
by Winkey on Wednesday January 17th 2018, 7:38
The Launcher's preferences have no effect on this.
So, after closing WoW, I always have to terminate the "Blizzard Battle.net" process in Task Manager.
wine-staging 2.20
ubuntu 14.04 32bit
by Sveinar Søpler on Wednesday January 17th 2018, 8:07
by spaceman on Wednesday January 17th 2018, 9:15
I would actually recommend this, if only for the agent.exe, Battle.net Helper.exe processes.
by Sveinar Søpler on Wednesday January 17th 2018, 15:41
However, if you use a "pure" 64 bit wine (self compile with the --enable-win64 configure flag) it will just pop a couple of errors in your log about agent.exe being a "Bad EXE format".
by spaceman on Thursday January 18th 2018, 9:37
by Are on Wednesday January 17th 2018, 7:30
Error on 64 bit 3.0rc6:
"game failed to initialize" when i try to start wow
by Steve Ebey on Wednesday January 17th 2018, 8:24
by Mike on Sunday January 21st 2018, 7:27
by Steve Ebey on Sunday January 21st 2018, 8:13
by Tim Ryan on Sunday January 21st 2018, 9:29
by Mike on Sunday January 21st 2018, 10:17
by godson on Wednesday January 17th 2018, 5:07
This is on a 64bit version of wine.
by Steve Ebey on Wednesday January 17th 2018, 8:23
by godson on Wednesday January 17th 2018, 10:16
by Lewis Anderson on Saturday January 20th 2018, 7:04
by Steve Ebey on Saturday January 20th 2018, 14:45
$ winetricks
click on select default prefix, click ok
click on Change Setting, click ok
click the box for glsl=enabled, click ok
back out of winetricks by hitting cancel until you are back in terminal
if you compiled just the 64bit wine, you need to change to the /usr/local/bin and do ln -s wine64 wine so you can run winetricks
by Björn Bidar on Saturday January 20th 2018, 15:36
by Björn Bidar on Saturday January 20th 2018, 15:41
see here:
github.com/Thaodan/usenew/blob/master/doc/usenew.org#options-1
by Lewis Anderson on Friday February 9th 2018, 15:30
by MedGuard on Tuesday January 16th 2018, 22:52
by Joel Cool on Tuesday January 16th 2018, 14:55
Wine Staging 2.21
Ubuntu 16.04
by Joel Cool on Tuesday January 16th 2018, 20:00
by Sveinar Søpler on Wednesday January 17th 2018, 6:06
Did they change so that DX9 does not work at all, or just a "warning" that the support is ending some time in the future? Guess its just the warning...
Well, as i have posted before, atleast the reason why the did not bother with fixing ground effects with DX9 is there, and the reason they did not bother with OpenGL is cos of Apple Metal.
The only real alternative for wow is then DX11.. so lets hope some time in the future we can get DX11 performance for wine 3.x to the level DX9 was with Wine 2.0 :)
by ergo on Wednesday January 10th 2018, 3:09
Warning: Your current system will not be supported in future versions of World of Warcraft which will require a 64-bit operating system.
Warning: Your graphics card will not be supported in future versions of World of Warcraft, which will require a Shader Model 5 capable graphics card or better.
www.wowhead.com/news=280322/7-3-5-ptr-build-25826-updates-racial-tweaks-for-allied-races-increased-minimum-r
by Sveinar Søpler on Sunday January 14th 2018, 3:56
WoW works "ok" with DX11 as it is now tho, but the performance is so-so if you compare it to 2.0 and dx9 (pre CSMT "fix" that came with 2.1). If wine-devs would be interested in performance tuning, it could be nice tho.. so we shall see.
Hopefully wine-staging will be updated to work with 3.0 when that is ready, cos as it is now release wine does not work. And unless something has changed with rc-6, the vsync bug is still there for dx11.
by Björn Bidar on Sunday January 14th 2018, 4:02
Is this reported?
>WoW works "ok" with DX11 as it is now tho, but the performance is so-so if you compare it to 2.0 and dx9 (pre CSMT "fix" that came with 2.1). If wine-devs would be interested in performance tuning, it could be nice >tho.. so we shall see.
Is that tracked too? this will be critical for the next addon as Dx3d 9 is likely removed than.
I wish we collect money for or bug bounty or something.
by Sveinar Søpler on Monday January 15th 2018, 1:37
DX11 performance: Its nothing to "track". CSMT was reworked to a less "hacky" version when 2.1 was launched, and it was stated:
Since most of our users enable the CSMT because of the performance improvements (although it can also be used to fix drawing issues for specific games), here is one additional note. The main focus during our work was on correctness and not directly on performance. We included some new ideas to speed up the rendering but also left out some more experimental ones which were included in the old versions. The performance might therefore differ compared to Wine Staging 2.0
Now, DX11 did not work with wine-2.0, so it cant be compared in itself. DX9 w/wine-staging-2.0 is faster than DX11 w/wine-staging-2.1x simple as that. If the performance will ever be on par, i cant say. In windows DX11 in wow is usually faster than DX9 (atleast with up-to-date-drivers and capable hardware). Iv'e done many benchmarks with things like Unigine Valley and Unigine Heaven in wine, and from what i can say from that is that the DX11 performance in those benchmarks are ALMOST the same as native OpenGL performance when running the native Linux client... And that is awesome. Why World of Warcraft suffers that much i dont know, or for all i know Linux OpenGL performance just is that much worse performancewise than Windows and DX11. It is not unheard of to have fps problems in raids and the likes even under windows.
I know a DX11 -> Vulkan wrapper is being worked on, that hopefully and possibly will have a lot less overhead than the current DX11 -> OpenGL wrapper wine uses. Until then, i guess we will have to make do with what we got.
Afaik the reason wine-dev does not work with World of Warcraft has to do with some ntdll authentication libraries or something that wine-staging fixes. I must admit i have not tested wine-3.0-rc5/6 with battle.net, so this info might be totally off.. I have not seen anything specifically regarding battle.net in the patchnotes, but that does not mean it doesnt work... Cos with most things wine, fixing an obscure 2D game from 1996 might be the thing that fixes the latest battle.net client :) The performance of wine-3.0-rcx is sadly not on the same level as wine-staging. Unigine Valley DX11 is a slide-show with wine-3.0-rcx, so cant compare performance there tho.
by Björn Bidar on Monday January 15th 2018, 5:10
The fix was for the game (s) itself as they used the back to enable the anti cheat engine.
The patch required for this, is this:
github.com/wine-compholio/wine-staging/commit/f1b1baf057bd8bf7f22bfdf3f6d982effaeab42a
One thing I noticed while using dx3d11 on wow with wine that my gpu is basically idle.
I had never more than 40% load.
Is this intended or this the exact issue Here?
My GPU is an Nvidia GeForce GTX 1080ti.
by Sveinar Søpler on Monday January 15th 2018, 6:55
The game in itself is like that in windows too tho, so its a game issue that is possibly exaggerated by wine. The game engine is a rather old engine with patch-upon-patch but no complete rewrite, thus limited multi-thread capabilities ++. Even tho WoW should be capable of using 8+ cores, it really does not utilize fully more than 2 i guess. With CSMT and nVidia threading optimization (dont remember atm as im at work), the game will offload on different cores, but well....
As it is a mmorpg, lots of calculations, entity placements++ is done in CPU + rely on the server calculations and your bandwidth. This means that even tho you have powerful hardware, it really does not matter that much unless the servers push enough info for your computer to have something to do. Even spell effects and the likes i think is somewhat calculated using cpu and heavily rely upon server info. When a boss places a pool of fire on the floor, the servers have to calculate where that pool is, and keep updating whoever stands in the pool.. things like that. With 25 ppl, this info is sent to everyone, and the server have to keep tabs on where everyone is at all times. I suspect (as this seem to be the problem with many mmorpg's) that some sort of syncronization is made between clients to try to make stuff as even as possible for "everyone". Take Everquest (have not played in years tho) which is a super-old graphics engine, still wont push out 500fps on a new computer. Its a combination of different stuff... latency, cpu, server-calculations.
Yeah, i agree that regardless of this, you should have atleast 100+ fps at all times, but SOMETHING is preventing this even in windows. Wine does not help on the situation, as the fps is higher in general in windows :)
C
by Björn Bidar on Monday January 15th 2018, 7:02
I saw the same things as you said, althrough with metal at least on OS X they must had fixed at least something.
I really want to know what "SOMETHING" fixes this on Windows.
If we can help in anway than I would gladly help.
Maybe there's a way to debug this better, if possible to debug this on windows and give some vs. data.
by Sveinar Søpler on Monday January 15th 2018, 15:38
Loads of changes there tho, so i kinda gave it up as it is a HUGE patchset to implement.
Meh.. I hope 3.0 gets finished soon, so some proper coders can get to work on staging again :P
One should think that Wine would have a small interest in getting their software up and running on one of the worlds largest playerbases tho (WoW and Overwatch being hugely popular), but i guess its not important enough :)
by Björn Bidar on Monday January 15th 2018, 16:08
Look at the patch definition it depends on some patches.
>One should think that Wine would have a small interest in getting their software up and running on one of the worlds largest playerbases tho (WoW and Overwatch being hugely popular), but i guess its not important >enough :)
Maybe we could gather money on this or help in a way that this feasible.
by Sveinar Søpler on Tuesday January 16th 2018, 5:26
Got an idea to try rather than implementing patches on 3.0, i think ill try to patch 2.21 with the patches i believe get wow running 1 by 1, so i will know for sure what is needed before trying to implement those on the 3.0 source perhaps.
by Sveinar Søpler on Wednesday January 17th 2018, 15:51
What i did was to compare the wine-staging-2.15 source that have the same error as the 3.0-rcX source. I compared that with the wine-overwatch-2.15 source that works with wow, and found the following:
1. wine-staging-2.15 got the same error as 3.0-rcX
2. wine-overwatch-2.15 works
3. Difference between staging and overwatch is the aforementioned ntdll-x86_64_ExceptionInformation changes and quite a bit of wined3d changes and some minor stuff.
4. I applied ONLY the ntdll-x86_64_ExceptionInformation changes to wine-staging-2.15 and it worked.
5. Applying ntdll-x86_64_ExceptionInformation to wine-3.0-rc6 makes the error message go away, but crashes.
6. Difference between wine-2.15 and wine-staging-2.15 when it comes to wined3d, and d3d11++ is huge, and cant really pick what patch you need.
Conclusion: Most likely wine needs quite a few of the wined3d, and possibly d3d11 changes from staging. Since wined3d consists of like 20 or so patchSETS (with multiple patches in many of them), the task for ME as a non-coder is rather futile. A lot of the d3d functions are implemented, but i dont really "read code" that well, so...
Was worth a shot. Probably got to learn something, and got to test a new tool i liked for comparing changes.. "Meld" :)
by Panagiotis Apostolou on Monday January 8th 2018, 15:21
I have installed wine 2.4 (staging) (as stated in the about tab of winecfg) on ubunty 16.04 on a laptop with a dual gfx card (Intel + nvidia 820m)
Sorry if this sounds completely noobish but whatever combinations of options, when I run either Wow.exe of Wow-64.exe or from the launcher, all fail with "ERROR Game Initialization failed!". I just downloaded wow so I guess that makes it the latest version.
The bare minimum steps described here didn't work out but I'm using wine 2.4 instead of 2.21
Can someone be so kind to make a list of steps to follow that would be comprehensive for an "outsider"? I don't mind compiling things from scratch.
by Steve Ebey on Monday January 8th 2018, 15:52
github.com/wine-compholio/wine-patched/releases
As that page shows, 2.21 is the last release that is patched, and ready to be compiled on your machine. I am running Wine Staging 2.18 as that seems to give the best performance in directx 11, since blizzard has dropped DX9, and if you run DX9, the texures for certain ground effects are not visible.
by Panagiotis Apostolou on Monday January 8th 2018, 16:22
Anyway building 2.21 from the link you provided. Guess I should remove any existing versions before installing the 2.21
by Steve Ebey on Monday January 8th 2018, 21:21
by Panagiotis Apostolou on Tuesday January 9th 2018, 12:22
You have been disconnected (BLZ51900007)
When I run the launcher I get the login screen appears but when I login I get error:
Could not log to Battle.net
More help: us.battle.net/support/en/article/24014
And there is an option to continue offline When I press continue offline I get the error:
Failed to create a graphic context.
If you receive this error again, check that your graphics drivers are up-to-date and that your system meets the minimum requirements.
More help: BLZBNTBNA0000000A
This happens with both wine and wine64. Tried it with both Intel gfx and nvidia (proprietary 340.102)
by Panagiotis Apostolou on Tuesday January 9th 2018, 14:57
err:secur32:SECUR32_initSchannelSP TLS library not found, SSL connections will fail
Although I have installed libgnutls30, libgnutls-dev and libgnutls28-dev (i386 too)
by Panagiotis Apostolou on Wednesday January 10th 2018, 13:32
I get this log on the command line pastebin.com/kLqZ2NXY
by Sveinar Søpler on Tuesday January 16th 2018, 6:55
There is a LOT of libraries++ to install to compile it tho, and you can see that when you run the .configure script. If you get things "missing" you can still compile wine, but may be missing important stuff.
Parhaps run the ./configure script and post the output here? Last 15-20 lines or so :)
by Sveinar Søpler on Tuesday January 16th 2018, 6:49
I use PlayOnLinux that got those nifty icons and easy shortcuts to bring up winecfg, regedit++ and i guess they are running "wine" as default to launch those, so making a symlink is required with a wine64 only install.
When it comes to wow, it seems as even tho you launch the wow-64.exe file directly, it will launch agent.exe in the background. This sometimes hamper performance. Agent.exe looks to be a 32-bit program, so by using a pure wine64 install, agent.exe is prevented from running in the background. (debug log indicates wrong binary format for agent.exe in a wine64 install).
by Jay Greenfield on Saturday January 6th 2018, 0:19
Have you ever tried Wowmatrix? I run it with Wine 2.21-Staging to get all of my addons. It runs just fine minus an error message I've seen pop up upon closure, however, this doesn't affect my addons or the use of the application. DBM and Healium are on there among junk sellers and repair.
www.wowmatrix.com/faq/alternate-download
by Björn Bidar on Saturday January 6th 2018, 0:24
First Wowmatrix has a native version, which is the only good thing about.
I dont trust it, it redownloads addons done by curse and just steals traffic from devs.
If you want a native app try lcurse.
by Jase Whipp on Monday January 8th 2018, 8:10
by David Eriksson on Wednesday December 27th 2017, 7:48
wine-gaming-nine from aur 2.21 staging .
With nine patchet and dx9 was really a winner. 60+ fps in dungeons .
Noticed that Nvidia card is better on native apps - My chromebrowser are loading pages faster etc etc
So if you are on linux and want a good cheap gaming card i must recommend the rx550 4gb or better . My cpu is an amd-8350 8 cores 4 ghz and i have 16 gb ram . Sorry for my bad English .
by Roo on Tuesday December 12th 2017, 14:49
Lately, since with Wine 2.20 and so, I've had an issue where top right quarter of my screen has been completely void of certain spell effects that go on the ground. They just disappear if you turn your camera, and show normally in the other 3/4 of the screen (well, normally, with DX9 they're kinda single-colour pools, but they can be seen). So, depending on where you're facing, you might be standing in shit without noticing.
Anyone else seen this?
Wine 2.15 with overwatch patch doesn't have this issue for me. Is it possible one of the patches was missed or something?
Also, I've had pretty stellar FPS with Gallium Nine. 8) I highly recommend trying it, if performance is an issue for you. It's no DX11 though, but that doesn't really work for me that well anyway atm so it's by far the best way to run the game under Linux from what I've seen.
by Sveinar Søpler on Sunday December 17th 2017, 6:25
Ground effects works in DX11, although sadly with horrible performance compared to Wine 2.0 and the old CSMT staging patches.
The ground effects is possibly due to some changes in the 7.3 client, but since DX9 is relatively underused for Windows pc's, i guess its not that much of an issue. They did a fix for the mac client regarding this and the OpenGL backend:
us.battle.net/forums/en/wow/topic/20758847141?page=4#post-80
us.battle.net/forums/en/wow/topic/20758687941?page=2#post-32
What you can test is to go to that spider spot in Antoran Wastes (www.wowhead.com/npc=126115/venorn) When i use DX9 i cannot see the green "fel pools" on the ground from the dripping green stuff, but when i use DX11 they show up fine. There are loads of similar effects that miss in raids and other places, but this is easily reproducable. Try with 2.15 DX9 vs. 2.20+ DX9 and see if there is a difference? If there is, its definately a Wine bug.. and for all i know, the "windows people" complaining about this might just be wine users not admitting they use wine/linux cos they know they won't get any help that way? :) That would be awesome if it was the case, cos then the 2.0 client could be fixed for DX9 and we all could play with double the fps on nVidia cards :) (Staging-nine ofc benefit too).
by Sveinar Søpler on Sunday December 17th 2017, 6:36
Be happy to give it a go if someone can post 2.15-staging source w/overwatch patches tho :)
by Steve Ebey on Monday December 18th 2017, 9:26
by Sveinar Søpler on Monday December 18th 2017, 17:00
I dont have windoze installed, and it has more or less just become a stupid hardheaded thing for me not to do so.. But yeah, i have before, and if things get too bad, i probably will again - dualboot.
One other option i might consider is to get a newer motherboard and cpu that support VT-d with pci-passthrough so i can run QEMU with native drivers. Its somewhat of a hassle, but probably doable :) Running a VM of Windoze is aaaaalmost as bad as dual-boot tho, cos there is some stuff with gpu being bound to some driver or whatnot so you have to load some kernel modules and stuff.. well.. havent studied too much.
Lets hope 3.0-staging will be near what 2.0-staging was for DX9.. although i dont think we will ever get there again with DX11, as the GLSL translation needed for DX11 is too slow.
by Siren Watcher on Tuesday December 26th 2017, 5:16
by Sveinar Søpler on Tuesday December 26th 2017, 6:43
Perfect viewable result of this DX9 texture bug. Now to convince blizzard to fix it :)
by Mybrid on Sunday December 3rd 2017, 15:21
I just thought I would share some of my experience of getting Warcraft to run after my wine installation set to WinXP was blocked. I had to upgrade where the Wine 2.21 allows one to set Win10 as the Windows version.
# Overwatch patch notes for new DRM in Google search. My searches on how to upgrade form a WinXP wine return a bunch of Overwatch patch pages at the top of Google search for new DRM coee. Overwatch patch has been incorporated into Wine since 2.1 so is on longer needed. Just use wine 2.1 or higher.
# Battle.net Launcher.exe: I've been stuck for weeks on not being able to log in because either the 'Login" button would not display or after log in the application crashed. Turns out I needed to download the very latest installation client from Warcraft. Something in the latest Battle.net.exe works but previous versions did not.
# No install. I did not install Warcraft as part of the WinXP - Win10 upgrade of wine. Warcraft is a huge download. I backed up my 'Program Files (X86)" folder and retained all the Warcraft folders.
# Battle.net installer will find an existing version when hitting the "Install" button after downloading the latest Battle.net.
# Warcraft window did not display and eventually kept crashing with "Bad Window ID". I guess the last time a played months ago must have been with a different X config. In the Cinnamon Window manager I set the Warcraft window to "Visible in All workspaces" and this fixed my problem.
# I had to use "winetricks" and install Directx 9 because my Warcraft of WinXP was still configured to Directx9.
by Sveinar Søpler on Thursday November 23rd 2017, 14:40
DX11 runs fairly ok. Not huge fps, and some dips in huge aoe fights (world bosses and such), but overall worth it with functioning ground effects. Have not found any evidence Blizzard plan on fixing ground effect bug in DX9, atleast not yet.. and seeing as they have said XP is no longer supported i guess most system able to run WoW have some sort of DX11 functionality, as they will atleast use Windows 7 or newer. No problems averaging 35-40 fps running around Argus doing dailies. Sure, having 150+ would be ideal, and you can almost do that in DX9 mode, especially if you use the 2.02 patched branch.. but at the cost of missing loads of ground effects vital for raiding :)
So.. as a summary what i have as settings picked up from posts in these threads, and some experimenting on my own.
I compile wine-staging from source with GCC 7.2.0. I use the following configure string before compiling:
./configure CFLAGS='-march=native -O3 -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --enable-win64 --prefix=/where-you-want-binaries-installed-if-you-dont-want-syswide
This will produce a 64 bit binary ONLY, so you have to make a symlink in the /bin folder of your installed folder:
ln -s wine64 wine
to be able to run winecfg and such. AND it will not run battle.net app (or any other 32 bit binary). This means if you do what i have done, you need to swap between pre-compiled wine-staging-2.21 for your distro whenever you need to patch or similar. (I use PoL to easily switch versions tho.. other solutions is also available). I have found that if you run a multilib 32/64bit, wow MAY launch some "agent.exe" in the bacground for some reason, and that does sometimes suck resources.
Winecfg i have set up with:
Windows version: Windows 10
No library overrides
Enable CSMT
Enable VAAPI
Wine settings in PlayOnLinux gui:
GLSL Support: Enabled
Direct Draw Renderer: OpenGL
Video memory size: 4096
Offscreen rendering mode: Default
Render target mode lock: Disabled
Multisampling: default
Strict Draw Ordering: Disabled
Debug flags: -all
I have the following tweaks:
export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SYNC_TO_VBLANK=0
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
export STAGING_RT_PRIORITY_SERVER=90
I run the 64 bit wow client from a 64 bit wineprefix.
The following settings in WoW configfile /WTF/Config.wtf
SET worldPreloadNonCritical "0"
SET processAffinityMask "255"
SET gxTextureCacheSize "3070" (Depends on your gfx card.. other tips may be 2047)
SET gxApi "D3D11"
Ingame graphics settings is set to "7". VSYNC off, tripplebuffer off. I run "Windowed mode" (Because i have dual screens)
I have a nVidia 970 card with 4GB vram. Did some testing with xorg.conf, and actually found that for ME the best setup was with ForceFullCompositionPipeline=Off (metamodes), although it MAY at times be some tearing when browsing with Firefox, although the new Firefox seems better at that. Using nVidia binary driver: 387.12
This depends on your distro i guess, and drivers and whatnot. Maybe wow runs utter crap for someone using these settings, maybe not. If you get a better result, feel free to post your findings :)
Whenever you change wine version, or nVidia driver you should clear out the following folders:
$home/.nv/GLCache (nvidia shader cache folder)
/wowfolder/Cache (World of warcraft texture cache - seemingly rebuilt if you change gfx driver or wine version)
When you clear this, you WILL have stutters a bit.. but after zoning around and playing a while the textures/shaders will be compiled and saved to disc for smoother gameplay later.
by Sveinar Søpler on Saturday November 25th 2017, 16:30
Project is pre-patched with what i have tried my best to fix the wine-staging-2.21 patches. Slackner will no doubt do a WAY better job + add something more when the real 2.22 wine-staging is commited, but for now it seems to run :) PS. Use at your own peril!
github.com/SveSop/cyberwine.git
Once downloaded, configure with:
./configure CFLAGS='-march=native -O3 -fomit-frame-pointer -pipe -DWINE_NO_TRACE_MSGS -DWINE_NO_DEBUG_MSGS' --enable-win64 --prefix=/where-you-want-binaries-installed
PS. the above will only produce a 64-bit binary, so dont forget to do the ln -s wine64 wine in the /bin folder before running anything like winecfg or the likes :)
by Steve Ebey on Wednesday November 29th 2017, 20:52
by Sveinar Søpler on Wednesday November 29th 2017, 23:36
Havent they more or less stopped the curse client? And now use the Twitch app? More or less the same i guess :) I havent tested it, as i only run 6-7 addons and manage them manually.
Wow is not a amazing performer in windows either, as its very cpu bound when there are many enteties around, and the graphics engine is rather old and outdated. Now that they officially are ditching XP, one may hope they perhaps develop a updated engine for the next xpac, with support for Vulkan :)
by Steve Ebey on Thursday November 30th 2017, 1:27
I would love to see vulkan or even native opengl support in WoW, and would love a true linux client also. Not sure if any of that will ever happen. I plan to examine wine source code, to learn what I can about directx. specifically as it pertains to 3D rendering, in hopes that I can come up with a decent implementation to improve the performance on Linux.
by Sveinar Søpler on Thursday November 30th 2017, 3:41
DirectX9 is rather bugged atm with missing ground textures, and chances are that they will more or less ditch DX9 support altogether is imo rather high, as nothing older than Windows 7 is supported "officially". Win7 and newer all have DX11 support, and i suppose if you have an old/non dx11 graphics card, you have troubles playing wow anyways.
Vulkan MAY be an option.. perhaps the most im willing to go in terms of wishful thinking tho :) Atleast with Vulkan support, it could be a lot more performance to gain from Wine as Vulkan Vulkan would be a lot less work than DirectX11 OpenGL as it is now. Wine 3.0 supposed to be right around the corner with possible DX12 Vulkan, so interesting times. The marketshare for ppl using Linux exclusively to play WoW is so little, that even considering developing that as a TRUE working project will 99.9% never happen.
My projections: Blizzard will ditch DX9, tune the graphics engine for next xpac to support DX11 and DX12. We will have the same situation we had with limited DX11 support a year back with Wine, and had to fall back to DX9. Now DX11 works, and with a new client the new "fallback" for us Wine users will be DX11, with improved DX12 support during 2018 :)
Not really sure how many that use Wine to play WoW tho.. but from posts on this forum i guess its below 10 :P And using Linux exclusively without dualboot at all? Hah.. like 2? :)
by Dox on Sunday December 3rd 2017, 10:00
Just for the record, I'm still using Wine 2.18 for DX11, compiled with -march=native -O2, since it seems to work better then later versions fps wise. Also there is some bug with mouse from 2.19 that make it harder to turn camera for mouse turning.
I asked in the forum if there is more speed increase incoming, but except for a weird reply from someone that didn't read my question it seems, still no reply. Need to find out if we should bug report the fact that WoW with DX11 simply doesn't CPU for more fps. If it is a bug, perhaps it can be fixed and we actually end up with workable fps.
by Sveinar Søpler on Sunday December 3rd 2017, 16:26
Im currently fishing for a official reply from Blizzard regarding DX9 support, but probably wont get an answer.
When it comes to cpu load vs gpu load, its not ONLY a wine issue. This problem is somewhat the same in Windows aswell, but i havent run wow with windows in quite a while, but this WAS a problem, and from searching different forums this is still a problem. Ppl with 1080 cards getting 20-40% gpu load, and 30 ish % cpu load.
The wow gfx engine is a WC3 engine thats been patched and tweaked each expansion, but have limited multithreading capabilities. Give that + that a LOT of the "world" things is all done in CPU, it does not help if you have a overpowered graphics adapter.
Wine ofc makes this "problem" worse tho.
And yeah, i DO agree with you that they could/should bring some of the tweaks from 2.0 CSMT back, but i have a sneaky suspicion that its not as easy as a couple of lines of "tweaks" as 2.0 does not work at all with DX11. DX11 have some other ways to do stuff, and ive tried to post regarding the different way that DX11 detects vram vs DX9.
There is little activity on the wine-staging these days, as its still not officially updated for 2.22. Perhaps this is because Wine 3.0 is around the corner? I think i read some comments about "late november" as a estimate some time ago, but dunno.
by Sveinar Søpler on Monday December 4th 2017, 8:59
I wonder if this has anything to do with SM4 pixel shaders for GLSL 4.4 that came in 2.20 (i think)? Did you compare between 2.18 and 2.19?
Interesting anyway :)
by Sveinar Søpler on Wednesday December 6th 2017, 14:55
2.18 does indeed give better fps in WoW.. no doubt.
I also benched Unigine Heaven benchmark under wine with all the staging from 2.18 -> 2.21 and it was a decline in score each release for some reason. However it does not really give so large a difference than it does in WoW, so there is something going in there i guess. It COULD have to do with more cpu usage? WoW is a lot more cpu dependant than Unigine Heaven tho, and rely upon a lot more stuff being calculated.. Heaven benchmark are able to load my 970 to 100% when running tho, even without AA.
From what i tested yesterday, i have no real idea.. I have tried to make some sense to the patch differences between 2.18 and 2.19/2.20 and maybe think of something that would mess up wow.. but cant really come up with a better idea than the SM4 patches from 2.19 -> 2.20.
2.18 fixed the vsync issue (able to disable it), and thats imo a must.. so anything older is not good.. And anything newer seem to perform worse for WoW.
Status as of now:
2.0.2-staging w/DX9 and overwatch patches ref. Dox = Best performance by far.. but wow is plagued by the missing ground effects bug, so kinda suck to have to switch wine versions depending on encounter..
2.18-staging w/DX11 = Better performance than 2.19+ for some reason.
Can't submit a bug to the Wine dev's cos a general "Performance sucks" im pretty sure will be ignored :)
S
by Dox on Wednesday December 6th 2017, 17:24
I'm staying on 2.18 for now. I really hope we get some more performance soon, I doubt it will happen. You should try the bug report thingie!
I figure I see you posting in Xanmod forum. Personally I stay away from PDS-mq kernels since they don't play nice with OW (complete freeze). So I was on an old 4.13 that still had CFQ. However, since I saw that post about PDS-mq vs MuQSS, I'm now using 4.14.4-xanmod7 with MuQSS now, while setting it to throughput. I think it has gotten me some more fps, and it works nicely with OW aswell.
by Sveinar Søpler on Thursday December 7th 2017, 13:59
I have quite a bit better performance with 4.14.2-xanmod4 and PDS-mq than with 4.14.4-xanmod7 and MuQSS in wow tho, and have tested a few tweaks from Alexandre without any real change. Will see if i can convince him to maybe put up a dual repository for custom choice perhaps :)
There should be a test-site like Phoronix for wine that would show some differences between the wine versions.. Or something like that. Benchmarking in WoW is not that easy as it is not replicable due to so many external factors.. let alone hoping that any of the wine developers play wow :) Will look into it..
by Dox on Thursday December 7th 2017, 16:44
by Dox on Thursday December 7th 2017, 18:04
by Sveinar Søpler on Friday December 8th 2017, 8:18
Worth testing indeed :)
CFQ kernel will perform better i guess, but afaik the MuQSS or PDS is not really about performance but more for interactivity. Like if you compile wine in the background while surfing/watching youtube videos or things like that. I also use simulationcraft to score gear i get, and have set it to 6 cores when i calculate... the difference between PDS, MuQSS and CFQ is noticable if you run it while playing :)
You mention you load all 4 cores and no HT.. does that mean you have disabled HT? PDS seem to not put that much strain on HT cores, where MuQSS seem to put equal amount of load on HT/Real cores.. So if you have disabled HT, it might be worth testing?
by Dox on Friday December 8th 2017, 18:23
I don't have HT, I bought my i5-4670k especially because of that. I was going to overclock it (and I have a 24/7 OC on air of 4ghz on all cores for the past 4 years now). And HT aware schedulers are (were) rare, so it can lead to slowdowns.
Anyways, lets talk game here, and kernels at Xanmod forums. (Linux_Gamers_Group on Discord will also work).
by Sveinar Søpler on Sunday December 10th 2017, 9:07
Tested by turning off my HT cores for WoW, but seems a bit worse for performance for me.. but then again, i have a much older CPU than you, although it runs @ 4.2GHz overclocked (And has done for many years).
When it comes to Wine versions, i agree that 2.18 seems the smoothest for WoW as it is now, and that 2.21 actually is noticably slower. 2.22 that i patched with staging myself after some fiddling, i guess is in the state of "cant really be trusted" perhaps.. Dunno.
Started to TRY to patch 3.0-rc1 with the staging patchset, but waaaay too much work for me atm, especially since im rather clueless to what all the code does. Sometimes the implemented patches to main looks a bit different than the patch from staging too, so its more or less (for me as a non-coder) just guesswork if its implemented or not.. extremely so now with 3.0-rc1 and all the work that has been done.
And.. 3.0-rc1, does NOT work with Battle.net/wow without the staging patches. Perhaps some day staging will catch up and it will be worthwhile to test 3.0, but as of now, ill stick to 2.18 for DX11.. unless ofc Blizzard decides to fix the ground effects in DX9 (would be preferred and get back to 2.0.2)
by Björn Bidar on Thursday November 30th 2017, 0:07
by Steve Ebey on Thursday November 30th 2017, 1:17
by Björn Bidar on Thursday November 30th 2017, 1:25
Lcurse can update add-ons from git repository's.
by Steve Ebey on Saturday December 2nd 2017, 8:52
by Björn Bidar on Saturday December 2nd 2017, 9:00
I for myself use a VM with windows.
by Steve Ebey on Saturday December 2nd 2017, 9:38
by Björn Bidar on Thursday December 7th 2017, 0:00
But maybe ask at #wine-staging
by Brian McCarthy on Sunday January 14th 2018, 12:44
I have been using lcurse for over a year, not always perfect (it did break for a while when curse changed their website, but fixed now) but gets the job done without dual boot or VM usage. I don't think it detects your currently installed addons though if i remember correctly, you have to manually enter them into lcurse to get started. (this doesn't break your existing addons, its just more of a first time use annoyance)
by Harald on Monday November 13th 2017, 4:37
And the link to the solution in english is eu.battle.net/support/en/article/12706.
by John Lang on Monday November 13th 2017, 2:46
I have tried reinstalling wow, using almost all the guides i can find, and even a few different wine versions, but can't seem to get past it. I dunno, if it something i am doing wrong, not installing something, not configuring wine properly or what it is, it is really frustrating as i have friends who play, and i can't join them.
Please help me if you can :(
by Steve Ebey on Monday November 13th 2017, 7:51
6881 to 6999
3724 to 3724
1119 to 1119
6012 to 6012
4000 to 4000
6112 to 6114
i did not have to open the firewall in my fedora, but you might need to open it in your linux distro. hope this helps.
by John Lang on Monday November 13th 2017, 14:17
I tried that on my router, and still stuck on Retrieving realm list.
by Peter Anderson on Tuesday November 14th 2017, 14:05
I solved it by adjusting the MTU on my PC network interface to 1460 (was 1500). Also adjusted the MSS to 1420. No problems with connectivity since then.
by Coonable on Wednesday November 15th 2017, 21:12
In a terminal:
ifconfig eth0 mtu 1460
I
by Harald on Sunday November 12th 2017, 10:22
Debian stretch here with 2.20 staging.
Only had a little problem during installation with Battle.net-Setup.exe, don't think I saw it here. If I'm not alone on this, this worked : eu.battle.net/support/fr/article/12706
P.S : I'm new here, but thank you for all the work done to be able not to have double boot :)
by Sveinar Søpler on Wednesday October 25th 2017, 9:56
I get a crash and no image when starting now... Starts in both DX9 and DX11 mode with 2.19-staging tho, so i guess some sort of tweak was done? Anyone else having troubles launching with Dox's patched 2.0.2?
C
by nicola manca on Thursday October 26th 2017, 10:03
I tried 64/32bit and dx9/dx11, also in combination with different windows version, no change.
any help?
by Sveinar Søpler on Saturday October 28th 2017, 8:25
C
by nicola manca on Saturday October 28th 2017, 15:55
My problem still persists, after character selection the loading screen stay stuck at 70% and then I got disconnected with that error code :(
btw, no matter if I use 32bit or 64 bit or dx9/dx11
by Björn Bidar on Saturday October 28th 2017, 17:10
by Sveinar Søpler on Sunday October 29th 2017, 11:15
Guess its the same for me vs. the 2.0.2-staging from Dox that he can use, and i cant. Perhaps some settings that comes to play? Or some random library?
Btw. do you launch it from the battle.net client, or from the Wow-64.exe command line? I launch mine directly by running the Wow-64.exe file with -d3d9 commandline option. I use PlayOnLinux to manage the shortcuts and launcher options described in earlier threads here tho. GLSL=Disabled when i run dx9, but have to enable it to run dx11.
C
by Sveinar Søpler on Sunday October 29th 2017, 11:34
C
by Björn Bidar on Monday October 30th 2017, 11:20
What I wanted to say is don't over optimize and enable everything.
by nicola manca on Tuesday October 31st 2017, 6:52
Thank you for your help, but unfortunately, so far, it is still not working.
Actually I didn't changed anything apart directx, architecture and win version combinations. Just after the patch of last wednesday it doesn't finish the loading to enter the world. That's quite frustrating :S
I also tried to switch the optimize network stuff, but didn't changed anything. How can I try to modify the cache size?
thanks!
Nicola
by Sveinar Søpler on Tuesday October 31st 2017, 9:32
This you modify in the "Config.wtf" file (Found in your /WTF/Config.wtf) Numerous other threads for windows how to find that file tho... So you should be able to find the same structure under your wineprefix folder.
Add this line at the top:
SET gxTextureCacheSize "2047"
Depending on the vram you have ofc.. Dox found this to work the best for him on his 4GB 970 card... I personally actually find 3070 to work the best for me, but it kinda depends on vram/ram and overall graphics setting (I use "7" on the graphics slider ingame). What this does is tell WoW how much ram it can use.. Wow for my settings tend to use 1400-1800'ish vram, but depends on where you are++. Tuning this will help improve general "stutter" when turning around and such. Do a google search for gxTextureCacheSize and read what ppl write there is a good start.
Another tweak i use is to add:
SET worldPreloadNonCritical "0"
in the same file. This allows for a LOT faster zoning. This helps for random DC's when zoning.. like HS to Dalaran on a populated night had a tendency to DC me or just take a lot of time.. Same for a friend of mine using Windows.. Worth a shot :)
The usual suspects when troubleshooting wow is the same as for windows, as i think it MAY be something else than wine that is causing problems... as i take it "finish loading to enter the world" means you have already passed the character select screen.. ie. graphics are already loaded and operational. Usual suspects: addons. Also you can try to delete the Config.wtf file altogether and just add the two lines i typed above.. This way you have reset your config.. You have to set up graphics++ again, but worth to check if you can zone in then perhaps.
Sveinar
by nicola manca on Thursday November 2nd 2017, 4:39
I tried to install windows 10 and the game loads perfectly. I thus suppose the problem is something related to the linux/wine environment.
I use Debian stable 64bit, just reinstalled.
I also reinstalled WOW64 bit in a fresh playonlinux container using the following steps:
- create a 64bit container with wine-2.19-stagin
- winetricks corefonts directx9 vcrun2015
- set windows version 8.1
- launch battle-net setup
- launch Wow install
- disable streaming from battle.net control panel
The loading screen now gets stuck at 90% instead of 70%, it's an improvement but not enough.
Maybe I miss some libraries, but I don't see any relevant error from the playonlinux 'debug' mode. How can I investigate this?
Am I the only one experiencing such problem?
thanks for the help!
Nicola
by Sveinar Søpler on Thursday November 2nd 2017, 9:16
eu.battle.net/forums/en/wow/topic/17613764712?page=58
58 pages long.. SSD helps a lot, but as you say, you installed windows 10 (assumably on the SAME hdd as your Debian install?) without problems..
Things to try xept actually buying a SSD if you dont have it (i have a SSD with wow installed tho..)
1. The aforementioned "tweak" in the Config.wtf file:
SET worldPreloadNonCritical "0"
This will let you enter the zone, and load things "on-the-fly", although maybe causing stuttering after zoning in...
2. You COULD try a different kernel I/O scheduler.. WineHQ recommends (someplace that i have read it.. ) the deadline scheduler
Do
cat /sys/block/sda/queue/scheduler
to check what you are running now (assuming sda is the disc where wow is installed.. change for sdb-sdc++ depending on your setup)
sudo echo deadline > /sys/block/sda/queue/scheduler
to change the active scheduler "live". Not sure how you change it permanently for Debian, but for Ubuntu you can do it by udev rules, or just create a script that do it when you want to play, as deadline is possibly not the very best for regular desktop usage.
Sveinar
by nicola manca on Friday November 10th 2017, 3:35
so far the only solution was to copy the windows installation (win10), it works under wine 2.19-staging both on the SSD and on the HDD (I've 2 hard drives). I tried to install in wine setting win10 from the beginning, but apparently I cannot install vcrun2015 this way. I will make some more test changing the wine configuration during the installation, or maybe comparing the two folders.
by Sveinar Søpler on Friday November 10th 2017, 7:23
by nicola manca on Friday November 10th 2017, 7:34
by Sveinar Søpler on Friday November 10th 2017, 7:48
Theoretically unless something is damaging the binary .WDB files when downloading from the client, the install should be 100% identical, but sometimes shit happens and that is why Blizzard made the repair tool in the first place :) The AddOns folder containing your addons is one of the first troubleshooting things blizzard would ask you to clear out, the other is the WTF folder, as sometimes the settings may crash the client. Now on a fresh and new install, the Config.wtf is empty, so why it would cause an error is beyond me, but if you copy the WoW folder over, and it works without a hitch, it may be some obscure thing you forgot you disabled or something? Like previously suggested IPV6 disabled or something like that.
You could try to just copy the Config.wtf file over from the working install -> the non working one and see if thats enough?
This is ofc assuming you are using the same wine-prefix for both your tests, or atleast have identical settings in both winecfg and whatnot..
by MedGuard on Tuesday October 31st 2017, 5:10
Ubuntu Mate 17.10, wine 2.19-devel
by Sveinar Søpler on Tuesday October 31st 2017, 9:35
See my answer above..
SET worldPreloadNonCritical "0"
Is worth a shot.
If it is just a wine error/no graphics or similar, then it is perhaps worth it to twiddle around with different OS versions in wine aswell as dx9/dx11 and GLSL settings++ in wine.
Sveinar
by MedGuard on Tuesday October 31st 2017, 10:26
As for the hang of the game, the click on "creating a new character"...
by MedGuard on Wednesday November 1st 2017, 3:50
by Tekmad on Monday November 6th 2017, 5:12
by Björn Bidar on Monday October 23rd 2017, 13:31
I'm not sure if this is a wine bug.
Has someone else the issue?
by Sveinar Søpler on Sunday October 22nd 2017, 15:30
Any chance or even a point getting this to work with the pre 2.1 CSMT hack-patching that makes DX9 run almost as it should do?
C
by Dox on Monday October 23rd 2017, 7:33
My repo is a fork of Gamax, which ultimately is based on wine-patched. I don't have time this week, but if I have time this weekend, I'll see if I can rebase my commits onto Wine 2.0.3.
by Sveinar Søpler on Monday October 23rd 2017, 12:27
In Windows, DX11 performance in WoW is a tad better than DX9 from what i remember, so one can only hope Wine some day gets there :) I guess Wine 2.1x is more for functionality rather than optimizing for performance when it comes to DX11..
C
by Dox on Wednesday October 25th 2017, 9:01
Getting this error: Required library "USER32.dll' is missing export 'SetPhysicalCursorPos'
This isn't implemented till commit "2e9ca4626e2bedb5b8a0123a1c70d591f5e9d57c" on may 15th of this year. So newer wine versions will work. I'm going to fork wine-staging, make a new branch based on tag 2.0.3, rebase the commits in wow-2.0 repo on top of them, and cherry-pick this commit as well, to see if I can get it running again.
by Dox on Wednesday October 25th 2017, 9:13
by Dox on Wednesday October 25th 2017, 11:59
github.com/IngeniousDox/wine-wow-2.0
Just to be clear: I'm not going to work on rebasing it onto wine-2.0.3 + 2.0 staging. I'll leave that for someone else, if they really need it. Though IMO it shouldn't be. If we need any of the bug fixes, you can just directly apply them to the wow-2.0 branch.
by Sveinar Søpler on Wednesday October 25th 2017, 12:40
Gonna give it a whirl and see if its stable.
So, you picked patches from the 2.0.3 source commits and applied those BEFORE 2.0 staging? Found that spot you linked a while back to be a page filled with 100'eds of patches, and rather clueless where to begin :) So.. yeah, unless im taught step-by-step what to do, all i can say is that i appreciate your work :)
C
by Sveinar Søpler on Wednesday October 25th 2017, 13:03
fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend.
fixme:d3d9:D3DPERF_SetOptions (0x1) : stub
fixme:nvapi:unimplemented_stub function 0xbe7692ec is unimplemented!
fixme:msctf:ThreadMgr_ActivateEx Unimplemented flags 0x4
fixme:msctf:ThreadMgrSource_AdviseSink (0xf7cd980) Unhandled Sink: {ea1ea136-19df-11d7-a6d2-00065b84435c}
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x1200e4b8): stub
err:seh:setup_exception stack overflow 1744 bytes in thread 0009 eip 000000007bc60cb4 esp 0000000000160f40 stack 0x160000-0x161000-0x260000
Crashes before login screen (same as it did with last source). Anything else you need from me?
Did a fresh git clone from your source and compiled that.
C
by Dox on Thursday October 26th 2017, 6:35
by Sveinar Søpler on Saturday October 28th 2017, 8:24
Thx for the effort tho. We will possibly all end up at DX11 some point in the not-so-far future anyway i guess, so lets hope some performance will come with the release version of wine :)
C
by Sveinar Søpler on Monday October 30th 2017, 11:17
Yeah, the missing ground textures is damn annoying indeed...
C
by Björn Bidar on Monday October 30th 2017, 11:24
I did MoS 2nd boss on mythic plus 12+ and it was a nightmare when the textures of shit were not visible.
What made things worse is that I was melee.
by Sveinar Søpler on Thursday October 12th 2017, 14:12
System:
Elementary OS based on Ubuntu 14.04
I7 2600K@4.2GHz - 16GB ram - Driver nVidia binary - 387.12
nVidia 970 4GB
IO scheduler - Deadline (For xanmod i used mq-deadline)
Wine settings:
export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SYNC_TO_VBLANK=0
export STAGING_SHARED_MEMORY=1
export STAGING_WRITECOPY=1
export STAGING_RT_PRIORITY_SERVER=90
Registry settings:
HCU/Software/Wine/OpenGL/DisabledExtensions=GL_ARB_vertex_buffer_object2
HCU/Software/Wine/Direct3D/csmt=0x1
HCU/Software/Wine/Direct3D/VideoMemorySize=4096
WoW settings (Config.wtf)
SET worldPreloadNonCritical "0"
SET processAffinityMask "255"
SET gxTextureCacheSize "3072"
I did not disable addons, and ran with whatever i use - Bartender4, ClassTimer, DBM, Mapster, OmniCC, Pawn, ShadowedUnitFrames, Skada, TellMeWhen
Tested with different kernels and different Wine versions. Tests in DX9 was done at graphics level 7 - SSAO disabled (not supported) and Liquid detail=Low. GLSL=Disabled.
I did /timetest 1 from Shackle's Den -> Prepfoot (Listed as test #1), then back from Prepfoot -> Shackle's Den (Listed as test #2)
As last time, i scroll the camera into first person, so not to make the character viewdistance a factor.
2.0-Overwatch - Kernel 4.13.6 (From mainline)
#1
Min: 28.431
Max: 229.695
Avg: 111.071
#2
Min: 23.177
Max: 223.604
Avg: 97.770
--------------------------------------------------------
2.0-Overwatch - Kernel Liquorix-4.12.0-14.2
#1
Min: 28.263
Max: 248.077
Avg: 120.614
#2
Min: 17.596
Max: 235.627
Avg: 105.850
-------------------------------------------------------
2.0-Overwatch - Kernel 4.4.0-97 Release from Ubuntu
#1
Min: 16.980
Max: 242.248
Avg: 107.090
#2
Min: 19.588
Max: 231.498
Avg: 94.149
--------------------------------------------------------
2.0-Overwatch - Kernel 4.13.6-xanmod11
#1
Min: 36.719
Max: 244.810
Avg: 124.226
#2
Min: 26.038
Max: 226.244
Avg: 109.111
--------------------------------------------------------
2.18 - DX9 - Kernel 4.13.6 (Mainline)
#1
Min: 28.875
Max: 140.252
Avg: 75.125
#2
Min: 20.910
Max: 130.955
Avg: 67.726
-------------------------------------------------------
"Winner" - Xanmod.
Then i tested with 2.18-staging branch and DX11 - first one i compiled myself gcc-7.2. DX11 tests were done at graphics level 7 SSAO Enabled, and GLSL=Enabled in wine config.
2.18 - Kernel 4.13.6 Mainline
#1
Min: 10.360
Max: 112.736
Avg: 60.472
#2
Min: 15.651
Max: 107.234
Avg: 54.019
-------------------------------------------------------
2.18 - Kernel 4.13.6-xanmod11
#1
Min: 27.349
Max: 109.729
Avg: 63.763
#2
Min: 24.743
Max: 105.337
Avg: 57.376
------------------------------------------------------
2.18-staging (WineHQ official version) - Kernel 4.13.6-xanmod11
#1
Min: 10.110
Max: 108.053
Avg: 63.271
#2
Min: 19.752
Max: 102.439
Avg: 57.170
------------------------------------------------------
Not that huge a difference between my "self-compiled" version of 2.18-staging and the WineHQ one, but a frame is a frame. "Winner" was the xanmod kernel (both kernels was 4.13.6). Did not bother to test the 4.4 or Liquorix against 2.18-staging tho.
Any comparisons or comments?
C
by Tom B on Tuesday October 17th 2017, 6:01
I'm on Arch and will do a similar self-compile test and possibly a kernel test with xanmod. Out of interest, why did you disable GLSL for DX9 but enable it for DX11?
What did you use to track min/max/average fps in game?
by Sveinar Søpler on Tuesday October 17th 2017, 8:15
When you stand at the flightmaster, just type /timetest 1 , and you "enable" benchmark mode the next time you use a flightmaster. When you land at your destination, the min/max/avg is printed on screen :)
Remember to type /timetest 1 again before next benchmark, as landing auto-disables it.
C
by Steve Ebey on Friday October 6th 2017, 8:47
Wine 2.0.2 OW patch, from Dox, source compiled, same Cflags. FPS in ironforge, 139-155.
Both tests run after clean installs of wine, to ensure no leftover code from one version messing with the other. Both test run using DX9. DX11 on 2.18 staging crashed to desktop, randomly. When I could get in, FPS in iron forge never topped 40. In the DX9 testing useGLSL is set to disabled. When set to enabled, both versions of wine lose around 25% in FPS and the character turning and moving is jumpy.
in summary, 2.0.2 OW Staging, compiled on my hardware, gives the best performance, almost on par with Windows 10, and well enough, that except to check addon updates from curse, I am staying on Linux to play WoW.
by Tom Dewhurst on Saturday October 7th 2017, 23:05
by Dox on Sunday October 8th 2017, 17:55
by Tom Dewhurst on Sunday October 8th 2017, 18:11
by Dox on Monday October 9th 2017, 5:04
Good spot for checking is going Antoran Wastes, just to the left of Hope's Landing teleporter on the map, where there are spiders. Green goo drops from the sky and leaves a pool that gives a debuff of "Corrosive Acid" when you stand in it. With DX11 I can see it, with DX9 I cannot see it, but you can see that you are standing in it because you get the debuff.
by Steve Ebey on Monday October 9th 2017, 12:08
by Sveinar Søpler on Tuesday October 10th 2017, 8:20
If that happens, we are as it stands now up "that creek" when it comes to performance, as DX11 is a rather crappy experience atleast for me.
However, i was away a couple of weeks ago, and decided to install wow on my old 2012 model Macbook air... And i must say that even tho the settings was way lower (3 set as default), and fps around 30-35'ish, the experience was slightly smoother than 60-80 fps and wine. Its kinda sad that Apple did not go for Vulkan, as that would possibly kickstart a transition towards a Vulkan client which we all could really benefit from when it comes to Wine.
I dread the day i "have" to dualboot to windows-oh-my-god-10 :( Maybe ill just quit wow again over doing that... ugh :(
C
by Tom B on Monday October 9th 2017, 10:33
In DX11 at 4k on my Threadripper 1950X and 980Ti I get 40-60fps in even non graphical areas (was questing an alt in outlands and seeing drops down to 35!). Most of my settings are on high except for view distances which are 7. Prior to the patch I was on a slower Xeon X5670 and was getting better FPS. For me DX9 and DX11 give almost identical FPS. Can't imagine a CPU upgrade would cause a drop in FPS.
Has anyone had any luck getting OpenGL to work? My game launches but all the textures and lighting effects are messed up.
by Sveinar Søpler on Tuesday October 10th 2017, 8:11
Even recent upgrade to OpenGL 4.6 for the nVidia driver and Wine 2.18 has shown no change in setting -opengl on the wow client when regards to trashed textures. I do not think they are going to do any work on OpenGL at all, as it was somewhat of a "pet project" for one of their devs that no longer work there, and is not officially supported (and has not been for some time).
C
by tristania0102 on Friday October 6th 2017, 6:34
teste bug in mouse point
sorry my bad english
by tristania0102 on Thursday October 5th 2017, 17:13
need tutorial for install for play on linux
battle net no log...
by Jen on Thursday October 5th 2017, 8:39
by Björn Bidar on Thursday October 5th 2017, 8:40
by Jen on Thursday October 5th 2017, 8:40
by Steve Ebey on Tuesday September 26th 2017, 9:06
by Björn Bidar on Tuesday September 26th 2017, 9:18
As long these arent in mainline wine wow wont work:
github.com/wine-compholio/wine-staging/commit/f1b1baf057bd8bf7f22bfdf3f6d982effaeab42a
github.com/wine-compholio/wine-staging/commit/467fed65016e85920a3a9906c443ef0de364983b
One issue we got is that to many spread false information.
by Jen on Monday October 2nd 2017, 8:49
by Steve Ebey on Tuesday October 3rd 2017, 8:49
by Jen on Wednesday October 4th 2017, 22:48
by Steve Ebey on Wednesday October 4th 2017, 22:52
by Sveinar Søpler on Saturday September 23rd 2017, 10:58
Cant remember it was supposed to be like that tho, but my memory of Panda exp is rather old, so for all i know its supposed to look this weird...
pasteboard.co/GLIwR10.jpg
Bug or oki? :)
S
by Yuki on Saturday September 30th 2017, 9:12
by Dox on Wednesday September 13th 2017, 9:57
Question is now, does it happen in DX9 under Windows aswell? I don't have Windows, so I cannot check it at all.
If it is just for Linux+Wine, it could be a bug on Wine end aswell.
by Björn Bidar on Wednesday September 13th 2017, 10:08
Maybe create a bug.
The OS X client uses another OpenGL backend that is only in this client.
See here:
us.battle.net/forums/en/wow/topic/20418713498#post-9
Originally the OpenGL backend was shared between Windows and Mac. The Mac OGL backend (GLL) was eventually forked during WotLK as it became hard for the mac team not break windows OpenGL and didn't want to maintain the largely unused windows OGL backend. The windows OGL backend remained largely untouched all they way though WoD in an OpenGL 2 state. The mac GLL backend meanwhile saw continuous development and WoD added experimental OpenGL 3.2 (which you had to enable from the console).
For legion, it was decided to drop DirectX shader model 2 support (almost impossible to maintain an extreme legacy path on a modern game). From DX's perspective, this only drops some very very old and long unsupported cards, but both OpenGL backends relied on the shader model 2 style path in the engine (ARB assembly shaders) and had to be updated. For the mac side, the OGL 2.1 path was removed and the 3.2 was enabled for the GLL backend and runs through the shader model 4 style path. Meanwhile, the windows OpenGL backend was completely rewritten, targeting OpenGL 4.2 (though I don't think it uses any major OGL 4.2 features, it's likely close to a OGL 3.3 backend). That being said, the windows OGL backend has had exactly 0 testing from quality assurance since it was rewritten and is very likely to have bugs. It is basically an unmaintained, modern backend.
While we're talking history of backends, I'll throw in metal. Metal was added as an experimental backend (not available to the public) in 6.2. Metal will be the default mac backend in legion for cards able to support it. It currently runs a shader model 4/5 hybrid path with development efforts to get more shader model 5 features working (esp with new features added in 10.12).
However i'm not shure about the metal backend.
by Dox on Wednesday September 13th 2017, 10:23
As for the ground effects missing? For example missing ground effects in ToS: Fel Fire at Gorgoth, no crashing wave at Mistress, weird ground effects at Harjatan, to name a few. There are multiple through the game.
by Sveinar Søpler on Wednesday September 13th 2017, 11:34
S
by Sveinar Søpler on Wednesday September 13th 2017, 13:02
Also, that i havent run WoW in Windows for years now, so i cant really tell how stuff is supposed to be there either :P
S
by Björn Bidar on Wednesday September 13th 2017, 13:15
Also some ground effets look rather limited like this at harjatan:
www.dropbox.com/s/v761x9cnmsv3ky9/WoWScrnShot_090717_220546.jpg?dl=0
by Dox on Wednesday September 13th 2017, 13:55
But I was assured it was going to get fixed. It is already pushed up the the developers.
by Björn Bidar on Wednesday September 13th 2017, 14:10
by Dox on Wednesday September 13th 2017, 14:56
by Dox on Wednesday September 13th 2017, 10:17
eu.battle.net/forums/en/wow/topic/17616812948?page=3#post-58
I figure this is why they are stopping support for XP / Vista, so they can tell people to use DX11.
by Dox on Wednesday September 13th 2017, 12:29
So we wait, again.
by Sveinar Søpler on Wednesday September 13th 2017, 13:04
Lets not hope it turns out to be one of those Blizzard oh' so often used "Soon" terms then :P
S
by Yuki on Saturday September 30th 2017, 9:16
by Dox on Saturday September 30th 2017, 9:39
If you want to help get this fixed, open a thread on forum (US preferably, since that forum actually gets read by the devs.) Ask for: "Fix DX9, and if they are not going to do that, give us the ability to use pre 7.3 graphic with some Environment variable we can set in Config.wtf."
by Björn Bidar on Saturday September 30th 2017, 11:42
the EU forums wont read by someone near that stuff.
If you look at the recent problem with the Shadowcaster Voruun you see how far this gets, eg. in this case:
first both get working as intended and weeks later the US guys get an acknowledgement that there's a bug help and infos about an hotfix.
I'm currently workaround this by locking where the ground efffects are and avoiding them like hell and dont fail mechanics.
At the end of the I only want the that stuff works.
A fixed OGL render would be very cool.
by Dox on Monday September 11th 2017, 6:35
github.com/IngeniousDox/wine-wow-2.0
NOTE: This is the same repo as I linked before. I renamed it and set a different master branch to signal that there is a new build out.
It would be lovely if some people can build and test it, since this is the first time I patched and released a version of Wine. I built it myself with "-march=native -O2", and I went to Ironforge next to a fountain to test water settings. I don't crash there, so I figure it works, but you never know.
Cheers,
Dox
by Sveinar Søpler on Monday September 11th 2017, 8:47
Does it mean it actually updated? Or was it just a change of branch with nothing happening, and i need to do a new clone from the link above?
S
by Dox on Monday September 11th 2017, 10:15
(If you don't want to download again, just fetch the repo changes, and create a new tracking branch for wow-2.0 locally.)
by Sveinar Søpler on Tuesday September 12th 2017, 8:33
There IS however a binary difference between compiling the "old" source and the new one, so i guess it IS updated.
I tried setting water to "Good" (Think thats my recommended), and had a random crash after about an hour or so... (Think it was some memory cant be read or something in wow-64.exe) Cant guarantee it was that, but maybe its not fixed? All other settings that i use is the same tho.
S
by Sveinar Søpler on Wednesday September 13th 2017, 1:18
One thing i noticed yesterday was that WoW now crashes when i exit - atleast after playing a while. Have not had a crash while playing (water on "low").
S
by Sveinar Søpler on Wednesday September 13th 2017, 5:33
"I recommend using the Gallium Nine Version of Wine along with the Gallium Nine Version of Mesa (Nouveau), this makes the Game run a lot faster."
Have you tried using Gallium Nine and Nouveau driver with recent WoW? Is it more stable and/or faster than using 2.0-CSMT patched version?
S
by Dox on Wednesday September 13th 2017, 6:36
Gallium Nine is a perfect option if you have AMD. I would like to hear good stories about Nouveau before I even bother trying it myself with my nvidia card.
by Steve Ebey on Wednesday September 13th 2017, 8:31
env WINEDEBUG=-all STAGING_SHARED_MEMORY=1 STAGING_WRITECOPY=1 STAGING_RT_PRIORITY_SERVER=90 nice -15 wine64 "C:\\Program Files (x86)\\World of Warcraft\\Wow-64.exe" >$/dev/null
word wrapped here, but a single line in the command line box, for the desktop shortcut. The only issue i have, is the window launches minimized and I just alt-tab to it, and it goes full screen. I run Fullscreen at 1680x1050 in game. winetrick settings, glsl disabled, csmt enabled (just in case) render set to opengl. hope this helps you enjoy the game. I do still boot to windows, to update addons, but 90 percent of my game time is in Linux now, with decent fps and all the nice perks linux affords.
by Dox on Wednesday September 13th 2017, 9:32
I'm just going to repeat, the Overwatch branch is the old branch. The WoW-2.0 branch fixes the liquid detail crash.
by Sveinar Søpler on Wednesday September 13th 2017, 11:29
I have GTX970 4GB and a old I7 2600K, 16GB ram, so by no means a "super computer".. Put the slider on 10, but set water to LOW, and viewdistance to 3, makes me have great FPS most of the time.. Dips to 40'ish during raids tho, but not too shabby. That is with the "old" overwatch 2.0 branch from before. The "new" branch gives slightly less fps, and somehow introduces some random stuttering even tho i have 80-100 fps... DX9 and CSMT ofc, and 64 bit wow.
Oh, and i run Elementary 0.3 (Ubuntu 14.04), with kernel 4.12(Xanmod), and nVidia 384.69 proprietary drivers.
The 2.16-staging does work with DX11, but the 2.0 branch does not. Horrible fps tho.. 20-25fps in dala vs. 40-45 with the "old" branch.
I did test with WoW-2.0 branch and liquid to "Good", but had a couple of random crashes. Switched back to the overwatch branch, and "Low", and not had any troubles.
S
by Sveinar Søpler on Thursday September 14th 2017, 3:58
After starting using the overwatch branch and 64-bit client and dx9 with liquid set to "Low", i have not had any crashes, and have decent enough fps to not feel hindered when playing. I have better fps with that than what i had with 2.0-rc6 back in february or so, even after 2.1 release i kept using the 2.0-rc6 as it had the "old" CSMT patches, and a lot better fps.. the overwatch branch seems to have some additional patches, cos i have better fps than i remember having back in february, but then again, it could just be fewer ppl around playing WoW theese days than it was in february :P
I can agree that perceived fps vs. actual fps MAY be just a placebo effect when comparing your wow-2.0 branch vs. the 2.0-overwatch branch, and ofc setting water to "Good" WILL most likely be what tips the fps meter a bit down again (after all, its more effects = more strain). But, as i said before, i have crashed a couple of random times with liquid to "Good" even with this branch. Is it just totally bad luck on my part, and that could just aswell have happened with liquid to Low? I usually play for 2-3 hours when i do a session...
Will be interesting to see if ground effects that i cant really tell if im missing or not (cos i probably never have seen how it is supposed to look) will be fixed in some upcoming minor patch, and if this breaks anything tho :)
And from what was posted earlier here, gallium-nine and nVidia is really not recommended even tho i have a GTX970 and kernel 4.12?
S
by Dox on Thursday September 14th 2017, 4:56
- You can simply test if you crashing has to do with Liquid bug due to OW branch, in a spot I use in IF: Just keep it to low, port to IF, walk out of that room, there is a fountain there. Set it to Fair / Good / Ultra, and crash.
- 2.16 staging doesn't crash since it doesn't have the OW patches, so you won't notice it there. (Unless you used 32 bit, see next point)
- 32 bit you can run out of Memory indeed, you get it faster if you increase view distance. This is I believe about the ~4gb limit max 1 program can use in 32 bit.
- You have a Nvidia like me, even setting Liquid detail from Low to Fair will dip fps, especially in places with liquid details (this includes lava, fel lava, and other things that are called Liquids - so not just water). Good even more. Etc
- If you compiled yourself this time, compared to downloading Wine as a binary before, you will have faster code. Esp if you use "-march=native -02", and use GCC7.1.
- If did some of the tweaks I said, they really help, could have given you more fps compared to when you played before.
About Nouveau: It lacks fancontrol and power management, so you could fry your card, or it will just run at low Mhz. (See, nouveau.freedesktop.org/wiki/FeatureMatrix/)
by Sveinar Søpler on Thursday September 14th 2017, 8:26
2. Have not tested 2.16 and this water thing, but when i started playing with 2.15-staging (couple of weeks back), i had to run 32-bit and did indeed get the "out of memory" error.
3. Se #2
4. Yeah, agree. So may aswell be what is fooling me when i tested... and eventually get a crash 2-3 hours playtime. Have not happened when setting "Low" on liquid tho.
5. Hmm.. i seem to be using gcc 6.3.0 (atleast if i type gcc --version), but i have gcc 7.2.0 installed and is what i had to use to get 4.12 kernel up and running with nVidia binary blob (DKMS auto compile module uses that afaik). Cant say im that familiar with compiling, other than following instructions and howto's, so any way i can check what compiler i have used when compiling the source?
6. Yep, i have added a couple of more tweaks that i did not use back in february - STAGING_SHARED_MEMORY, STAGING_WRITECOPY and STAGING_RT_PRIORITY_SERVER options is new this time around, so that might just aswell be what is contributing to a wee bit more fps than when i used 2.0-rc6 back in february :)
Will wait a bit with Nouveau until i am sure 4.12 kernel fully support clocking and fan control. (I read something on Phoronix in may about 4.12 having clock control tho, so kiiinda thought it was working as intended theese days with 4.12 kernel).
S
by Sveinar Søpler on Thursday September 14th 2017, 8:57
Guess i needed to do some fancy config with update-alternatives on my ubuntu distro to make gcc-7 the default compiler :) Gonna do a recompile from your wow-2.0 branch, and keep liquid on low to see if its possible to get a twitch of a fps more from that :)
S
by Dox on Thursday September 14th 2017, 10:08
by Sveinar Søpler on Thursday September 14th 2017, 10:42
In other words, liquid is not liquid, as it depends on where the liquid is i guess :P
Yeah, confirmed.. 2.0-Overwatch crashed hard at the fountain in IF, but not the wow-2.0 branch :)
Thx!
S
PS. Gonna give it another go at liquid set to "Good" then. Oh, and now with wow-2.0 compiled using gcc-7.2.0 :)
by Dox on Wednesday September 13th 2017, 6:51
overwatch-2.0 branch: Staging 2.0 with all Awesies patches on top (which changes some stuff for DX11 in d3d that breaks liquid detail.)
wow-2.0 branch: Staging 2.0 with only the ntdll patches from Awesie. (which leaves those changes to DX11 out.)
In other words: The FPS should be exactly the same with either, only the difference is that by 1 you are forced to set liquid detail to low. Liquid detail takes a lot from your GPU, so you might notice fps gains from just doing that.
Dox
PS: I haven't crashed at all, so I'm wondering if you are actually building the wow-2.0 branch in the first place. Perhaps start fresh in a new directory, clone fresh, and try again?
by Björn Bidar on Wednesday September 13th 2017, 7:32
by Dox on Wednesday September 13th 2017, 9:34
github.com/IngeniousDox/wine-wow-2.0
It is a different branch, and will fix your crash with liquid settings. (Molten lava is a liquid you know).
by Sveinar Søpler on Wednesday September 13th 2017, 11:36
As i wrote before, i did a new clone from the link you posted :)
S
by Sveinar Søpler on Monday September 18th 2017, 2:39
I know you want to pin the "you are full of B*S" thing on me when i say that i FEEL there is more fps/less stuttering using the "old" source vs. this new patched one. But i still claim it hehe. I have set the liquid detail to "Low" on both, and i have both sourced compiled for use.
1. I have had random crashes and even had a disconnect using wow-2.0 - Could ofc be just random bad luck, but i tend to play 2-4 hours at a time when first playing.
2. wow-2.0 seem to have more stutter/less fps on Argus than the other 2.0-overwatch patch. There should be no reason for that, but still i "feel" it is so. Cant really meassure for sure.
The source tree from the Gamax92 git repo with the 2.0-overwatch patches i cant figure out how to download. When i choose -b overwatch-2.0 when i do a clone, its the same as your wow-2.0. Dunno if it is cos i cant figure out how to use git, or if the patches are just replaced. One thing is that when i compile the source the binaries is the same as wow-2.0, but my 2.0-overwarch binaries are different.
S
by Dox on Monday September 18th 2017, 4:38
Basically Gamax used all of them (clumped in 1 big patch) to create Overwatch-2.0. This contains the code that results in the liquid crash. I was more restricted, and just took the patches that had to do with "ntdll" so we can log in, you can see which by checking out the WoW2.0 branch, since I commited the individual commits. Both me and Gamax applied them on top of Staging 2.0.
Now, there are some commits that change some stuff in d3d9, that I didn't apply, so it could be possible that those have an effect for you. You could try applying them and see if you get more fps. According to the bug report about the liquid details, this is the commit that *probably* causes the crash:
bitbucket.org/awesie/wine-overwatch/commits/c218450374b8fd4926ae0403d7fa56ef79b7ddac
Which in fact is 1 of the last d3d patches in the line. (So you just don't apply that or fix it). There are only 3 more afterwards, don't know if they need the code, or if you can just use them.
Let me know if you get more fps without liquid details crashing. And I'll add them on top of the wow branch.
by Sveinar Søpler on Monday September 18th 2017, 8:39
In other words: Im waaay too much of a noob to get a non-patched staging-2.0, and apply what to me seems like a endless list of patches i really cant figure out is for 2.0 or not..
How many ppl is running the 2.0 branch vs. 2.16 "official" one with wine you think? Would be nice to hear from someone else using this with WoW aswell, just so its not only one sided claims from me :)
S
by Steve Ebey on Monday September 18th 2017, 19:23
by Sveinar Søpler on Tuesday September 19th 2017, 3:21
The day 2.x release has the same DX11 performance as 2.0 has in DX9, id be really happy :) I see there is improvements in the staging sources each release, but i kinda think they will never implement CSMT stuff in that sourcetree ever, so not sure how its gonna turn out.
If i try to start with 2.16-staging, and GLSL disabled, i get a error message about not being able to create 3D something, so i have to have it enabled with 2.16-staging. Disabled in 2.0 gives best performance.
S
by Dox on Tuesday September 19th 2017, 5:18
SET worldPreloadNonCritical "0"
And fiddling with:
SET gxTextureCacheSize
wowwiki.wikia.com/wiki/CVar_gxTextureCacheSize
About GLSL, it used to help a lot to disable it. I always just did, but since I was revisiting stuff anyways....it feels like it isn't needed anymore. NVidia driver has gotten way better at it. See also: www.phoronix.com/scan.php?page=news_item&px=NVIDIA-378.09-Beta-Linux
I plan to do some /timetest 1 tests to confirm. But just haven't gotten around to it. wowwiki.wikia.com/wiki/Taxi_Time_Test
by Sveinar Søpler on Tuesday September 19th 2017, 8:26
This is a issue not exclusively related to wine tho, as the battle.net forums is loaded with ppl setting this due to slow loading times in windows, and it helped a buddy of mine aswell, and he is using Win10.
When it comes to gxTextureCacheSize its a bit more hit & miss. I used to have it at 1024, but set it to 2047 per your previous recommendation. I might try to put it back to 1024 perhaps. Wow does not utilize gfx mem on my card at all enough to my taste... I dont think it will in windows either, and perhaps even less when using dx9. Removing it or setting it to 4096 (what i have physically) does cause slightly worse performance tho. I have never seen wow use more than around 800'ish MB regardless of setting this to 1024 -> 4096
I have done a bit of twiddelig with the viewdistance in the past, and setting it to 10 or near max will lower the fps when i overlook from high (eg. flying high above a populated Dalaran or the likes). Putting it to 3 is just a preferred issue to not have those dips in fps when flying overhead, and kinda dont bother me much tho. But i can do some testing what that taxi_time_test thingy if i manage to reproduce a stable fps in low-pop areas. The reason? Cos having 10 players vs. 400 players "randomly" will also create randomly differences in fps :)
S
by Dox on Tuesday September 19th 2017, 9:46
PS: I did find it very weird that it is just below "2048" and I assume it has something to do with something the index table for the texturescache in WoW, which slows down if you get more then 2GB for GPU Ram while using DX9. Though, this could be just me jumping to a conclusion.
by Sveinar Søpler on Tuesday September 19th 2017, 10:38
Did some benchies tho, and cant conclusively say one thing or another, but anyway. The tests was done by the following setup:
1. Gfx settings set to 7 - liquid detail set to "low"
2. I am running 1080P setup in windowed mode (i run a dualscreen setup in Linux, so need that)
3. Tests were done by scrolling all the way in to "first person view", did not move the mouse or "looked around" while flying
4. Tested by flying from "Hafr Fjall" in Stormheim -> "Meredil" in Suramar. Wrote down the results. Fly the same route back. Added the individual results together and divided by 2 to get a average for min/max/avg.
5. The command is "timetest 1".. it auto-disables when you land.
Results:
1024 gxTextureCache - wow-2.0 branch
min: 18.6
max: 188
avg: 84.4
2047 gxTextureCache - wow-2.0 branch
min: 14.7
max: 183.6
avg: 83.1
"Auto" (deleted the setting from Config.wtf) gxTextureCache - wow-2.0 branch
min: 15.8
max: 193.1
avg: 83.2
---
1024 gxTextureCache - 2.0-overwatch branch
min: 20.2
max: 185.8
avg: 85
2047 gxTextureCache - 2.0-overwatch branch
min: 16.6
max: 186.9
avg: 82.9
"Auto" gxTextureCache - 2.0-overwatch branch
min: 14.9
max: 187.1
avg: 83
Also did a round with GLSL Enabled, and it made for a "choppy" run, although not incredibly low average.. but clearly visible stuttering
1024 gxTextureCache - wow-2.0 branch - GLSL Enabled
min: 19.2
max: 177.5
avg: 84.2
Cant conclude one or the other tbh, and it might be better ways to test it perhaps? To me, id say its a miniscule difference between the wow-2.0 branch and the "old" 2.0-overwatch one (although i must admit i lost the source to it, and cant figure out how to get it back.. cos i compiled with gcc-6.3 and not gcc-7.2.. Dunno if it would make a difference tho, but would be nice to test)
I will keep my gxTextureCache settings to 1024 for the time being, as it seems to me it gave a couple of more fps on my rig. The "Auto" one seemed to be slightly better than 2047, so for all i know, it may default to 1024? Only the blizzard coders know i guess :P I did not test with liquid set to "Good", as it might have crashed the overwatch branch, so for comparison alone, i set it the same :) If you want better water effects, wow-2.0 is the best way to go there, as in a benchmark point of view for fps the results are equal. However, i personally feel it introduces some "microstutters" i dont have with the other source, much in the same way as enabling GLSL introduces a LOT of heavy stutters (for me), without really ruining the benchmark results. My oppinion tho :)
S
by Björn Bidar on Thursday September 7th 2017, 4:35
by Dox on Thursday September 7th 2017, 4:53
Setting Liquid to Low is/was needed due to the OW patches from Awesie, I poked Gamax about the bug. But if WoW users can log in now with vanilla Staging, OW users should be able to do the same. Will check.
by Dox on Thursday September 7th 2017, 11:28
Still not the same FPS as Staging 2.0 with d3d9 though. So ideally, if someone has the time / expertise to patch Staging 2.0 with the Staging 2.16 "Added 64 bit syscall thunks in fake ntdll.dll" patches, that would be the ideal.
by Tigs on Tuesday September 5th 2017, 9:58
Actually switching to 2.15-staging (using this site wiki.winehq.org/Ubuntu) was quite easy but it always caused a memory error.
Surprisingly i could solve that (or at least reduce the appearance of that error to a bearable minimum) by switching winecfg from XP to Windows 7.
I can't say it's working like it did before - framerate sometimes drops very low and the mouse input sometimes acts really strange, but at least it's playable.
Maybe this might help someone.
by spaceman on Tuesday September 5th 2017, 6:46
Thanks.
"Second it's hard to support any wrapper like lutrius if someone gets problems.
It's like playonlinux unsupported here. "
Hmmm...neither my post or the post I replied to referred (other than in passing) to wrapper. My post mentions I used Lutris then ripped everything out and started from scratch (without Lutris).
"The 64bit Client works with direct X 9 render as long liquid details are up to low.
See that submitted bugs for this app before the comments."
Unconfirmed bug...I can certainly test that tonight in my many personal investigations. I barely had time to test and out of the box install of Wine / WoW.
by Dox on Tuesday September 5th 2017, 7:43
On Ubuntu I started with installing Wine Staging so I had a wine version installed. Here are ways you can log in.
1) Used Staging 2.15 - and launch 32 bit with command line option -d3d11. Very low fps, very laggy.
2) I then tried using Staging 2.15 - and launch 32 bit with command line option -d3d9, but I crashed before the game loaded.
3) Used Staging 2.15 with Overwatch Patches. This will allow you start 64 bit with -d3d11, I found it slightly better then 32 bit.
4) Used Staging 2.15 with Overwatch Patches. Again 64bit, this time with -d3d9, you have to set Liquid effects to Low or you crash sometimes. It is again slightly faster the other option.
5) Got Gamax to patch 2.0 with OW patches. See my wall of text below for more details. You run it with -d3d9, and set liquid details to low again. This gives absolutely superior fps.
Dox
NOTE: You can get the Staging 2.0 and/or Staging 2.15 with OW patches multiple ways:
- I compiled them myself from the Gamax repo.
- You can install them with Lutris (I did that aswell, and made an installer available for others).
- Or you can use the the runner from Lutris without installing Lutris itself, but then you have to manage your runners yourself, something Lutris handles for you otherwise.
NOTE 2: I used CSMT + __GL_THREADED_OPTIMIZATIONS + STAGING_SHARED_MEMORY=1 + STAGING_RT_PRIORITY_SERVER=90 + disable GLSL + OpenGL DisabledExtensions "GL_ARB_vertex_buffer_object2".
by Dox on Tuesday September 5th 2017, 8:37
- SET worldPreloadNonCritical "0": Faster loading screens.
- SET gxTextureCacheSize "2047: A setting for d3d9, with 4gb Vid card this seems to work the best. Setting it higher then that makes the game slightly laggier in places like Suramar. You can fiddle with it ingame and then turn camera around to see if it gets smoother, since you have to find a value that works for your Video Card. Use: /console gxTextureCacheSize setting to change it. (More info / Copy of old Blue Post: wowwiki.wikia.com/wiki/CVar_gxTextureCacheSize)
by Dox on Tuesday September 5th 2017, 8:48
by Steve Ebey on Tuesday September 5th 2017, 11:09
by Dox on Tuesday September 5th 2017, 12:07
Anyways, you can read more about it here:
github.com/wine-compholio/wine-staging/wiki/Environment-Variables
Remember that you have to give yourself rights to increase priority, it is all described there. Reason for me to use it is because I have 4 cores. With CSMT + NV Threaded, 3 of those cores are fully used most of the time, the 4th core has sound / chat / wineserver / rest of OS running. By giving the Wineserver realtime prio you can stop some FPS dips when WoW needs something from Wineserver.
by Steve Ebey on Thursday September 7th 2017, 9:32
by Sveinar Søpler on Thursday September 7th 2017, 2:22
Ended up compiling it myself, from the "mirror" link you posted below, as the main link could not be pulled, and the pre-compiled version you posted could not log on (some BLZxxxx error message after trying to log in)
A LOT smoother fps than the release 2.15-staging with d3d9. Back to what i'd say is the 2.0-rc6 i used before i quit last time (7.0-7.1 patch i think). 7.3 broke that branch without the patches, so im very happy someone takes the time to patch the old branch with "working" CSMT :P I have 40'ish fps in a populated Dala, and peaks well past 100'eds in world. I have set water to "low", and viewrange to 3... Shadows to "high", and the rest to max.
Im using POL btw, and popping in the custom wine version is probably just as easy as in Lutris :)
S
by Dox on Thursday September 7th 2017, 4:10
2.0-rc6 and 2.0 should have the same CSMT implementation, it was 2.1 where it was changed.
About FPS, you can really get some more fps if you do the little tweaks. I wrote about most of them above, but I haven't talked about NVidia settings (if you have it): I turn on triple buffer in xorg, and force full composition pipeline to stop tearing. OpenGL triplebuffer works better then adding VSync+Triplebuffer ingame with d3d9.
Dox
PS: I started using Lutris next to PoL when they had the OW runner. Now I have fully switched over to Lutris. Just like every program you have to learn to use it, but once you do you notice how easy it is. I find it easier then PoL atm.
by Sveinar Søpler on Friday September 8th 2017, 1:21
Not that familiar with git really, other than cloning a repo and doing the "git pull" to update any patches... Does your fork keep that 2.0-ow version "up-to-date" if any patches appear?
Another thing i forgot to mention i had to do to get my self-compile working was that i only built the amd64 version, so i had to make a symlink to "wine" from "wine64" in the /bin/ folder of my winebuild result..
Lutris/POL is just a gui to make switching between prefixes and different wine versions easy... AND come with different installer-scripts for predefined games/whatever. Haven't tested Lutris, and i mostly just use Wine to run WoW, so can't really see a reason to make it "even easier" as its dirt-easy as it is :P
To those interested in installing a custom wine in POL, you just put your compiled result (ie. when you compile wine with ./configure prefix=$HOME/your_folder) under $HOME/.PlayOnLinux/wine/linux-amd64/your_folder and when you start POL it shows up automagically as "your_folder" under wine versions. (PS. Look above if you only compile 64-bit version tho..)
S
by Dox on Friday September 8th 2017, 13:25
Unfortunately, since it has all the patches, it also gets the wine3d code changed. That is actually what introduces the crash with higher then low liquid detail. So, what we need now is: Staging 2.0 patched with only the ntdll patches, either the original from Awesie in the overwatch branch. Or the ones now in Staging 2.16.
by Tigs on Monday September 4th 2017, 10:32
fixme:d3d:wined3d_check_device_multisample_type multisample_type 32 not handled yet
and i end up with a transparent screen and the warcraft mouse cursor and nothing else happens.
Is there any solution for this? When i google it i only find people who say "install lutris", which i won't cause i don't trust it.
I'm running wine-2.4 (Staging) on Linux Mint 18.1 which worked superb until Blizzard came up with Patch 7.3.0
If there isn't any fix for now, is there any help in sight?
Thanks for help
by Jon on Monday September 4th 2017, 19:37
by Philipp Ludwig on Tuesday September 5th 2017, 0:24
by Dox on Sunday September 3rd 2017, 18:19
First of all, It has been a while since I looked here, since my setup has been working great for a few years now. I have this for reference:
Intel® Core™ i5-4670K CPU @ 3.40GHz × 4 - OCed @ 4ghz with 16gb RAM
Geforce GTX970 with 4GB with 2560x1440 screen
Ubuntu 16.04 with Gnome-Shell / AwesomeWM
I have been using DX9 with Wine Staging CSMT + __GL_THREADED_OPTIMIZATIONS (Nvidia) for a long time now. This is giving me 60 fps on setting 7, with some dropping below that in raids, but this is normal. I kept using newer versions of Wine Staging till 2.0, and I stuck on that. Why? Because from 2.1 the CSMT was stripped of some performance hacks to make it work with DX11. I figure most people would stay on 2.0 with WoW, but from what I have read while I was looking for solutions for 7.3 drama it seems a lot of people actually went and kept following each new staging build. The difference in FPS is very noticable in DX9, and even more if you compare current DX11+CSMT with 2.0-DX9+CSMT.
Now I'm posting, because through the Linux_Gaming_Group, specifically the Lutris channel, I was already in contact with gamax92. He keeps the Overwatch repo going with the Awesie OW patches. I asked him if it was possible to apply those patches to to 2.0. And he said: Yes! and took the time patch it into Wine Staging 2.0 for me to play around with. Thanks Gamax92/Awesie! Now I'm trying to pass on some love here.
The Github branch in his repo is: github.com/gamax92/wine-overwatch/tree/overwatch-2.0
A clone, with that branch set as master is here: github.com/IngeniousDox/wine-overwatch-2.0
You can compile it yourself if you want, this will give you the most FPS for your buck. I suggest reading up on the Wine Wiki how to build your own. I ended up using "-march=native -O2" as compiler flags, tried -O3 but it felt worse.
If you don't want to build it yourself, which I fully understand, I also got Strider (The creator of Lutris) to run and host the build. I created 2 installer scripts myself, 1 for DX9 with now working again Wine Staging 2.0, and 1 for DX11 that uses Wine Staging 2.15 Overwatch. This way I can easily switch between the two versions, I use the DX9 if I want speed (I'm sure the graphical issues will get resolved, the crashing can be stopped by setting Liquid detail to low). And if I want DX11 I just start the other 1.
You can get Lutris here: lutris.net
You can find the WoW installers here: lutris.net/games/world-of-warcraft/
DISCLAIMER: I'm just a user of Lutris, it isn't my program, but I do play multiple Blizzard games. Having Lutris makes it easier to keep clean wine prefixes for each game. And a good 1 click installer if I want a new prefix to fiddle with is even better. But for those sceptics, that still want to get fps, here goes:
A direct link to the Runner for working WineStaging2.0: lutris.net/files/runners/wine-wow-2.0-x86_64.tar.gz (I'm sure someone else would have commented with this link if I didn't post it)
I hope this post helps some people out there that just want to play World of Warcraft on Linux with good FPS. I know there is some nice CSMT work incoming in staging from glancing over the submitted patches. So at some point I'll switch over. But for now, I'm enjoying my high fps on Wine Staging 2.0, and I hope you will 2.
Cheers,
Dox
PS: There are more tweaks you can do then these basics, but this post has gotten 2 long already. If people are interested I will make a small followup post. Or you can hit me up on Discord "Linux_Gamers_Group".
by Siren Watcher on Sunday September 3rd 2017, 2:30
I also have been getting dropouts in old zones, its fine within new dalaran, argus, etc. But I've had drop outs in one damn dungeon twice in timewalking dungeons, old dalaran and this one same place downstairs in orgrimmar over and over when I fly into the same spot. Again as people have commented, lots of windows users are getting this issue also. I would expect that because its new infrastructure, they might be trialing some things. There has been lots of resets this week so might be implementing some fixes hopefully.
Hoping even more heavily that the next issue of staging has a fix, if the dropouts are caused by the lutris overlay of wine... If this fix is implimented by wine, it would also amazingly solve the overwatch bugs id imagine and make it playable on straight wine staging.
by Jen on Sunday September 3rd 2017, 11:13
by shawn on Saturday September 2nd 2017, 16:53
Wine 2.16. Launcher works, Wow won't start from the launcher. Starting it by runnint Wow-64.exe yields a dialog box saying "Game Initialization Failed!"
Wine 2.15 Yields the same results as above.
overwatch-2.15-x86_64 - Launcher and Wow work and run ok using D3d 11, though performance isn't that great. It's usable in the short term but nothing like running Wow with Wine2.16 last week.
by spaceman on Tuesday September 5th 2017, 5:06
I tried Lutris and tbh I got in a mess with it. I'm pretty good at following instructions but there were too many gaps and assumptions for a new user (I will install a test OS and fiddle). I ripped everything out and started fresh. I installed Wine Staging (I've always used -devel to date, but all guides seems to use -staging so...) 2.16 and Set the Blizzard App Launcher to Windows XP with the 7 dll overrides I've used historically (it would not install/run without them). Now I can launch WoW with the launcher but trying to launch the Wow-64.exe (or Wow.exe) directly still returns "Game Initialization Failed!" (with or without dll overrides, setting Windows version as XP/7/10).
I set 'use 32 bit version of game' in the Blizzard App launcher and the game will launch, it crashes two or three times then I can log in. Performance is 'clippy' but FPS is low average. Playable in low graphical intensity environments. I have to disable hardware mouse and that gives me a visible, if flat, single colour grey, mouse. I can use either DX9 or DX11, DX9 performance is marginally better, I need to set graphic quailty low, 1 really to make the game anything like approaching playable. I ran out of time last night for further test.
Tonight: reinstall antiX, Debian Testing and Ubuntu. Install latest Nvidia drivers, wine-staging 2.0 and 2.16 and -devel 2.0 and 2.16. I also intend a Lutris install so I can juse that until we get changes baked into Wine that address whatever changes Blizzard has made to their game client. I look forward to skipping into WoW direct with the App and experiencing reasonable FPS again soon.
by Björn Bidar on Tuesday September 5th 2017, 5:38
But I think it's easy to oversea something with so much stuff that is posted here.
Second it's hard to support any wrapper like lutrius if someone gets problems.
It's like playonlinux unsupported here.
The 64bit Client works with direct X 9 render as long liquid details are up to low.
See that submitted bugs for this app before the comments.
by spaceman on Tuesday September 5th 2017, 11:55
Well, like I said "I can use either DX9 or DX11, DX9 performance is marginally better, I need to set graphic quality low, 1 really to make the game anything like approaching playable. I ran out of time last night for further test. " Setting graphics low, 1, will put Liquid detail to low. And switching off Options | Game Settings | Launch 32-bit client (instead of 64-bit) returns the same Wine Error as trying to launch the game direct: "Game Initialisation Failed."
"It's a bit annoying that ppl doenst read." I agree -.-
by Atonner on Thursday August 31st 2017, 22:20
Nvidia 970, Proprietary drivers current.
Fedora 25
*add to config.wtf
SET worldPreloadNonCritical "0"
(fixes long load screen wait issues)
* env variables or hide them in a script
export __GL_THREADED_OPTIMIZATIONS=1
export __GL_SYNC_TO_VBLANK=0
winetricks glsl=enabled
winetricks vsm=3
winetricks gsm=3
winetricks videomemorysize=4096
* winecfg
wine-staging 2.15 ->CSMT on, VAAPI on
wine set to windows 10
(if your launcher doesn't display tiled inserts, run it with wine set to XP mode once, all the way to character login screen, then switch back, also -- make *sure* that both mono and gecko install in a new prefix -- I've noted that the automated install in staging often breaks and doesn't complete the registry entries)
wine64 to launch BattleNet launcher or World of Warcraft launcher ( i have all the above wrapped up in a shell script)
game options => -d3d9 and tick the "run 32 bit client"
(currently 0 addons)
12 -> 25 FPs in open areas of New Dalaran, 7->12 FPS in the hearth in foyer in New Dalaran. (but I've only spent about 15 minutes in game - so results may not be accurate yet)
I did NOT find that the overwatch-wine bundle worked - although the launcher worked and behaved as normal (see the XP mode to WIN10 mode bit) all attempts to launch the game ended up stuck in RtplWaitForCriticalSection. I'm suspecting that F25 and the build environment have a minor library difference.
I'm going to bet that whatever DRM Blizzard rolled out is *only* in the 64 bit client, not the 32 bit client.
by Jen on Friday September 1st 2017, 1:33
by Björn Bidar on Friday September 1st 2017, 1:54
by Jen on Friday September 1st 2017, 8:40
by Jen on Friday September 1st 2017, 11:16
by spaceman on Tuesday September 5th 2017, 5:13
Thanks for your help!
by Björn Bidar on Tuesday September 5th 2017, 5:44
(Although I don't think the second one helps).
If you need those you can set them in an shell script where you start wow.
For example I have a script to set the wineprefix for wow, set the first variable and start the game.
It's easier to do this stuff in a script than do it every time you start the game.
I always recommend a separate prefix for each application (although blizzard games for example can be put together in one).
by Roo on Thursday August 31st 2017, 11:53
And, one of those exceptions was d3d11, and when I tried DX11, the game crashed incredibly hard. But I've seen reports of working DX11, how do you do it?
by Simba on Monday September 18th 2017, 21:51
by Steve Ebey on Tuesday September 19th 2017, 9:28
by tagelicht on Wednesday August 30th 2017, 17:19
thanks for your nice instruction and i managed to set it all up & get the game running with it. But once I want to login to my character, the loading screen finishes, and then the game crashes leaving a memory access error message.
Do you have any advice for this? I am using the overwatch-2.15 wine, with no library changes whatsoever.
by Jen on Wednesday August 30th 2017, 17:26
by tagelicht on Wednesday August 30th 2017, 17:32
by Yuki on Wednesday August 30th 2017, 20:56
by Jen on Wednesday August 30th 2017, 21:04
I've found for me it happens at the edge of Stormwind towards Northshire, Northshire, Burning Steppes, and around the Tomb of Sargeras.
Other places reported are Frostwall, Ironforge, and Stormshield. (I was able to verify the Tomb of Sargeras one.)
Is this a WINE or a WoW bug? How do we get it fixed?
by Zander on Thursday August 31st 2017, 22:23
by Siren Watcher on Tuesday August 29th 2017, 19:09
I think there is no need to compile wine-overwatch... I downloaded precompiled binaries from lutris.net/files/runners/wine-overwatch-2.15-x86_64.tar.gz, unpacked them at /opt and using the wine binary from this package, I managed to play the game.
Using Linux Mint 18.2 (Ubuntu 16.04 derived) here.
us.battle.net/forums/en/wow/topic/20758687677?page=2
The Overwatch 2.15 x86_64 can be found from the above link.
by Zander on Wednesday August 30th 2017, 12:08
by Siren Watcher on Tuesday August 29th 2017, 19:00
Also located at: us.battle.net/forums/en/wow/topic/20758687677
Trackers fix also worked for me.
1. Downloaded Lutris lutris.net/downloads/
2. Downloaded battle.net lutris.net/games/battlenet/
3. Downloaded WoW [didn't let it reinstall itself with the 40gb, just on lutrix] lutris.net/games/world-of-warcraft/
4. Redirected Lutris's battle.net to load to my already installed WoW.
5. Then followed Tracker's comment [unpacked it in my download folder and lutris auto-found it in the dropdown menu, though I also downloaded overwatch but didn't let it fully install too].
Loads fine now. Thanks heaps :hugs: forums.
Original posts:
Tacker's Comment:
FYI - If you use Lutris to run WoW, go into Manage Runners, then choose Wine - Manage Versions and select the Overwatch 2.15 x86_64. Once that's downloaded, in the Warcraft icon, right click and configure, go to the wine version section and change it to use the new overwatch one you just downloaded. Came right up after that for me.[/quote]
Isaacnewtoon's follow up Comment:
I use Lutris!
It worked for me! Thank you, thank you thank you!!!
I was getting a bit overwhelmed reading through the proposed solution listed at winehq appdb.winehq.org/objectManager.php?sClass=version&iId=33768 by user chiro, involving github.com/gamax92/wine-overwatch
Side note: Lutris makes gaming on Linux super easy and I highly recommend it![/quote]
by Björn Bidar on Tuesday August 29th 2017, 19:22
Can You point out whats the error and show the patch(es) that it?
by Chiro on Wednesday August 30th 2017, 0:15
Not a proper solution, so they won't become upstreamed.
bugs.winehq.org/show_bug.cgi?id=40479 is likely the error
by Chiro on Tuesday August 29th 2017, 11:48
by Jen on Tuesday August 29th 2017, 12:53
by Jen on Tuesday August 29th 2017, 13:03
Answered my own question, for anyone else looking.
by Pedro Pimenta on Tuesday August 29th 2017, 18:01
by Lianna Burnett on Tuesday August 29th 2017, 10:01
by Chiro on Tuesday August 29th 2017, 10:43
Post logfiles and try gamac version for overwatch.
by Elijah Rum on Sunday August 6th 2017, 4:31
Old library overrides don't seem to work very well, battle.net just shows some random error and dies even before letting me to input email + password.
Though I can see the login window, no login buttons can be seen, error window being popped up every 2 seconds.
I'm using arch with wine-2.14.
Could anybody know the correct way of actions here (i'm the wine newb)? Thanks in advance!
by Björn Bidar on Sunday August 6th 2017, 4:35
by Elijah Rum on Sunday August 6th 2017, 4:56
by Gena on Sunday July 16th 2017, 6:53
by Steve Ebey on Sunday July 16th 2017, 8:12
Steve
by Gena on Sunday July 16th 2017, 8:13
by Steve Ebey on Sunday July 16th 2017, 9:06
by Gena on Monday July 17th 2017, 14:36
# cat /sys/block/sda/queue/scheduler
noop [deadline] cfq bfq
I noticed when I play with DX11 my loading becomes a bit faster.
by Tim Ryan on Monday July 17th 2017, 14:56
SET worldPreloadNonCritical "0"
in Config.wtf. That fixed it for me.
by Gena on Monday July 17th 2017, 16:55
Without this option HDD periodically don't used while loading.
by Steve Ebey on Friday July 14th 2017, 11:42
by Björn Bidar on Friday July 14th 2017, 11:46
I play at 4k and play just fine with staging, csmt and d3dx9
by Steve Ebey on Friday July 14th 2017, 12:09
by godson on Tuesday June 20th 2017, 6:44
The only playable way I have found so far is to revert to 2.10 devel and switch back to DX9 on a lowered graphics setting. I am getting stable FPS but obviously something is wrong with staging and the updated patch.
by Douglas Picolotto on Saturday June 24th 2017, 15:39
by Alberto on Saturday June 24th 2017, 19:03
Because I don't have knowledge to compile wine or similar I need to wait a patch included in one version of wine-staging.
I looked Internet for RPMs for wine-staging 2.8 (and wine-staging-32bit 2.8, of course ) but I have failed (I have openSUSE Leap 42.2).
by HeyCitizen on Saturday June 17th 2017, 19:43
I tried nuking my addons/settings, eventually reinstalling the entire game in a new 64bit prefix. I tried wine-staging and wine-staging-git, also recompiled the git version with 'march=native' as suggested in another thread. At the time, the 7.2.5 PTR still worked fine, so I hoped the 7.2.5 patch would magically resolve the issue, and it did! But alas, since another hotfix was pushed, I am back to square one. PTR still works fine, but live still crashes seconds after login.
I can play for a little while using the 32bit client, but it doesn't give me the same performace and it runs out of memory and crashes which kinda cramps my playstyle.
Any thoughts?
by Paul Crane on Saturday June 17th 2017, 20:52
by Björn Bidar on Sunday June 18th 2017, 0:31
by HeyCitizen on Sunday June 18th 2017, 12:05
by Björn Bidar on Sunday June 18th 2017, 12:11
Generic did the trick for me (my cpu is broadwell ep).
by HeyCitizen on Sunday June 18th 2017, 12:29
kernel 4.11.5-1-ARCH
AMD FX(tm)-6300 (Family 21, Model 2)
CFLAGS="-march=bdver2 -mtune=bdver2 -O2 -pipe -fstack-protector-strong"
or
CFLAGS="-mtune=generic -O2 -pipe -fstack-protector-strong"
yeilds same (freeze) results
by Gibbo on Monday June 19th 2017, 13:57
gcc 7.1.1
kernel 4.11.5-2-ck-piledriver
AMD FX 8320
I have tried compiling 2.9.1 and 2.10.1 with
CFLAGS="-march=bdver2 -O2 -pipe -fstack-protector-strong" as well as native and x86-64 all with the same result
I can get away with running in 32bit but I take a performance hit or at least I assume I do. It could be the newer versions of wine or something else of course as I can't compare 64bit.
by Björn Bidar on Monday June 19th 2017, 14:16
by Björn Bidar on Tuesday June 20th 2017, 3:52
Either some of the patches or plain wine is the issue.
I tried the serveral version from current to (0a16521c7e1490e224bef8104953aebb7e9e7f28) to the tag 2.10.
I've tried a version after 2.9 and the commit that was save of is 25e345194ddf9a518405ce038ea91883417a785e.
You can grab pkgbuild with what I build my pkg if you wish:
github.com/Thaodan/thaopkgs/tree/master/wine-staging-git
Please be so kind and try if gcc 7.1 makes no issues here.
You can also try some commits after the save commits and report to me wich made the issue.
by HeyCitizen on Tuesday June 20th 2017, 10:24
by Björn Bidar on Tuesday June 20th 2017, 19:56
I've disabled it and now the latest version works fine.
That patch is the issue:
github.com/wine-compholio/wine-staging/commit/ee5545a45f164d640c9b1cd6575a5645afaeb4a9
Just grab my latest pkgbuild.
by Xnovadatax on Wednesday June 21st 2017, 3:53
by HeyCitizen on Wednesday June 21st 2017, 7:16
by Xnovadatax on Friday June 23rd 2017, 1:04
But I could not apply it, because I'm new to linux, I had a little difficulty.
Anyway, let's wait for a compilation next to the wine. \O
by Tim Ryan on Wednesday June 21st 2017, 12:46
by Steve Ebey on Tuesday June 27th 2017, 0:01
by Steve Ebey on Monday June 26th 2017, 11:49
by Oliver Walbert on Sunday June 18th 2017, 3:08
by Tim Ryan on Sunday June 18th 2017, 10:51
by Gibbo on Thursday June 29th 2017, 7:30
by Entilzha on Saturday June 17th 2017, 18:24
by HeyCitizen on Saturday June 17th 2017, 19:48
by Jon on Friday June 9th 2017, 23:58
pcm.!default {
type plug
slave.pcm "surround51"
}
That actually worked on speaker-test, but had no effect on the available sound configurations in WoW. I get sound from all 6 speakers, but the World\ of\ Warcraft/Logs/Sound.log file confirms it's still stereo, and not only that, the sample rate is only 44.1 kHz while my soundcard is actually physically 48 kHz. I've tested this up to the latest 2.9 wine-staging, the problem exists in every version. Is this really the best it can do?
####################################
World\ of\ Warcraft/Logs/Sound.log:
####################################
6/9 19:44:36.152 => SI3 Init
6/9 19:44:36.209 => WoW Version 7.2.0 (24015) Apr 27 2017
6/9 19:44:36.259
6/9 19:44:36.309 => User Settings Report:
6/9 19:44:36.359 - ========= PLAYBACK =========
6/9 19:44:36.409 - Enable All Sound [1]
6/9 19:44:36.459 - Enable SFX [1]
6/9 19:44:36.509 --- Enable Emote Sounds [1]
6/9 19:44:36.560 - Enable Music [1]
6/9 19:44:36.610 --- Loop Music [0]
6/9 19:44:36.660 --- Pet Battle Music [1]
6/9 19:44:36.710 - Enable Ambient Sounds [1]
6/9 19:44:36.768 - Enable Dialog [1]
6/9 19:44:36.818 --- Enable Error Speech [1]
6/9 19:44:36.868 - Sound at Character [1]
6/9 19:44:36.918 - Sound in Background [1]
6/9 19:44:36.969 - Enable Reverb [1]
6/9 19:44:37.019 -
6/9 19:44:37.069 - ========== VOLUME ==========
6/9 19:44:37.119 - Master Volume [1.00]
6/9 19:44:37.169 - SFX Volume [1.00]
6/9 19:44:37.219 - Music Volume [1.00]
6/9 19:44:37.269 - Ambience Volume [1.00]
6/9 19:44:37.319 - Dialog Volume [1.00]
6/9 19:44:37.369 -
6/9 19:44:37.419 - =========== MISC ===========
6/9 19:44:37.469 - Sound Channels [32]
6/9 19:44:37.519 - Sound Cache [64MB]
6/9 19:44:37.570 - Mix Mode 2 [0]
6/9 19:44:37.620 - DSP Buffer Size [AUTO]
6/9 19:44:37.670 - Armor Foley SFX (Self) [1]
6/9 19:44:37.728 - Armor Foley SFX (Others) [1]
6/9 19:44:37.778 => End of User Settings Report
6/9 19:44:37.828
6/9 19:44:37.870 - SE3 Init...
6/9 19:44:37.928 - FMOD Memory Init
6/9 19:44:37.970 - FMOD System Create
6/9 19:44:39.238 - Setting Output Type
6/9 19:44:39.820 - 8 Output drivers detected
6/9 19:44:39.914 --- [0] System Default
6/9 19:44:39.964 --- [1] Out: default (Out: default)
6/9 19:44:40.014 --- [2] Out: HDA ATI SB - ALC892 Digital (Out: HDA ATI SB - ALC892 Digital)
6/9 19:44:40.064 --- [3] Out: HDA NVidia - HDMI 2 (Out: HDA NVidia - HDMI 2)
6/9 19:44:40.114 --- [4] Out: HDA NVidia - HDMI 0 (Out: HDA NVidia - HDMI 0)
6/9 19:44:40.164 --- [5] Out: HDA NVidia - HDMI 3 (Out: HDA NVidia - HDMI 3)
6/9 19:44:40.214 --- [6] Out: HDA NVidia - HDMI 1 (Out: HDA NVidia - HDMI 1)
6/9 19:44:40.264 --- [7] Out: HDA ATI SB - ALC892 Analog (Out: HDA ATI SB - ALC892 Analog)
6/9 19:44:40.314 ** Using Driver [0] System Default (Out: default (Out: default))
6/9 19:44:40.366 - DSPBufferSize = AUTO DETECT
6/9 19:44:40.415 - Setting DSP Buffer Size
6/9 19:44:40.465 - Using Control Panel Speaker Mode STEREO
6/9 19:44:40.506 - Setting Software Format (44100, 2, 1).
6/9 19:44:40.556 - Requested 32 channels.
6/9 19:44:40.626 - Initializing Software Channels
6/9 19:44:40.696 - Init FMOD Game System
6/9 19:44:40.757 - Ok
6/9 19:44:40.807 - Setting Rolloff Scale
6/9 19:44:40.857 - Setting Rolloff Callback
6/9 19:44:40.899 - Sound Bus Init
6/9 19:44:40.949 - Init Suppressors
6/9 19:44:41.019 - SE3 Init Success.
6/9 19:44:41.076 - Setting device callback
6/9 19:44:41.125 => SI3 Init Complete.
6/9 19:44:41.184
6/9 21:05:31.280
6/9 21:05:31.360 => Shutting Down SI3
6/9 21:05:31.402 - Shutting Down SE3
6/9 21:05:31.518 - Shutting Down SE3 COMPLETE.
6/9 21:05:31.573 => Shutting Down SI3 COMPLETE.
6/9 21:05:31.618
by Björn Bidar on Sunday June 18th 2017, 12:15
I'm using pa with a 5.1 profile and Wow sets the sound to 5.1.
by Jon on Sunday June 18th 2017, 15:49
Did you copy over your install from Windows, by any chance? I know I'm grasping at straws here, but it's driving me nuts. My install is Linux-only.
by Björn Bidar on Sunday June 18th 2017, 16:08
Maybe there's an issue with alsa and wine.
Check the sound tab of winecfg.
by Jon on Sunday June 18th 2017, 16:16
by Björn Bidar on Sunday June 18th 2017, 16:22
Wow doesn't depend on the actual anyway.
Do you use Pulseaudio?
Than just use pulse.
The asound.conf isn't relevant than.
You need to set the pulse profile to 5.1.
by Jon on Monday June 19th 2017, 2:12
"Just install pulseaudio, I don't know why" isn't an acceptable solution, sorry. If you can figure out what pulseaudio is providing to wine in terms of speaker configuration that can't be set with alsa configuration, that would be very helpful. There has to be a way to simulate it. Pulseaudio does not provide multi-channel support itself, so whatever is going wrong here is metadata-related.
by Björn Bidar on Monday June 19th 2017, 12:01
I have no idea how long you play Wow on wine, I just wanted to help. Dont be rude.
"Just install pulseaudio, I don't know why" isn't an acceptable solution, sorry. If you can figure out what pulseaudio is providing to wine in terms of speaker configuration that can't be set with alsa configuration, that would be very helpful. There has to be a way to simulate it. Pulseaudio does not provide multi-channel support itself, so whatever is going wrong here is metadata-related.
> I sounded like you already use pa for native applications and if this is true the pa profile is relevant and the asound conf is ignored.
by Jon on Monday June 19th 2017, 12:52
Can you please check something for me? This actually would be very helpful. If your setup is as described, I have trouble believing 5.1 sound is actually recognized in-game, even if winecfg's audio tab recognizes it as available. If I'm wrong and it is though, then in the sound options panel in-game there should be some speaker-setup pulldown menu that has a "5.1" option which is selectable. I suspect you actually don't have this option and you're really just getting stereo sound replicated to all speakers, like me. Don't feel bad, it took me a while to notice when this had happened too, and some careful testing to be sure. It's also worth noting here that Starcraft 2 (which I have installed in a separate wineprefix) also suffers from the same issue. The tooltip says that the speaker setup options available came from the Windows Control Panel, which as far as I can tell just stores settings in the registry. Since we don't have this in wine though, either pulseaudio is not working either, or it must be making/faking the necessary audio settings or registry changes automatically somehow. That's my hypothesis at this point, at least. If you could verify this one way or another, it would help a lot.
by David Eriksson on Tuesday June 6th 2017, 13:02
I have a Nvidia 970 card and world of warcraft run pretty good - Had the same performace ( low ) at the priodriver 381:22 . But the sound were much better . I use hdmi .
Amd fx 6100 6 core
16 gb DDR3 1600
Can some try with a amd Card ?
On Windows 10 i can run the game on ultra with no problems .
by David Eriksson on Saturday June 24th 2017, 10:14
by David Eriksson on Friday July 7th 2017, 11:21
With Opensource drivers and enable wine nine support i can play on High setting and tank RAIDS in 40-50 fps . Fu** Nvidia ! Now my Nvidia 970 is on the shelf and im using my cheap Amp rx 560 card .
by Steve Ebey on Saturday May 27th 2017, 0:59
by atmos on Sunday May 28th 2017, 15:26
by Steve Ebey on Sunday May 28th 2017, 21:29
by atmos on Monday May 29th 2017, 21:07
by Steve Ebey on Monday May 29th 2017, 22:14
by Matt on Thursday June 1st 2017, 8:57
M.
by Steve Ebey on Thursday June 1st 2017, 9:20
by HeyCitizen on Saturday June 10th 2017, 9:27
by Steve Ebey on Saturday June 10th 2017, 23:05
by Andrew Schott on Tuesday July 25th 2017, 16:47
Actually, I am on F25 as well and just got it going.
Download the zip and blow it out somewhere.
'sudo dnf install python3-lxml python-qt5'
'sudo pip install bs4'
cd into the lcurse dir and do a ./lcurse
I seen your name around this thread a bit, offhand I forget if you have other issues. Gimme a hollar if you need further aid. Wow64 runs rather well on Fedora and RHEL via the plethora of Wine options out there (Crossover, Lutris, wine, PlayOnLinux).
by Steve Ebey on Thursday July 27th 2017, 16:54
Any suggestions?
by Andrew Schott on Saturday July 29th 2017, 13:14
/home/andrew/Games/wine/battlenet/drive_c/Program Files (x86)/World of Warcraft
Also, I share the same addons dir across my Lutris and Crossover installs, so static links work, as its working perfect for me.
Then goto General pulldown -> Imort Addons and it will scan what you got and match it up best it can. I was using WowMatrix and I had to reinstall a good uarter of my addons. Not hard, but tedius. Afterwards firing up WoW was as if nothing happened (which for me was a good thing).
Let me know if you need me to do a screen capture, I can do that if its that confusing. Took me a few moments to figure it out, but I got it.
by Steve Ebey on Saturday July 29th 2017, 23:33
by Pat on Friday May 26th 2017, 1:15
by Björn Bidar on Friday May 26th 2017, 16:52
by Atonner on Saturday May 6th 2017, 8:13
I've been running WoW in wine for years, and I'm finding that the DX11 works quite well right now.
Oddly I have 2 minor issues on the launcher:
1: when the launcher prompts for login the standard login setup seems to fail, and a secondary login box pops down, presenting a plain white dialog box set for login. This login works, it is just ... less visually appealing shall we say (and somewhat concerning)
2: Once the launcher comes up I'm no longer seeing the "news" block in the centre of the launcher window, what there is are two small grey blocks in the top left of the 'news' block space -- all other features work correctly.
I originally thought this was a gecko issue as the issue described in 1: appears to be a browser session cookie issue (according to the windows side of the userbase) This issue occurs in a clean .wine prefix with gecko 2.47 confirmed to be installed and working.
is anyone else seeing this issue and does anyone have any clues on how to tidy this up?
by Atonner on Wednesday May 10th 2017, 19:01
Your browser's cookies are disabled. Please reenable cookies to continue.
shows on the launcher login window if you look for it - black text on a dark grey background makes it rather hard to see.
Trying to dig up why my gecko 2.47 doesn't seem to like blizzards cookies.
by Korben Carreno on Monday May 15th 2017, 16:31
Change Windows Version to Windows XP
Open Wine configuration (winecfg) and change setting at the bottom
by Peter Anderson on Friday May 26th 2017, 11:12
by Jon on Friday June 9th 2017, 5:18
1) You must have "browser hardware acceleration" enabled, or it will just hang forever trying to load the login buttons.
2) I realize now I had accidentally discovered this fix earlier, while trying to address some other bug, but failed to notice the correlation because something "undid" the fix somehow later. My best guess is it was the last WoW or Battle.net patch that undid it.
by Sveinar Søpler on Saturday November 11th 2017, 7:00
Hasn't really bothered with it, as i just deemed it a bug, but by chance i did a patch set as Windows XP and the "news" portion in the battle.net app worked (save for the warning about XP support ending). Setting it to Windows 7/10 immediately after does not fix this as its back to just two squares in the corner.. all buttons working tho, but the web content not loading.
Anything else i can try? DLL override or something?
As i said, everything else works when it comes to patching/buttons and whatever, but the webcontent is not showing up, so its not a huge problem :)
by Jon on Friday June 9th 2017, 4:39
by Jon on Monday May 22nd 2017, 5:13
by Yuki on Tuesday April 25th 2017, 6:37
by Björn Bidar on Monday May 8th 2017, 2:15
by Yuki on Thursday May 11th 2017, 13:28
Since the performance is worse than with wine-staging 2.0-rc6, I compiled that one manually for playing.
by Björn Bidar on Monday May 15th 2017, 3:32
by Yuki on Monday May 15th 2017, 13:50
by Raymond Child on Thursday April 13th 2017, 0:15
Has anyone had this issue and fixed it? I am using wine 2.4
by Tyler Gale on Sunday April 23rd 2017, 23:43
by Björn Bidar on Saturday April 8th 2017, 18:35
by Yuki on Tuesday April 18th 2017, 5:33
by Michiel on Monday April 3rd 2017, 5:28
Anyone else who encounters this?
The problem seemed (it's hard to determine, because the moments it happens seems quite random) to lessen when I switched back to Wine 2.4 (was on Wine 2.5) and removed the override that would set the application to run win7 mode. (It's now back to win-xp :-o)
There's plenty of memory (16GB) (besides, I've had that error 'using too much memory' while there was still plenty available), the NVidia card is only 20% busy at most, the CPU is not overly busy either.
One thing I have to do yet is run a memory test; could be one of the banks is faulty (?) that would cause these reboots as well... maybe others have similar issues, so was curious.
by Michiel on Tuesday April 4th 2017, 14:29
Have to play DX9 though, DX11 is unplayable slow.
by Pavel R on Friday March 31st 2017, 4:27
If I start game executable, it is unable to connect. I can only start it from launcher.
by Jase Whipp on Monday March 27th 2017, 16:52
by Paul French on Wednesday March 29th 2017, 7:51
by Wobbo on Tuesday April 25th 2017, 16:26
by Wobbo on Tuesday April 25th 2017, 16:44
by Jase Whipp on Friday April 28th 2017, 16:19
I've recently switched to Gnome Shell and I no longer have this issue, so I am guessing this is one of those long-standing Unity annoyances.
by Sam Oanea on Friday March 24th 2017, 15:10
Im new with this app and i want to run wow.exe but i can't. The app won't open wow. Can anyone help me with this please?
by Serenity Moral on Saturday March 25th 2017, 4:02
by Dmitry Belyakin on Monday March 20th 2017, 13:53
Just installed Windows to compare performance on my laptop (i7-3537U 2 cores + 2 hyper threading cores + 740M Nvidia) with Wine, and I've got the following results:
1. At first look, performance is the same for Win dx9 and Wine dx9, seems that it is smoother on Win but more stable in FPS with Wine overall (as for me). Dalaran is laggy as hell on both.
2. I tried to enable dx11 on Windows and it works amazingly! No lags in Dalaran, stable FPS. I didn't try raids, but it shoud be ok as well.
The only conclusion is that Legion well optimized for dx11 and poor optimized for dx9, but I'm not 100% sure.
by andzer on Thursday March 2nd 2017, 19:35
Honestly- gentoo/wine-2.0-rc6 is better fps than windows 7 on this box.
Ill be updating the BIOS now. Wish I could just delete this stuff, haarrr.
by andzer on Wednesday March 1st 2017, 22:06
specs:
Gentoo, kernel 4.4, Nvidia 375.39 drivers, i7-2640M CPU @ 2.80GHz, Quadro NVS 4200M, 8GB ram (A Thinkpad Lenovo T520 laptop.)
After varying lengths of time and definitely not always because of heat, framerate drops from 20-30[softcap] (12-20 in HoV raid,) .. to 1-2fps. - With the settings below I was able to see 60 in Dalaran but it wasn't stable and put my cpu at 97 pretty quick.
---Whats puzzling about it is that only a reboot fixes it---. Exiting the game, making sure wine is not in the process list, and starting over does not fix it.
At first I thought it was a heat issue but I have observed quite a few cases since using "cpupower frequency-set -g powersave" that the cpu was running a nice 'cool' 85 (with the nvidia temp at 81) where the same problem is observed.
Anyone experiencing similiar? have any ideas? Need some more information? Is there an IRC channel specifically for WOW on Wine?
by andzer on Wednesday March 1st 2017, 22:40
wine 1.9.2, 2.0, 2.0-rc6 and 2.1,
linux kernels 3.4.14, 4.1.12 and 4.4.48
nvidia drivers 375.26 and 375.39
by Dmitry Belyakin on Thursday March 2nd 2017, 1:59
I have 30fps cap for Legion content and it keeps temperature below the threshold and I'm happy :)
by andzer on Thursday March 2nd 2017, 3:15
my gentoo is way bare bones, no power management configured out-of-box. its all my by hand stuff basically, and its limited with acpi being deprecated in this kernel in favor of p-states, which have only two modes that i cant figure out how to configure beyond hot and cold.
lacking great understanding of it .. im going to boot ubuntu and see if that makes a difference
it just bothers me that it takes a reboot to fix it, (leaving it running at 45 for hours, same low framerate in wow.) plus long compiles like gentoo boxes do (emerge @world --deep, etc.. reach the same temperature threshold without any sputtering,) makes me think memory leak - or misconfigured power management. im going after the - its my kernel/distro angle.
I just want to raid effectively again! ;)
by DrThRaX on Monday February 27th 2017, 8:55
gtx 1060 (6GO)
16 Go
by DrThRaX on Friday February 24th 2017, 20:08
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\wow-64.exe" /v version /t reg_sz /d win7 /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\wow-64.exe\Direct3D" /v CSMT /t reg_sz /d enabled /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\wow-64.exe\Direct3D" /v DirectDrawRenderer /t reg_sz /d opengl /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\wow-64.exe\Direct3D" /v Multisampling /t reg_sz /d disabled /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\wow-64.exe\Direct3D" /v StrictDrawOrdering /t reg_sz /d disabled /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\wow-64.exe\Direct3D" /v UseGLSL /t reg_sz /d disabled /f
Stability 150FPS , without 30-12
by DrThRaX on Friday February 24th 2017, 20:09
wine reg add "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion" /v CurrentType /t reg_sz /d "Multiprocessor Free" /f
by Roland on Friday February 24th 2017, 21:20
i3 the 2nd gen ;)
Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz
im try to find a i7 3rd gen for my motherboard ;)
by Dmitry Belyakin on Friday February 24th 2017, 23:02
by DrThRaX on Saturday February 25th 2017, 6:16
wow is work perfectly with D3D9 & gtx 1060
by Dmitry Belyakin on Saturday February 25th 2017, 6:35
by Roland on Sunday February 26th 2017, 14:19
in Raid ~15 ppls - @ boss pull frames drops
by David Eriksson on Saturday May 13th 2017, 11:24
by Roland on Monday February 27th 2017, 0:25
by J.F. on Sunday March 5th 2017, 17:32
6th gen i5
32gb RAM
1060 6GB
by J.F. on Sunday March 5th 2017, 18:35
by Steve Ebey on Friday March 31st 2017, 17:07
by David Eriksson on Saturday May 13th 2017, 11:17
by Roland on Friday February 24th 2017, 6:57
Raids dropbs below 10...
i would love 30 :D
My system is i3 - 16 GB Ram - nvidia 1060 3gb
by Dmitry Belyakin on Friday February 24th 2017, 10:58
WINEDEBUG=-all __GL_THREADED_OPTIMIZATIONS=1 wine64 Wow-64.exe
This is my WTF/Config.wtf: pastebin.com/VKuE0Srt
Please pay attention that some things like locale, realmname etc may not be applicable for you (I use russian locale). Just carefully merge your settings with my if you want. I use low settings with middle textures.
And SET maxFPS "31" - fps was capped with 31, put 60 here. Picture smoother with 60 fps anyway.
wine should be wine-staging version 2.0-rc6. It performs much better then wine-staging 2.1 and 2.2. Run winecfg utility, select Staging tab, check "Enable CSMT".
Good luck!
by Drew on Thursday February 23rd 2017, 21:20
by Drew on Thursday February 23rd 2017, 21:19
by Sveinar Søpler on Thursday February 9th 2017, 14:38
However, it seems as DX11 is possible to enable with CSMT now, and thats a step in the right direction! Go devs!! :)
Also looked at the hint that someone felt the performance was a tad better with 2.0-rc6, so since i kinda had to roll back anyway after upgrading to 2.1 today, i gave that a whirl, and from first glance it actually does feel as if 2.0-rc6 has a tad higher perf than the 2.0 release have. Gonna stick with that until next 2.1 release comes along :)
PS. Running 2.0-rc6 i could not get the battle.net client to start, but had to start WoW directly... so i guess if a patch comes along ill have to swap between 2.1 and 2.0-rc6 for now.
by Dmitry Belyakin on Tuesday February 21st 2017, 7:11
by Dmitry Belyakin on Tuesday February 21st 2017, 7:11
by Sveinar Søpler on Saturday February 25th 2017, 6:39
Seems much like 2.1 really. Still huge difference with 2.0-rc6 over 2.1 or 2.2 sadly (appx 40'ish fps with 2.2/2.1, and 65+ with 2.0-rc6 in Dalaran for me).
Havent given the tips above a test yet, so maybe some more fps to be had from that :)
S
by Björn Bidar on Sunday February 5th 2017, 7:23
Dx9 Mode, 64bit client.
Latest wine-staging-git on arch.
by Dmitry Belyakin on Wednesday February 1st 2017, 12:30
Orgrimmar, auction with many people standing, I have 45 fps with wine 2.0, and 60 fps with wine-staging rc6. I don't know the max value for fps since fps is capped for 60, so I belive it even more than 60!
by Dmitry Belyakin on Wednesday February 1st 2017, 14:40
by Roland on Friday February 24th 2017, 6:02
on i3 16GB Ram - Geforce 1060 only get around 25 FPS - and Drops in Raids
by Dmitry Belyakin on Friday February 24th 2017, 6:11
JFYI: I have a huge lags in new Dalaran, and fps in a new content is unstable too (WoD, Legion. With WoD laptop overheats frequently and drops CPU freq, but it is possible to play 50-60 fps if I'm not mistake when CPU is cold enough) , so I capped fps for 30. With the old content I have a decent 60fps
by Roland on Friday February 24th 2017, 6:56
by Jon on Friday January 27th 2017, 21:23
Basically the issue is that (in d3d9 mode, 64-bit WoW client, wine 2.0, using prescribed dll overrides) after changing zones back and forth from raids/dungeons/pvp instances and Dalran (or sometimes just when leaving the class hall) WoW fails to progress past the loading screen. Usually the progress bar freezes part way, like at about 80-90% but not always exactly in the same spot. I still hear audio playing, and the mouse cursor is still present and active, but eventually the harddrive stops running and the zone load never completes. This doesn't happen every time. It seems to mostly only happen after a certain amount of zone changes or elapsed game time. Anyone else seeing this?
by Sveinar Søpler on Friday February 10th 2017, 15:54
us.battle.net/forums/en/wow/topic/20749718759?page=156
Some ppl describe their problems here, so i tried the setting mentioned:
SET worldPreloadNonCritical "0"
in the Config.wtf file.
Made quite a difference for me, but i never really had a huge problem with this, as the game is on my SSD, but my RL friend who has his wow installed on a older spin-disk really noticed the difference.
Worth a try :)
by Jon on Saturday February 11th 2017, 10:43
by diego on Friday January 27th 2017, 4:58
by Elijah Rum on Sunday January 29th 2017, 7:07
by diego on Sunday January 29th 2017, 15:56
gpu: gtx 960
by Pavel R on Thursday January 19th 2017, 13:01
by Real Name Sure on Monday January 30th 2017, 10:14
by Pavel R on Wednesday February 1st 2017, 0:01
I'm not sure if it is worthwhile to run the game with DX11. I don't think it is supported well enough in wine.
by Pavel R on Wednesday January 18th 2017, 12:22
by Jon on Wednesday January 18th 2017, 21:02
by Pavel R on Thursday January 19th 2017, 11:58
by Jon on Sunday January 22nd 2017, 19:25
api-ms-win-crt-math-l1-1-0
api-ms-win-crt-stdio-l1-1-0
msvcp140
ucrtbase
vcruntime140
by Elijah Rum on Wednesday January 11th 2017, 11:31
Gentoo, tried both wine versions: 1.9.23, 2.0-rc2.
Running old client throws some error on login.
by Elijah Rum on Wednesday January 11th 2017, 11:33
Now everything works.
by C.J. on Friday March 10th 2017, 11:22
by Patrick on Saturday January 7th 2017, 6:07
by ergo on Sunday January 8th 2017, 6:05
by Patrick on Monday January 9th 2017, 10:09
My specs if curious:
AMD FX 6300 and a GTX 960
by Patrick on Monday January 9th 2017, 12:07
by BloodyIron on Saturday January 14th 2017, 14:33
Still testing though
CPU: i7-980x
GPU: GTX 960 2GB
Res: 1920x1080
All details set to lowest, except shadow quality high, outline mode good.
Windowed Fullscreen
by Quyxor on Saturday December 31st 2016, 10:42
P.S. Sorry for my English
P.S.S Happy New Year!
P.S.S.S. Help me pls ;(
screen: dropmefiles.com/yNY2h
and glitches like that: www.youtube.com/watch?v=UHOmLNZ2ejY
terminal output:
__GL_THREADED_OPTIMIZATIONS=1 wine PortBattleNET/Program\ Files/World\ of\ Warcraft/Wow-64.exe -opengl
fixme:ver:GetCurrentPackageId (0x45e550 (nil)): stub
fixme:mpr:WNetGetUniversalNameW (L"Z:\\home\\quyxor\\PortBattleNET\\Program Files\\World of Warcraft\\data\\data", 0x00000001, 0x22c7b0, 0x22c770): stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:win:EnumDisplayDevicesW ((null),0,0x22efc0,0x00000000), stub!
fixme:dxgi:DXGID3D10CreateDevice Ignoring flags 0x1.
fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
fixme:dxgi:dxgi_device_init Ignoring adapter type.
fixme:d3d11:device_parent_create_swapchain_texture device_parent 0x8bed950, container_parent 0x8befb10, wined3d_desc 0x22ecb0, wined3d_texture 0x8bf3cf0 partial stub!
fixme:d3d11:device_parent_create_swapchain_texture Implement DXGIwined3d usage conversion.
fixme:win:EnumDisplayDevicesW ((null),0,0x22e840,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22e660,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22eca0,0x00000000), stub!
fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type.
fixme:win:EnumDisplayDevicesW ((null),0,0x22eab0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22e8d0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22eb20,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22e940,0x00000000), stub!
fixme:msctf:ThreadMgr_ActivateEx Unimplemented flags 0x4
fixme:msctf:ThreadMgrSource_AdviseSink (0x846fd40) Unhandled Sink: {ea1ea136-19df-11d7-a6d2-00065b84435c}
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x117ce4c8): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x22db00,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22d920,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22dae0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22d900,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22dae0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x22d900,0x00000000), stub!
fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
fixme:wbemprox:client_security_SetBlanket 0x7e1977e0, 0x134b00, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7e1977e0
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
fixme:wbemprox:client_security_SetBlanket 0x7df017e0, 0x14e8d0, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7df017e0
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:ver:GetCurrentPackageId (0x5c0e9d8 (nil)): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x33f3b4,0x00000000), stub!
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f7c8
fixme:win:EnumDisplayDevicesW ((null),0,0x33ef34,0x00000000), stub!
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f348
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
fixme:wbemprox:client_security_SetBlanket 0x7e05c7e0, 0x134b00, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7e05c7e0
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
fixme:wbemprox:client_security_SetBlanket 0x7defd7e0, 0x14e8d0, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7defd7e0
fixme:wbemprox:enum_class_object_Next timeout not supported
fixme:ver:GetCurrentPackageId (0x5c0e9d8 (nil)): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x33f3b4,0x00000000), stub!
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f7c8
fixme:secur32:schannel_get_mac_algid unknown algorithm 200
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x34f1a8
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x34f1a8
fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
by Patrick Dillon on Wednesday January 4th 2017, 22:18
Running Linux Mint 18.1 Serena with nvidia driver 367.57.
imgur.com/a/RtHi8
imgur.com/a/JVH6F
Frame rate hovers around 60-90 on the 7 preset, but the flashing on certain effects and textures not loading isn't great.
by Mike on Friday January 6th 2017, 7:33
by Björn Bidar on Friday January 6th 2017, 7:36
by Mike on Friday January 6th 2017, 7:52
by Björn Bidar on Friday January 6th 2017, 8:01
with or without csmt?
got an NVIDIA card and __GL_THREADED_OPTIMIZATION=1 ?
by Mike on Friday January 6th 2017, 8:10
by Björn Bidar on Friday January 6th 2017, 8:20
I you open winecfg and look for staging you'll see if csmt is enabled.
by Action Jackson on Wednesday December 28th 2016, 22:15
Now, I would like to play again on Linux.
At the moment, I am having pretty massive tearing in the open world, and the environment is -- well, a lot of the time it looks like I'm in the Emerald Nightmare with Xavius =)
I have older hardware, maybe 4-5 years old. But, it plays fine in Windows, so I won't list the spec right now. I know it's definitely not new hardware like I see other's here using.
Using OpenGL, so far. I updated to wine 2.0-rc3, still same issues.
Where would I start to resolve this issue?? Most of the posts seem to suggest they just installed the game, and it mostly worked.
Is there somewhere where I can alter a configuration file or something to get a playable situation.
Thanks.
by hirschhornsalz on Thursday December 29th 2016, 2:43
OpenGL is unusable at the moment, the main problem is that the Windows-OpenGL renderer is buggy and this could only be resolved by Blizzard. So you are required to stick with D3D9, which is far slower than in Windows.
For me it is not working, as a Raid Lead 20-30 fps with medium settings in the raid just don't cut it, I need 60 fps, and preferrably constantly. I have quite powerful hardware, so this isn't a problem in Windows, but it is in Linux. Back in Pandaria I could even record Videos while raiding without much fps drop, alas, those days are gone.
But OTOH I see people submitting test results where they got 6 (six) fps and rate it as "Platinum". In such extreme cases I do adjust the rating, but if someone says "outdoor 30 fps" and "gold rating", who am I to judge the validity of his test results.
by Action Jackson on Thursday December 29th 2016, 20:18
Switching to directx 9, the games seems to be better. I haven't determined how playable it is yet, since have only done basic stuff. But, seems ok for 3v3 skirmishes =)
by ergo on Wednesday December 28th 2016, 9:24
Above all... test FPS in ZONES from Legion or WoD expansions. Just because you get 90+ FPS in stormwind and nearby zones doesn't mean the game deserves Gold/Platinum rating especially when Legion zones bring down FPS to single digits.
Playing the game with the graphics preset set to 1 shoudn't be rated as gold too. Let me quote you the Bronze rating definition: Bronze
"APPLICATION WORKS, BUT IT HAS SOME ISSUES, even for normal use; a game may not redraw properly or display fonts in wrong colours, BE MUCH SLOWER THAN IT SHOULD ETC".
That's what we all face right now in WoW: much slower than it should.
by diego on Wednesday December 28th 2016, 19:43
by John Lang on Friday December 23rd 2016, 1:24
Has this happened to anyone else? Or know what is wrong, and how to fix it :D
by Ryan Davis on Friday December 23rd 2016, 20:57
by Ryan Davis on Friday December 23rd 2016, 21:07
Debug output shows:
fixme:secur32:schannel_get_mac_algid unknown algorithm 200
which may or may not be related.
by Björn Bidar on Saturday December 24th 2016, 6:00
Do use the launcher?
by Ryan Davis on Saturday December 24th 2016, 18:32
by Ryan Davis on Monday December 26th 2016, 1:42
I'm currently seeking older packages to downgrade to and retest. I'll fill you in when I have news.
by Ryan Davis on Monday December 26th 2016, 2:09
Works perfectly (the binaries are in /opt/wine-devel/bin.)
The regression seems to be in 2.0 rc1, and I'll file a bug in the morning.
I found the files in /var/cache/apt/archives and I can put them up for folks who need to download them.
Good luck and happy hunting.
by Ryan Davis on Monday December 26th 2016, 3:36
by Ryan Davis on Thursday January 19th 2017, 18:55
by David McInnis on Thursday December 22nd 2016, 0:44
On Arch Linux I installed extra/libtxc_dxtn, and multilib/lib32-libtxc_dxtn. It seemed to help a lot.
-Dave
by Alberto on Saturday December 24th 2016, 6:03
Thanks, David
by Lewis Anderson on Sunday December 18th 2016, 6:53
by Anthony Hughes on Friday December 16th 2016, 12:29
Here is a video of the issue:
youtu.be/w2gXXS87WQc
Has anyone else encountered this? If so, any advice on workarounds? Is this a bug I should file somewhere?
Thanks in advance.
by Elijah Rum on Saturday December 17th 2016, 18:37
It's a library for some texture compressing format, probably used by Blizzard.
by Anthony Hughes on Sunday December 18th 2016, 13:20
by Lewis Anderson on Friday December 9th 2016, 1:12
by HeyCitizen on Monday January 2nd 2017, 7:44
Alternatively, you can try not logging into the game world. The intro screen doesn't have many game objects or other players to load into your memory so ram usage should stay low as long as you don't log into your character. You might also want to avoid starting the game (or your computer) altogether. if your ultimate goal is to have your ram be as unused as possible.
If however, you were to make more ram available to WoW (by installing more ram and/or by closing other programs that use up memory) your character will be more likely to move around in populated cities without freezing up the game. This is ideal for people like me whose goal is to play the game smoothly.
by Lewis Anderson on Tuesday January 3rd 2017, 21:38
by Mr Bultitude on Sunday December 4th 2016, 6:15
by Chris Rankin on Tuesday December 20th 2016, 9:04
by Bousty on Thursday February 2nd 2017, 19:41
Work perfectly with wayland.
by lumirax on Saturday November 19th 2016, 11:56
I have installed Battle.net with wine 1.9.22, and I've got 2 problems :
1st, when I start Battle.net, I had problem solve by "dbghelp" set to disable to launch application. But when it start I can't connect with my account cause button don't appear, there's Battle.net's logo just turn and turn and never disappear to let me connect. If you've any idea ? I don't have anymore !
2nd, not a very big problem, but there's a graphic problem it's like there is a mirror on the application , if someone have problem like this and if you have solutions.
Thanks for help !
by Cory on Monday November 21st 2016, 18:36
That'll solve problem #1.
I'm not sure how to solve the mirror on the application.
Maybe check the Battle.net App page:
appdb.winehq.org/objectManager.php?sClass=application&iId=15365
Maybe start with a fresh WINEPREFIX? See if it disappears?
I had that same problem a long time ago, maybe it'll be fixed after it (the Battle.net App) updates.
*fingers crossed*
by lumirax on Saturday November 26th 2016, 9:42
That's work now with ttf-mscorefonts-installer ! :)
And this other problem fixed by updates
by kaimon on Monday December 5th 2016, 12:37
by kaimon on Monday December 5th 2016, 12:58
fixme's vary depending on overrides, among others regarding vcruntime, wbemprox, winhttp, heap, win, mmdevapi, nls, iphlpapi, winsocks, ntdll, dxgi, d3d11. Some vanish with various overrides but several people say overrides should not be necessary any more?
Errors:
err:ole:CoInitializeEx Attempt to change threading model of this apartment from apartment threaded to multi-threaded
err:ole:CoGetClassObject class {77f10cf0-3db5-4966-b520-b7c54fd35ed6} not registered
err:ole:CoGetClassObject no class object {77f10cf0-3db5-4966-b520-b7c54fd35ed6} could be created for context 0x1
Most of the times BN just ends up unresponsive in the system tray, sometimes it starts and spins endlessly without letting me enter anything (not even change the hardware accelaration). This is really annoying because I have to update via Win7 which I wanted to ditch. Game still runs, slow but without principal problems.
by kaimon on Monday December 5th 2016, 17:00
~/PlayOnLinux's virtual drives/WoW/drive_c/users/.../Local Settings/Application Data/Blizzard Entertainment/
~/PlayOnLinux's virtual drives/WoW/drive_c/users/.../Local Settings/Application Data/Battle.net/
~/PlayOnLinux's virtual drives/WoW/drive_c/users/Public/Application Data/Blizzard Entertainment.alt/
~/PlayOnLinux's virtual drives/WoW/drive_c/users/Public/Application Data/Battle.net/
Now Battle.net starts, updates and hangs with BLZBNTBTS00000025: Battle.net requires the Windows Secondary Logon service to be enabled. Changed system to Win7 or Vista, BN hangs again in the system tray. Changed back to WinXP, deleted the dirs again and after some unsuccessful trys the app starts, I can enter my password, and I now get BLZBNTBGS80000011 Login problem.
This is driving me nuts.
by Máté Vágó on Sunday November 6th 2016, 14:49
by Máté Vágó on Sunday November 6th 2016, 14:50
by Björn Bidar on Sunday November 6th 2016, 15:58
which browser hardware accerlation where?
by Máté Vágó on Sunday November 6th 2016, 20:23
1. set up a 32bit wine environment. (WINEARCH=win32 WINEPREFIX=~/wine_wow winecfg)
2. select win7 apply.
3. WINEARCH=win32 WINEPREFIX=~/wine_wow winetricks
4. select default wineprefix.
5. install fonts.
6. select corefonts and press ok.
7. wait 'till finish
8. WINEARCH=win32 WINEPREFIX=~/wine_wow WowInstaller.exe (that one you can get with starter editon from battle.net)
9. wait until the exe set up battle.net, and at the login screen select the gear at the top-right corner.
10. I dont really remember maybe the last option on the list.
11. disable hardware browser thing.
12. log in
13. press install wow
14. wait a bit
15. play
by Elijah Rum on Thursday November 3rd 2016, 15:14
by Elijah Rum on Thursday November 3rd 2016, 15:15
by Elijah Rum on Tuesday November 1st 2016, 3:28
64-bit version freezes almost immediately, somtimes during load.
32-bit feels okay until there's another player within the range of my vision. their textures don't seem to load, they look black and fps drops to ~10.
by Elijah Rum on Tuesday November 1st 2016, 3:28
by Elijah Rum on Tuesday November 1st 2016, 14:37
by Björn Bidar on Tuesday November 1st 2016, 14:43
by Elijah Rum on Wednesday November 2nd 2016, 5:07
Today in the morning freezes returned, but I had to go to work, so will probably try again in the evening, will run repair once again.
by Elijah Rum on Wednesday November 2nd 2016, 14:06
freezes are back, yay..
by Elijah Rum on Thursday November 3rd 2016, 7:03
Open battlenet launcher, update wow.
Then click on settings dropdown in battlenet and click 'scan and repair'.
After process's done, close the launcher and run the game without it.
Managed to play several hours without freezes yesterday, again, this way.
by Björn Bidar on Thursday November 3rd 2016, 12:10
by ergo on Thursday November 3rd 2016, 14:14
by Björn Bidar on Friday November 4th 2016, 16:25
by Elijah Rum on Sunday November 6th 2016, 14:15
All in all runs well, untill suddenly freezes.
Sometimes right after start, very rarely after 2-3 hours.
Would be really happy to find out it's fixable.
by Elijah Rum on Wednesday November 9th 2016, 4:18
by Björn Bidar on Wednesday November 9th 2016, 6:11
by Elijah Rum on Wednesday November 9th 2016, 6:45
Wine is staging with csmt enabled.
by Cory on Monday November 21st 2016, 18:47
I have an Intel HD4000 (intel i3 1.9GHz CPU), and I get about 25 FPS on average, with Wine 1.9.10
I remember reading that CSMT only helps people with AMD/nVidia cards. I know it didn't help enabling it when I tried using CSMT/staging on WildStar.
But hey. if it works. Don't touch anything! lol
by Dif on Thursday November 17th 2016, 13:05
Did you downloaded and compiled it manually or through a Layman repo?
I ask because the main Portage repo is still at 1.9.20 (and I updated it less than 6 hours ago).
Thanks in advance.
by Elijah Rum on Friday November 18th 2016, 4:55
You can use 'hossie' overlay from layman, or just copy the ebuild with new version in it's name run 'ebuild digest' and then emerge.
by Björn Bidar on Friday November 18th 2016, 19:33
I'm now at 1.9.23 and still get a freeze.
by Dif on Thursday December 1st 2016, 12:33
As for Björn, even in my case it still freeze even with 1.9.23. :(
by Björn Bidar on Monday October 31st 2016, 6:34
I played a few days without any issues but today the occured again.
Has anyone an idea what causes the issue or how to fix it?
by Jon on Friday October 28th 2016, 2:29
by Jon on Friday October 28th 2016, 2:30
by Ricky Johansson on Friday October 28th 2016, 3:30
SET gxTextureCacheSize "1024"
by Jon on Friday October 28th 2016, 4:10
by ergo on Friday October 28th 2016, 11:41
by mal karis on Thursday October 27th 2016, 21:24
by mal karis on Thursday October 27th 2016, 22:16
Still not sure what was broken.
by ergo on Sunday October 23rd 2016, 12:53
On the other hand the problem doesn't exist with an opengl renderer but with opengl there is a lot of flickering.
by Geoffrey on Wednesday October 12th 2016, 17:40
[Software\\Wine\\DllOverrides] 1476309412
#time=1d224d38a80a65a
"*api-ms-win-crt-conio-l1-1-0"="native,builtin"
"*api-ms-win-crt-runtime-l1-1-0"="native,builtin"
"*api-ms-win-crt-stdio-l1-1-0"="native,builtin"
"*d3dcompiler"="native"
"*d3dx11_43"="native"
"*d3dx9_43"="native"
"*winhttp"="native,builtin"
"*wininet"="native,builtin"
"api-ms-win-core-errorhandling-l1-1-0"="native,builtin"
"api-ms-win-core-interlocked-l1-1-0"="native,builtin"
"api-ms-win-core-libraryloader-l1-1-0"="native,builtin"
"api-ms-win-core-localization-l1-2-0"="native,builtin"
"api-ms-win-core-localization-l1-2-1"="native,builtin"
"api-ms-win-core-namedpipe-l1-1-0"="native,builtin"
"api-ms-win-core-processenvironment-l1-1-0"="native,builtin"
"api-ms-win-core-processthreads-l1-1-0"="native,builtin"
"api-ms-win-core-processthreads-l1-1-1"="native,builtin"
"api-ms-win-core-rtlsupport-l1-1-0"="native,builtin"
"api-ms-win-crt-environment-l1-1-0"="native,builtin"
"api-ms-win-crt-filesystem-l1-1-0"="native,builtin"
"dbghelp"="builtin,native"
"msvcp100"="builtin,native"
"msvcp140"="native,builtin"
"ucrtbase"="native,builtin"
"vcruntime140"="native,builtin"
First time poster, this isn't my first time configuring Wine to run WOW. Those above are all the entries in my "user.reg" file. Hope this helps someone. I'm running wine 1.9.20 with LinuxMint 18 Battle.net version 1.5.08058. It's installing smoothly now without anymore pop-up errors. Hope I was helpful.
by Hid on Monday October 10th 2016, 5:54
I have a 2GB video card so I chose 1024mb, but if that doesn't work for you, try anything between 32 and 2047mb - 2048 or above caused massive lag for me, while 2047 or lower removes camera turning lag, so make sure to keep it below 2048.
by Hid on Monday October 10th 2016, 5:54
by Martin on Sunday October 9th 2016, 3:28
Link: support.microsoft.com/en-us/kb/2999226
by chaslem on Thursday October 6th 2016, 0:25
Console FPS tests report 60FPS.
Here is some info:
OpenGL Renderer - Mesa DRI Intel(R) HD Graphics 520 (Skylake GT2)
Processor - 4x Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz
Graphics - Intel Corp Sky Lake Integrated Graphics (rev 07)
Ubuntu 16.04.1 LTS
wine-1.9.20
Things I've done:
Regedit OpenGL fix
Went to config.wtf and updated SET gxApi "OpenGL" (got this error when trying to open wow: WOW was unable to start up 3D acceleration)
Set graphics control from 2-4 (Same fps and problem regardless)
What do I need to do to solve this FPS issue?
by Mika on Sunday October 9th 2016, 15:15
by Hid on Monday October 10th 2016, 5:52
I have a 2GB video card so I chose 1024mb, but if that doesn't work for you, try anything between 32 and 2047mb - 2048 or above caused massive lag for me, while 2047 or lower removes camera turning lag, so make sure to keep it below 2048.
by Hannes on Tuesday October 11th 2016, 15:56
by Doer on Wednesday October 12th 2016, 8:56
by seba on Wednesday October 12th 2016, 23:22
Set graphics control from 2-4 (Same fps and problem regardless) "
same problem here!
~5 fps en citys
~40 alone
any solution? :(
by pokemon123 on Monday December 5th 2016, 2:33
bc i have the same problem :(
by Bill Mann on Wednesday September 28th 2016, 10:47
by DrThRaX on Friday September 30th 2016, 4:32
Try with vcrun2005 or vcrun2010
by erika jonell on Thursday September 22nd 2016, 8:52
TL;DR: nvidia GTX 1070 appears to not work well at all with latest wine & wow; suspect due to immaturity of drivers and/or wine wrt new card hw.
I'm at my wits end, actually past it (since i wiped and went back to win10 - ew ew ew ew)... however, i figured i would post here with all my attempts and what i did to see if someone could point out an error or possible reason why its not working.
first up initial main assumption of why its not working: flaws in 367 and 370 variant drivers when combined with nvidia GTX 1070 amd wine and wow (unconfirmed, but highly suspected given below).
OK, now on to historics. I -had- a gtx 970 rig until, well, bad things happened and i no longer have it. WoW ran well with it, quite well in-fact. I would typically issue __GL_THREADED_OPTIMIZATIONS=1 and __GL_SYNC_TO_VBLANK=0; vblank proven through glxgears to boost framerate a ton and threaded opts would help with staging's CSMT... together these worked wonderfully with the 970, with minor tweaking, and acceptable settings (nothing max, but nothing min either) i could easily get +50 fps dx9 in Legion's dalaran. this system was an i7 6700, 16gb ram, ssd, w/ said gtx 970.
built new system: wanted to give AMD a go, bought new FX-8370 (8-core), 16gb ram, Mobo: gigabyte GA-970A-UD3P rev2, etc. w/ new 1070. (am aware of the PCIx 2 limit), shouldn't have had the huge impact as WoW + wine wont push it THAT hard) FYI- runs beautifully on windows regardless so obviously not that big of a limitation... full settings doesnt drop below 40fps in high pop areas.
Linux OS System configs i've tried:
Arch Linux & ubuntu 16.04.1 (w/ nvidia-drvier-ppa)[tried as phoronix shown as using it, figured maybe ubuntu had a kernel tweak i didnt know about).
As for Arch:
--Stock kernel & Zen kernel @ 4.7.x - zen adds BFQ, other great tweaks for desktop usage (also used with 970 rig to great effect)
--DE: Mate (latest available) (personal tests show xfce contributing to 3d accel degredation, which was my goto DE, now not anymore).
--drivers: 1st used nvidia-dkms @ 370.x version (needed to run w/ zen kernel) + added in DRM/KMS via kernel options and initramfs tweaks to make blitting the screen faster (again used w/zen in old rig, ran beautifully).
--as for wine: attempted with 1.9.18/19, and staging variants w/CSMT... w/ d3d9 at LOW settings framerate in dalaran was at best 24fps (when I stared at the ground). w/ opengl (when it worked) similar if not lower (i.e., it was worse than running open-source w/ wine-nine patches & appropriate stack). Additionally, __GL_THREADED_OPTIMIZATIONS=1 and __GL_SYNC_TO_VBLANK=0 appeared to have no discernable affect in wine when i confirmed they did have an affect outside of wine. NOTE: not using CMST and seemed to have hardly any impact in performance (maybe a 5-10 fps drop at most).
--drivers pt2: thought maybe nouveau was being loaded somehow, while kernel module is loaded, nvidia, nvidia_drm,etc, etc. were also loaded. Xorg log stated nvidia driver in use, lshw and lspci stated card was using proprietary driver as well... purposefully blacklisted the nouveau driver... still appeared in lscpi kernel modules... but not in the "in use", everything else log wise checked out... still same crappy performance. next figured DKMS maybe wiered something up... regressed back to stock proprietary driver, dropped zen, etc etc. got everything back up, no change... same performance... at this poing was getting vary disparaged, so i figured i would give ubuntu a try since i KNOW the 1070 performed well in phoronix's tests which used Ubuntu with the nvidia latest driver ppa. so thats what i did
As for Ubuntu:
--16.04.01 -
--kernel 4.4.x
--DE: unity (actually shown to be very fast for 3d apparently *shrug*)
--drivers: updated w/ nvidia ppa (tried both 370.x and 367.x), as only way to recognize the 1070... confirmed that nvidia proprietary were recognized through xorg logs, lspci, lshw, etc.
--same setup as far as wine 18/19 w/ and w/o staging CSMT... same performance. literally the same.
at this point i was crushed... everything i tried didnt seem to work, i couldnt get any performance out of this card. Worst point is, I even tried with a borrowed RX 480 for shits and giggles with the open-stack + wine-nane (on arch, i couldnt get ubuntu's 16.04 kernel to recognize and load amdgpu driver for the 480); with the wine-nine stack it got better performance than the proprietary nvidia... never did try the nouveau stack (probably should have)
So... thats my story... and why (at present) i'm running windows... if anyone can offer a reasonable suggestion as to whats wrong, i'm willing to setup dual-boot to verify. Until then, i wait patiently for nvidia 1070 driver/wine progress...
by erika jonell on Friday September 23rd 2016, 10:06
OK, I actually got it working! and performance is better than ever. This is what i did:
Running Arch:
during install, while in archchroot i setup repo-ck to enable linux-ck kernel and utilized the linux-ck-piledriver kernel and associated nvidia-ck-piledriver drivers. Both are at 4.7.4 and 370.x i believe.
did all the normal setup stuff, DE, browser, blah blah blah...
setup used stock 1.9.19-staging. set it to enable CSMT, set it to use pbuffer as apposed to fbo as the offscreen renderer, and disabled strict draw ordering (makes sense since this should be controlled by CSMT).
since i use an nvidia card i launched with the following CLI options __GL_THREADED_OPTIMIZATIONS=1 __GL_SYNC_TO_VBLANK=0. NOTE: while guides out there say that using the English vs American spelling of optimi(z|s)ation works as well... well it doesn't (at least on my system). Use the 'z' spelling or it wont have an effect. You can validate this against glxgears. When the correct spelling is used, you should see the fps actually drop to about half with vblank also enabled, which makes sense as glxgears is single-threaded. When all combined, this boosted my d3d9 & opengl fps to 60+ in most situations. This is at a base setting of 7 in wow and its smooth as buttuh. Opengl perf seemed a little bit better, except for the seisure-inducing flicker glitches everywhere, which makes it a no-go.
I may try a custom compile of wine-staging since i've also updated my makepkg.conf to used march and mtune of bdver2, which should further optimize it for my system. I expect that would eek out some extra performance/efficiencies as well.
by erika jonell on Friday September 23rd 2016, 12:02
ANYWAY, i can run the game at max settings now, with fps around 50-60+ on average.
proof: i.imgur.com/Jlszi82.png
settings: i.imgur.com/TCyqp9G.png
I hope this trouble-log helps folks :)
by Bugs on Tuesday October 4th 2016, 13:01
Do you have any screen tearing when fast moving camera? When I use DX9 tearing is there and with OpenGL isn't. But OpenGL is unusable in Legion due artifacts in lighting. :(
by erika jonell on Tuesday October 4th 2016, 14:07
I use Arcc Linux and am running the linux-ck kernel optimized for AMD piledriver architectures. I am also using the nvidia-ck-piledriver drivers; which are essentially DKMS versions of standard nvidia drivers for that specific kernel (i.e., saves time instead of always re-running DKMS on every driver update)
Anyway, i'm using regular old wine-staging 1.9.19 64-bit (not 32-bit as battle.net doesnt like it anymore)
I've enabled CSMT with winecfg
i've also added the following registry entries:
wine reg add "HKEY_CURRENT_USER\Software\Wine\OpenGL" /v DisabledExtensions /t reg_sz /d GL_ARB_vertex_buffer_object /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\Direct3D" /v DirectDrawRenderer /t reg_sz /d opengl /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\Direct3D" /v Multisampling /t reg_sz /d disabled /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\Direct3D" /v OffscreenRenderingMode /t reg_sz /d fbo /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\Direct3D" /v StrictDrawOrdering /t reg_sz /d disabled /f
I've added/made-sure-are-set the following to the Config.WTF in the WOW directory:
SET gxApi "D3D9"
SET ffxDeath "0"
SET ffxGlow "0"
SET M2UseShaders "0"
and after setting the appropriate wine prefix for where i stored wow i run the following to start the game
WINEDEBUG=-all __GL_THREADED_OPTIMIZATIONS=1 __GL_SYNC_TO_VBLANK=0 wine Wow-64.exe -d3d9 $> /dev/null
that above: disabled all debug messages, any other wine messages that get through are sent to /dev/null (this makes sure the game isnt flooding your console slowing you down); the __GL_THREADED_OPTIMIZATIONS makes the nvidia graphics card attempt to multi-thread any OpenGL calls it gets (since the direct draw renderer is uing opengl and wine converts DirectX 9 to opengl, that will speed things up); the __GL_SYNC_TO_VBLANK=0 disables vertical sync w/ nvidia cards so it can run as fast as it can to draw things, rather than pacing itself to maintain vsync. This is does not produce tearing if you are using a decent compositor like compton, mutter, kwin, or clutter, but also doesnt hurt your fps ;) I run the 64-bit .exe since im using 64 bit wine. and i double-force the d3d9 renderer with -d3d9 out of paranoia ;)
NOTE: i found out even though you can run full settings in stormheim, other areas of the game are not nearly as well optimized, and framerates will drop... i've found setting graphics to 7 keeps things nice and smooth the majority of the time.
by erika jonell on Tuesday October 4th 2016, 14:34
linux-ck comes from here: repo-ck.com/
add it to your pacman.conf and import/sign the appropriate keys to pull from it.
see wiki.archlinux.org/index.php/linux-ck for additional info :)
by Bugs on Wednesday October 5th 2016, 14:56
I did everything you wrote except I am using PlayOnLinux for wine management. With stock kernel 4.7.4-1-ARCH and Intel Core i5 3570K, GTX 770 I am getting almost same FPS (+- 5) as in Windows 10 but with lowered quality graphics. :)
But when I fast move camera or enter new location, tearing and FPS drops are still there. I have OS and game installed at SSD with EXT4 filesystem so I/O shouldn't be problem and OpenGL still don't do it. You have camera movement smooth without FPS drops?
I'll try linux-ck or linux-zen tomorrow and I hope it will be better.
by erika jonell on Wednesday October 5th 2016, 17:33
That all said I personally dont run wow directly in OpenGL as whatever Shader Model my card runs (4.3 or 4.4 i think) is a bit glitchy with Wow's new opengl renderer, so i always run directx 9 (d3d9) renderer, i still also experience that hitch sometimes when im in a crowded or very very graphically busy area, but the appended 2 helps some, in my case :)
zen, and particularly ck make some nice tweaks to both IO and CPU schedulers to make them more desktop usage friendly rather than server/supercomputer friendly ;) So definitely give them a try and see how they work for you :) I've noticed definite improvement in responsiveness, which may help you out :)
by Bugs on Wednesday October 5th 2016, 14:56
I did everything you wrote except I am using PlayOnLinux for wine management. With stock kernel 4.7.4-1-ARCH and Intel Core i5 3570K, GTX 770 I am getting almost same FPS (+- 5) as in Windows 10 but with lowered quality graphics. :)
But when I fast move camera or enter new location, tearing and FPS drops are still there. I have OS and game installed at SSD with EXT4 filesystem so I/O shouldn't be problem and OpenGL still don't do it. You have camera movement smooth without FPS drops?
I'll try linux-ck or linux-zen tomorrow and I hope it will be better.
by Ben on Monday October 24th 2016, 20:10
Wanted to thank you this fixed all my issues with the flickering.
I been able to run between 45-60fps on my system.
AMD 8320 960GTX 8 Gig of ram.
I did not compile wine just downloaded the staging and added the keys to registry and modified the wtf file Voila! no more flickering!
You may want to post this to the wine_gaming sub reditt once in a while you have peple there asking about the same issue.
Los
by Dif on Thursday September 22nd 2016, 5:03
Unfortunately, nothing. I have been playing for a couple of minutes (just moved the mule char from the bank to the AH and did some search) and it freezed. :(
by Dif on Thursday September 22nd 2016, 5:07
Is it possible to delete this?
Sorry about this.
by Björn Bidar on Sunday September 18th 2016, 16:38
I think it has something to do with the freeze as it sometimes occured before the freeze.
I relogin didn't help, a restart of the game engine didn't too ( enter this in chat to restart the game engine /run RestartGx();)
Only a restart of the helps.
See the last two files that were added (last by date):
dl.dropboxusercontent.com/u/172590784/wow/screenshots/index.html
by Björn Bidar on Sunday September 18th 2016, 16:59
Name : wine-staging-git
Version : 1.9.18.r0.g7baaab5-1
Description : A compatibility layer for running Windows programs git + staging patches not yet upstreamed git
Architecture : x86_64
URL : www.winehq.com
Licenses : LGPL2.1
Groups : None
Provides : wine=${pkgver} wine-compholio=${pkgver}
Depends On : lib32-fontconfig lib32-libxcursor lib32-libxrandr lib32-libxdamage lib32-libxi lib32-gettext lib32-glu lib32-libsm lib32-gcc-libs lib32-attr desktop-file-utils
Optional Deps : lib32-giflib [installed]
lib32-libpng [installed]
lib32-libldap [installed]
lib32-gnutls [installed]
lib32-lcms [installed]
lib32-libxml2 [installed]
lib32-mpg123 [installed]
lib32-openal [installed]
lib32-v4l-utils [installed]
lib32-libpulse [installed]
lib32-alsa-plugins [installed]
lib32-alsa-lib [installed]
lib32-libjpeg-turbo [installed]
lib32-libxcomposite [installed]
lib32-ncurses [installed]
lib32-libcl [installed]
oss
cups [installed]
samba [installed]
lib32-libtxc_dxtn [installed]
Required By : usenew-git wine-mono wine_gecko winetricks
Optional For : None
Conflicts With : wine wine-compholio
Replaces : None
Installed Size : 393.15 MiB
Packager : Bj
Build Date : Sat Sep 10 15:31:54 2016
Install Date : Sun Sep 18 03:44:23 2016
Install Reason : Explicitly installed
Install Script : Yes
Validated By : None
It was build by myself, see here for the code to build the pkg:
github.com/Thaodan/thaopkgs/tree/master/wine-staging-git
by Björn Bidar on Wednesday September 14th 2016, 18:12
by Björn Bidar on Saturday September 17th 2016, 12:09
by DarkHunter on Saturday September 17th 2016, 22:17
by Frederic Spycher on Saturday September 17th 2016, 23:47
by DarkHunter on Monday September 19th 2016, 0:42
just try repair on WoW its help me
some files broken after last update
by Dif on Thursday September 22nd 2016, 5:12
I am asking because the day after the freezes started on my PC, I did try to repair the game and it bought me a couple of hours of game play, but then for some reasonthe freezes reappeared.
by DarkHunter on Saturday September 24th 2016, 7:59
mb they have bug and files missing again
but you can see frezees if not have files and have network problem - i tested it with friends
by DrThRaX on Wednesday September 14th 2016, 14:09
wine reg add "HKEY_CURRENT_USER\Software\Wine\DirectSound" /v DefaultSampleRate /t reg_sz /d 44100 /f
Config.wtf (8 Core / 2048 memory gpu)
SET M2UseShaders "0"
SET ffxGlow "0"
SET ffxDeath "0"
SET UseVertexShaders "0"
SET useWeatherShaders "0"
SET ffxSpecial "0"
SET weatherDensity "0"
SET reflectionMode "0"
SET maxFPS "60"
SET ffx "0"
SET maxFPSbk "5"
SET mapShadows "0"
SET timingMethod "1"
SET M2Faster "0"
SET Sound_SoundOutputSystem "1"
SET Sound_SoundBufferSize "150"
SET processAffinityMask "255"
SET gxTextureCacheSize "2048"
by Björn Bidar on Wednesday September 14th 2016, 18:11
by DrThRaX on Wednesday September 14th 2016, 20:00
wowwiki.wikia.com/wiki/CVar_gxTextureCacheSize
SET processAffinityMask "255"
SET gxTextureCacheSize "2048"
by DrThRaX on Wednesday September 14th 2016, 20:04
launch winecfg => staging (tick all the boxes) => OK
eg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\Wow-64.exe" /v version /t reg_sz /d win7 /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\Wow-64.exe\DllOverrides" /v *mscoree /t reg_sz /d native /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\Wow-64.exe\DllOverrides" /v *msvcr80 /t reg_sz /d native,builtin /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\Wow-64.exe\DllOverrides" /v *msvcr90 /t reg_sz /d native,builtin /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\Wow-64.exe\DllOverrides" /v *winhttp /t reg_sz /d native,builtin /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\AppDefaults\Wow-64.exe\DllOverrides" /v msgsm32.acm /t reg_sz /d native /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\DllOverrides" /v *winhttp /t reg_sz /d native,builtin /f
wine reg add "HKEY_CURRENT_USER\Soft