WineHQ

World of Warcraft

World Of Warcraft Legion

Application Details:

Version: 7.1.5
License: Retail
URL: http://www.worldofwarcraft.com
Votes: 228
Rating: Silver
Wine Version: 2.4

Maintainers: About Maintainership

Test Results

Selected Test Results

What works

d3d9, d3d11, running d3d11 now

Dalaran: 18 -30 fps

Questing:  44-60 fps, depending on how many people are around. Quest/flight spots drop mostly to ~30 fps

Raiding: 11-30 fps (20+ People)

PvP:  15 - 30 fps

wine64  with wow-64.exe or running through battle.net app

Ingame Graphics Settings:

Graphics Quality: 6 / Raid/BG Quality: 1
View Distance: 3
Shadow Quality: Low
Sunshafts: Disabled
Lightning Quality: Good


What does not

-

What was not tested

Installation. Took Wow directly from my win7 installation. 

Additional Comments

Intel i7-3770K @ 3.50GHz
Nvidia GeForce GTX 970 
32GB DDR3 (1333Mhz) 
SSD
Kernel 4.9.13-1
Nvidia Driver 375.39-1 set to max. performance with PowerMizer enabled + adapted Clockspeed

winecfg: Default Settings, Win7, CSMT enabled

Have had run the game on d3d9 before 2.3 but d3d11 seems a little bit more stable now.
selected in Test Results table below
DistributionTest dateWine versionInstalls?Runs?RatingSubmitter
CurrentDebian GNU/Linux Unstable "Sid" x86_64Mar 25 20172.4 Yes Yes SilverSerenity Moral 
ShowArch Linux x86_64Mar 17 20172.3 Yes Yes SilverGibbo 
ShowUbuntu 16.10 "Yakkety" amd64 (+ variants like Kubuntu)Mar 14 20172.3 Yes Yes Silvergodson 
ShowDebian GNU/Linux 9.x "Stretch" x86_64Mar 10 20172.2 Yes Yes GoldC.J. 
ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Mar 01 20172.2 Yes Yes PlatinumJacob Cameron 

Known Bugs

Bug # Description Status Resolution Other apps affected
11674 Dual-core unsupported in WoW and SC2 STAGED View
35363 Several ERRs in WoW when outdoors NEW View
35461 Synergy server causes mouseover events to fail in World of Warcraft NEW View
37594 World of Warcraft in-game browser does not work NEW View
37942 World of Warcraft (7.x.x) hangs: 100% CPU usage UNCONFIRMED View
38265 World of Warcraft 64bit client can not open ticket message from of GM UNCONFIRMED View
40868 World of Warcraft ; seh:RtlCaptureStackBackTrace stub STAGED View
41166 World of Warcraft Legion 7.0.3 OpenGL Artifacting UNCONFIRMED View
41167 HLSL shader parsing failed REOPENED View
42017 Silence d3d11_immediate_context_OMSetBlendState spam at console RESOLVED FIXED View
42065 WOW 7.1 spams fixme:d3d_draw:draw_primitive_arrays Start instance (VALUE) not supported. UNCONFIRMED View

Show all bugs

HowTo / Notes

Comments

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

Key delays
by Jase Whipp on Monday March 27th 2017, 16:52
I've looked everywhere I can think of for an answer to this problem. I'm running Ubuntu Unity, whenever I press and hold a key in WoW the character will keep moving after I've released the key. Anyone else have this issue and no how to fix it?
Running wow
by Sam Oanea on Friday March 24th 2017, 15:10
Hi

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?
Wine vs Windows comparison
by Dmitry Belyakin on Monday March 20th 2017, 13:53
Hello guys!
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.
I would delete this whole thread if I could - my issues have zilch to do with wine. ;)
by andzer on Thursday March 2nd 2017, 19:35
To really really confirm .. I ripped a hard-disk out of a windows 7 box and stuck it in my notebook, where I have the exact same issue, reboot required and all.

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.
Having framerate drops that only go away after reboot.
by andzer on Wednesday March 1st 2017, 22:06
This is confounding ;) .. and sucky ..

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?
re
by DrThRaX on Monday February 27th 2017, 8:55
FX-8120 (8 core to 3.4 GHz)
gtx 1060 (6GO)

16 Go
Boost FPS
by DrThRaX on Friday February 24th 2017, 20:08
Replace Wow-64.exe by Wow.exe for wow 32

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 Roland on Friday February 24th 2017, 6:57
sure but i have under 20FPS alltime...
Raids dropbs below 10...
i would love 30 :D

My system is i3 - 16 GB Ram - nvidia 1060 3gb
  • RE: by Dmitry Belyakin on Friday February 24th 2017, 10:58

by Drew on Thursday February 23rd 2017, 21:20
Any suggesstions would be helpful. TIA
Low Fps in mint
by Drew on Thursday February 23rd 2017, 21:19
Radeon R9 270x. 9-20 fps in dalaran and in raid situation with graphics turned all the way down. Ive tried variouss versions of wine
Wine 2.1 performance
by Sveinar Søpler on Thursday February 9th 2017, 14:38
Seems as 2.1 has made quite a decline in performance for WoW. Tested both with and without CSMT, and the perf. difference between them is not as big as 2.0x

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.
Yellow Tint
by Björn Bidar on Sunday February 5th 2017, 7:23
Has anyone the same issue tha the game sometimes gets a yellow tint until game restart?
Dx9 Mode, 64bit client.
Latest wine-staging-git on arch.

by Dmitry Belyakin on Wednesday February 1st 2017, 12:30
I can confirm it: Example:
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!
occasional failure to finish loading when changing zones
by Jon on Friday January 27th 2017, 21:23
I seem to have a relatively new problem lately that seems similar to an old problem which turned out to be a memory leak.

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?
tested d3d11 wine-staging 2.0
by diego on Friday January 27th 2017, 4:58
work, but low fps min 5 max 20.

by Pavel R on Thursday January 19th 2017, 13:01
I found the problem. Wine was unable to load libgnutls. Looks like it was compiled with version of gnutls different from the one installed on my system. Symbolic link to correct library name fixed that.
  • RE: by Real Name Sure on Monday January 30th 2017, 10:14
    • RE: by Pavel R on Wednesday February 1st 2017, 0:01
Disconnected
by Pavel R on Wednesday January 18th 2017, 12:22
I'm running on Fedora 23. When using wine 2.0-rc5 (or any other rc, from playonlinux), I'm getting disconnect error immediately after entering login and password. With 1.9.12 game connects and works great. Any idea what could be the problem?
No update?
by Elijah Rum on Wednesday January 11th 2017, 11:31
Battle.net does not update WoW to 7.1.5. Does it for you, guys? Any solutions?
Gentoo, tried both wine versions: 1.9.23, 2.0-rc2.

Running old client throws some error on login.
To anyone having fps issues.
by Patrick on Saturday January 7th 2017, 6:07
Try the latest wine staging version 2.0-rc3. It gave me a giant fps boost, now the game is actually playable again! :)
Graphics artifacts
by Quyxor on Saturday December 31st 2016, 10:42
Hi everybody. I am a beginner user Ubuntu 16.04 LTS (64). I installed Wine (version 2.0-rc2). My graphics card - geforce gtx 770 / driver 375.26 (tried other versions). When you start WoW from -opengl team FPS in the game is high (an average of 60+) but there are horrific artifacts. And a bunch of console falls fixme. Can anyone encountered this problem and can help me fixed a it.

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
Want to use Linux again, but need Warcraft =)
by Action Jackson on Wednesday December 28th 2016, 22:15
I was able to play great before Legion, but had to switch back to windows.

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.
To All reviewers/testers
by ergo on Wednesday December 28th 2016, 9:24
Make sure to include in testing results your native resolution, used renderer (opengl/d3d9/d3d11).

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.
Cannot Log in
by John Lang on Friday December 23rd 2016, 1:24
I have noticed in the past 2-3 days that i cannot log into wow, it seems to hang on "logging into game server" and then i get the message BLZ51903006. I use Linux Mint, and tried upgrading to new version (18.1) and still not working. The most weird part is that is for the 2 days before this happened, i would get the errors, but only in the late morning, and afternoon. Early morning and nights, the game would log me in, and work fine.

Has this happened to anyone else? Or know what is wrong, and how to fix it :D
libtxc_dxtn helps on Arch
by David McInnis on Thursday December 22nd 2016, 0:44
Hi,

On Arch Linux I installed extra/libtxc_dxtn, and multilib/lib32-libtxc_dxtn. It seemed to help a lot.


-Dave
cant get 32bit work in arch linux
by Lewis Anderson on Sunday December 18th 2016, 6:53
32 bit just disconnects and wont log in any one know how to fix it?
Intermittent flicker and lag in Fedora 25
by Anthony Hughes on Friday December 16th 2016, 12:29
Hi, I'm using Fedora 25 64-bit with Gnome 3.22 with an AMD HD 6870 GPU on the open source drivers. Legion works fine for the most part but in certain areas of the game I get this weird crosshatched flickering pattern. When it occurs the frame rate plummets to single digits. I've tried multiple graphics settings in the game and tried switching between wine and crossover - the problem occurs in both. I've tried switching between Wayland and Xorg - the problem occurs in both. I've tried switching between Gnome, KDE, and XFCE - the problem occurs in all three. The problem does not occur however under Ubuntu 16.04 or OpenSuse 42.2. I suspect this might have to do with the newer Mesa version that ships in Fedora 25 but that's just speculation.

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.
ram scaling to high
by Lewis Anderson on Friday December 9th 2016, 1:12
In wow I use arch wine staging 1.9.23.2 my ram just slowly goes from 2.1gb to 3.something after 30 mins and ive seen go as high as 5 gbs ram after a couple hours. anyway to stop this that anyone knows?
Wow on Wine on Fedora 25 Gnome (Wayland)
by Mr Bultitude on Sunday December 4th 2016, 6:15
I ran into an issue when I installed Wow on Wine (1.9.22) on Fedora 25 Gnome. When I ran wow and was in game, using the mouse to try to move my character caused the camera to spin (somewhat crazily) and go to top/bottom view. In all menu screens and in battle.net the mouse worked fine. I knew Fedora 25 Gnome defaulted to wayland, so I went to the login/password screen option and selected "Gnome on xorg". Doing this allowed the game/camera to work just fine.
Unable to connect
by lumirax on Saturday November 19th 2016, 11:56
Hi everyone,

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 !
win7
by Máté Vágó on Sunday November 6th 2016, 14:49
Its worked for me with only installing corefonts and set win version to win7.
  • RE: win7 by Máté Vágó on Sunday November 6th 2016, 14:50
    • RE: win7 by Björn Bidar on Sunday November 6th 2016, 15:58
      • RE: win7 by Máté Vágó on Sunday November 6th 2016, 20:23

by Elijah Rum on Thursday November 3rd 2016, 15:14
i only have intel hd 5500, it'll die then
  • RE: by Elijah Rum on Thursday November 3rd 2016, 15:15
freeze
by Elijah Rum on Tuesday November 1st 2016, 3:28
gentoo, intel hd 5500.
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.
  • RE: freeze by Elijah Rum on Tuesday November 1st 2016, 3:28
    • RE: freeze by Elijah Rum on Tuesday November 1st 2016, 14:37
      • RE: freeze by Björn Bidar on Tuesday November 1st 2016, 14:43
        • RE: freeze by Elijah Rum on Wednesday November 2nd 2016, 5:07
        • RE: freeze by Elijah Rum on Wednesday November 2nd 2016, 14:06
        • RE: freeze by Elijah Rum on Thursday November 3rd 2016, 7:03
          • RE: freeze by Björn Bidar on Thursday November 3rd 2016, 12:10
            • RE: freeze by ergo on Thursday November 3rd 2016, 14:14
              • RE: freeze by Björn Bidar on Friday November 4th 2016, 16:25
        • RE: freeze by Elijah Rum on Sunday November 6th 2016, 14:15
          • RE: freeze by Elijah Rum on Wednesday November 9th 2016, 4:18
            • RE: freeze by Björn Bidar on Wednesday November 9th 2016, 6:11
              • RE: freeze by Elijah Rum on Wednesday November 9th 2016, 6:45
                • RE: freeze by Cory on Monday November 21st 2016, 18:47
            • RE: freeze by Dif on Thursday November 17th 2016, 13:05
              • RE: freeze by Elijah Rum on Friday November 18th 2016, 4:55
                • RE: freeze by Björn Bidar on Friday November 18th 2016, 19:33
                  • RE: freeze by Dif on Thursday December 1st 2016, 12:33
x86_64 freeze
by Björn Bidar on Monday October 31st 2016, 6:34
Has anyone fixed the freeze menbtioned in the comments below?
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?
confirmed
by Jon on Friday October 28th 2016, 2:29
Yes, this seems to have gotten much worse with Legion.
Battle.net broke before patch
by mal karis on Thursday October 27th 2016, 21:24
The patch to battle.net for 7.1 causes it to fail, but doesn't have much in the stdout to say why. Just some HTML about a moved object.
Camera lag
by ergo on Sunday October 23rd 2016, 12:53
Does anyone experience an extreme lag when switching camera on the latest wine staging (csmt) on d3d9? Whenever I change direction my fps drops from 70-80fps to 20-25fps for a 1-2s. It's extremely annoying.

On the other hand the problem doesn't exist with an opengl renderer but with opengl there is a lot of flickering.
Battle.net install
by Geoffrey on Wednesday October 12th 2016, 17:40
Got a new Solid State Drive for my Linux PC. Started a fresh install of everything of course. While adding the .dll libraries using winecfg (error, add library, restart battle.net app, error, repeat) I noticed it was truncating the library names to a specific number of characters. So I did some digging found that it stores the info in .wine/user.reg. I found the area to add the .dll info to. The section I'm refering too looks like this:

[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.
Camera turning lag fix
by Hid on Monday October 10th 2016, 5:54
I had this exact problem (based on your description), what worked for me to completely fix it was to open Config.wtf (in your World of Warcraft/WTF/ folder) and change/add: SET gxTextureCacheSize "1024"

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.
ms conio lib name in the description
by Martin on Sunday October 9th 2016, 3:28
The name of the lib is: api-ms-win-CRT-conio-l1-1-0 and should be updated in the desc.

Link: support.microsoft.com/en-us/kb/2999226
Extreme Lag Issues
by chaslem on Thursday October 6th 2016, 0:25
New to Linux. Went from my setting cap of 60FPS to 20FPS. When I spin or move or do anything there is a lot of lag.

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?
Battlenet Fails
by Bill Mann on Wednesday September 28th 2016, 10:47
Getting the MSVCP140.DLL error with 1.9.19 development on a virgin install of Linux Mint 18 Mate. Had same problem on Linux Mint 17.3 Mate.
Very Poor performance with Nvidia GTX 1070
by erika jonell on Thursday September 22nd 2016, 8:52
WARNING LONG POST

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 Dif on Thursday September 22nd 2016, 5:03
I resumed the attempts under Linux (I have been playing under Windows for the last few days due to the freeze) since I got the wine-1.9.19 update.

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. :(
  • RE: by Dif on Thursday September 22nd 2016, 5:07
Skybox corrupted/wrong
by Björn Bidar on Sunday September 18th 2016, 16:38
Has anyone the same issue?
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
64bit client new update
by Björn Bidar on Wednesday September 14th 2016, 18:12
Has anyone tried to client since the new update? I run it currently and it works without issues.
Optimisation fps
by DrThRaX on Wednesday September 14th 2016, 14:09
For maximum fps:

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"
Only Graphical Settings
by Jackson on Sunday September 11th 2016, 15:57
Disclaimer: I'm new to Wine, so this could well be a misconfiguration.

Running Battle.net and WoW works fine, but if I take graphics over the "3" setting in WoW systems preferences, I lose most textures. Am I missing a driver or something?

wine: 1.9.18
distro: Ubuntu 16.04.1
Nvidia driver: 364.19
WoW: 7.0.3
Frequent hangs
by Dif on Saturday September 10th 2016, 7:20
Hi all,
since yesterday (09/09/2016) morning (EU CET) the game keeps hanging up. Everything in-game freezes up (I can't move and so everything else, the in-game menu isn't accessible, etc.), but the task manager doesn't report the WoW process as zombie.

It happens no matters what I do, from combat with mobs to standing still. Sometime it happens after minutes after login and sometime after the first movement after login.

I tried to run it from a terminal and the output is the following: pastebin.com/J5pa1eTS

I have been playing for almost a month without issues (therefore I assume it is not something weird in the engine included in the 7.0.3 patch) and I got the last Wine update few days ago (but I played for several hours since I got it up to the night of the 8th, so I assume it isn't a regression of Wine).

My system is composed by:
WoW 7.0.3.22566
Wine 1.9.18 (Staging)
Kernel 4.4.6-gentoo
Nvidia drivers 361.28
KDE 5.6.5 with Framework 5.23.0

I did a reboot (more the once) in case there was any hanging process that could interfere, but it didn't solve the problem.
patch version 7.0.3.22566 crashes Wow64.exe
by Adrian Demarais on Thursday September 1st 2016, 22:09
New patch, around 7 Mb, downloaded today, Sept 1.
Battle.net runs as always, but the game client Wow-64.exe
now crashes without ever bringing up a window.
No glaring "this is the culprit" errors when launching by command line, but there is a new "fixme".
The pop-up crash box:
-------------------------------------------
|ERROR #132 (0x8510084) Fatal exception!
|Program: C:\Program Files...Wow-64.exe
|ProcessID: 41
|Exception: 0xC000001D
|(ILLEGAL_INSTRUCTION) at 00007fad22c865fe
-------------------------------------------
Output from command line launch.
The "fixme:ntdll" lines are new from this game patch.

fixme:ver:GetCurrentPackageId (0x56e540 (nil)): stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:mpr:WNetGetUniversalNameW (L"C:\\Program Files (x86)\\World of Warcraft\\data\\data", 0x00000001, 0x22c7e0, 0x22c7a0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x22a8e0,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x22a8e0,0x00000000), stub!
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: cannot open shared object file: No such file or directory
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f1c8
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f1c8
fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3

--------------------------------------------------------------------
World of Warcraft version 7.0.3.22566
wine-1.9.17
running as Windows 7; running as Windows 8 or 10 made no difference

Adding overrides for ntdsapi (native, builtin)and ntprint (native, builtin) made no difference
Override for msvcp140 (native, builtin) was still required from previous breakage.

Battle.net still runs without crashing.
Getting Error code: BLZBNTAGT00000846
by Julia HB on Saturday August 27th 2016, 12:43
I was playing WoW just fine last Thursday (8/25/16), and then on Friday afternoon, I launched battle.net and got an "Update" box instead of the "Play" box on the WoW launch screen of battle.net. So I clicked "Update". It thought about it for a moment then popped up a dialogue box that said: "We tried to make a file writable but failed. Please log in as an administrator and try again." It gives an "OK" box to check, and then below that: "More help: BLZBNTAGT00000846" When you click on that, it takes you to:

us.battle.net/support/en/article/BLZBNTAGT00000846?utm_medium=internal&utm_source=app-other

What I need to know is has anyone else gotten this error, and if so, what file is the game complaining about... and how to get a workaround for it. Thanks!
Keyboard input lag
by Joe on Friday August 26th 2016, 18:27
Hi all

I just recently did a fresh-install of 64bit Ubuntu 16.04 after being on 14.04 for a number of years. Since the update I'm having a problem in WoW where my keyboard input is lagging by a few seconds.

Additionally sometimes my key presses also stick (holding W for a bit keeps me running but then after letting go of W I keep running for a few seconds).

There doesn't seem to be anyway to cancel the action until the game just decides to accept new input, which is often very sporadically (sometimes no problems for several minutes, other times this happens continually).

My mouse on the other hand is working flawlessly and responds without issue.

I had this and a few more issues using the standard release of wine. I'm currently using wine-staging which has fixed my FPS problems but the keyboard input is still an issue.

Has anyone experienced this problem lately? I've seen a few threads where people had a similar problem either back in Cataclysm or in a much older version of Ubuntu (~9.0). Unfortunately none of those fixes have helped me out much.

Thanks!

by Ikuria on Tuesday August 23rd 2016, 6:04
be happy, my opengl just opens up a black screen (sound and game workes well because i know where the buttons are)
Battlenet Launcher dont Start
by Lucy on Friday August 19th 2016, 1:58
hey,

i have an error:

Unhandled exception: unimplemented function msvcp140.dll._Mtx_init_in_situ called in 32-bit code (0x7b43c7cc).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:7b43c7cc ESP:0033fc94 EBP:0033fd18 EFLAGS:00200212( - -- I -A- - )
EAX:7b4291a9 EBX:00000004 ECX:0033fcc0 EDX:0033fd38
ESI:7e541ea0 EDI:00111580
Stack dump:
0x0033fc94: 00000010 0033fce8 7bc51440 0093bcba
0x0033fca4: 04165d60 00000000 80000100 00000001
0x0033fcb4: 00000000 7b43c7cc 00000002 7e541ea0
0x0033fcc4: 7e54816a 04160014 92b31800 04165d60
0x0033fcd4: 3f015a8a 0033fd00 7e48d000 04161970
0x0033fce4: 04164260 0033fd18 7e408bc0 0033fd20
000c: sel=0067 base=00000000 limit=00000000 32-bit r-x
Backtrace:
=>0 0x7b43c7cc in kernel32 (+0x1c7cc) (0x0033fd18)
1 0x7e541b17 in msvcp140 (+0x61b16) (0x0033fd4c)
2 0x7e4e6335 in msvcp140 (+0x6334) (0x0033fd8c)
3 0x0091aa62 in battle.net (+0x51aa61) (0x0033fd8c)
4 0x00919688 in battle.net (+0x519687) (0x0033fdcc)
5 0x0041e2d1 in battle.net (+0x1e2d0) (0x0033fe08)
6 0x00912806 in battle.net (+0x512805) (0x0033fe50)
7 0x7b4602dc call_process_entry+0xb() in kernel32 (0x0033fe68)
8 0x7b4612da ExitProcess+0xff9() in kernel32 (0x0033fe98)
9 0x7bc8109c call_thread_func_wrapper+0xb() in ntdll (0x0033feb8)
10 0x7bc8406f call_thread_func+0xce() in ntdll (0x0033ffa8)
11 0x7bc8107a RtlRaiseException+0x21() in ntdll (0x0033ffc8)
12 0x7bc53617 call_dll_entry_point+0x3d6() in ntdll (0x0033ffe8)
13 0xf7583dad wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000)
14 0xf7583f10 wine_switch_to_stack+0x1f() in libwine.so.1 (0xffad1fd8)
15 0x7bc594d1 LdrInitializeThunk+0x220() in ntdll (0xffad2018)
16 0x7b4674a0 __wine_kernel_init+0xa5f() in kernel32 (0xffad3188)
17 0x7bc5a3b3 __wine_process_init+0x152() in ntdll (0xffad31f8)
18 0xf7581fe7 wine_init+0x2c6() in libwine.so.1 (0xffad3258)
19 0x7c000a82 main+0x81() in (0xffad36a8)
20 0xf73bd196 __libc_start_main+0xf5() in libc.so.6 (0x00000000)
0x7b43c7cc: addl $12,%esp
Modules:
Module Address Debug info Name (184 modules)
PE 350000- 3e1000 Deferred qt5multimedia
PE 400000- f5d000 Export battle.net
PE 1070000- 152d000 Deferred qt5gui
PE 1530000- 17be000 Deferred qt5quick
PE 17c0000- 17f6000 Deferred qt5winextras
PE 1800000- 1cf9000 Deferred vivoxsdk
PE 1d00000- 1d4c000 Deferred ortp
PE 1d50000- 4158000 Deferred libcef
PE 10000000-10015000 Deferred vcruntime140
PE 61000000-61029000 Deferred qt5xml
PE 64000000-640b8000 Deferred qt5network
PE 65000000-6545a000 Deferred qt5widgets
PE 66000000-6628c000 Deferred qt5qml
PE 67000000-67485000 Deferred qt5core
ELF 7a800000-7a936000 Deferred opengl32
\-PE 7a820000-7a936000 \ opengl32
ELF 7b400000-7b7e2000 Dwarf kernel32
\-PE 7b420000-7b7e2000 \ kernel32
ELF 7bc00000-7bcf6000 Dwarf ntdll
\-PE 7bc10000-7bcf6000 \ ntdll
ELF 7c000000-7c004000 Dwarf
ELF 7c81a000-7c8a4000 Deferred libgmp.so.10
ELF 7c8a4000-7c8da000 Deferred libhogweed.so.4
ELF 7c8da000-7c918000 Deferred libnettle.so.6
ELF 7c918000-7c92d000 Deferred libtasn1.so.6
ELF 7c92d000-7c961000 Deferred libidn.so.11
ELF 7c961000-7c9c3000 Deferred libp11-kit.so.0
ELF 7c9c3000-7cb21000 Deferred libgnutls.so.30
ELF 7cb6a000-7cb71000 Deferred libxfixes.so.3
ELF 7cb71000-7cb7c000 Deferred libxcursor.so.1
ELF 7cb7c000-7cb8f000 Deferred libxi.so.6
ELF 7cb8f000-7cb9c000 Deferred libxrandr.so.2
ELF 7cb9c000-7cba8000 Deferred libxrender.so.1
ELF 7cba8000-7cbd3000 Deferred libxcb.so.1
ELF 7cbd3000-7cd22000 Deferred libx11.so.6
ELF 7cd22000-7cd37000 Deferred libxext.so.6
ELF 7cd40000-7cd49000 Deferred libffi.so.6
ELF 7cd49000-7cd80000 Deferred uxtheme
\-PE 7cd50000-7cd80000 \ uxtheme
ELF 7cd80000-7ce10000 Deferred winex11
\-PE 7cd90000-7ce10000 \ winex11
ELF 7ce10000-7ce24000 Deferred api-ms-win-core-fibers-l1-1-1
Unable to update in Battle.net
by John Lopez on Sunday August 14th 2016, 22:24
Hello,

I just recently reinstalled Linux, running the newest release of Ubuntu, also the newest version of wine, and after installing Battle.net successfully my WoW always says "Update". Upon clicking it gives me the error "We tried to make a file writable but failed. Please login as administrator and try again." I was under the impression that Wine was always run as admin so I'm not sure what the issue is here - and I would welcome any suggestions. I am fairly new to Linux and am still learning the in's and out's.

Thanks,

John
Battlenet keeps crashing
by Wontez on Tuesday August 9th 2016, 17:39
I keep getting this error after updating to Wine-1.9.16

Unhandled exception: unimplemented function msvcp140.dll._Mtx_init_in_situ called in 32-bit code (0x7b43bfac).
Register dump:
Freezes
by Alexander on Monday August 8th 2016, 9:53
Sometimes game freezes for 10-15 seconds. It's very rarely and i can't understand what cause this behavior. Is anyone has the same thing? WoW x64, wine 1.9.16, Nvidia proprietary driver.
  • RE: Freezes by hirschhornsalz on Tuesday August 9th 2016, 3:39
    • RE: Freezes by DKay on Thursday September 1st 2016, 19:09

by Insilico on Saturday August 6th 2016, 21:22
I am running battle.net and WoW on the new 1.9.16 with no issues to speak of aside from the battle.net client displaying with a fully black screen. If you also have this issue, change your OS to Windows Vista under winecfg. This fixed the issue for me.

Aside from this minor issue, WoW is running with FPS comparable to wine-staging 1.9.15 with CSMT enabled, which is a huge improvement over the FPS issues I encountered with 1.9.15 stable.
Battle.net.exe crash
by Tim Ryan on Friday August 5th 2016, 21:36
For everyone on here having problems with battle.net, simple go to the battle.net page here on AppDB and follow the guide. It works. I tried the things on this page and was still getting a crash, but after following that guide I'm up and running.
battle.net helper.exe crash
by pascal on Friday August 5th 2016, 11:04
hi all im on linux mint 18 and wine 1.9.15 i cant lauch battle.net.exe without crash of helper.exe help me pls


Unhandled exception: page fault on read access to 0x0000049c in 32-bit code (0x10b489bb).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:10b489bb ESP:0033d2c0 EBP:0033d2c8 EFLAGS:00210246( R- -- I Z- -P- )
EAX:00000000 EBX:37266650 ECX:55028f70 EDX:556fc0a0
ESI:0033d364 EDI:373189d8
Stack dump:
0x0033d2c0: 5a22c000 0033d364 0033d2f4 10b48fc8
0x0033d2d0: 0033d364 5a22c000 37266650 55006d8c
0x0033d2e0: 00000001 372f6778 00000001 00000001
0x0033d2f0: 00000000 0033d51c 10ab113c 0033d364
0x0033d300: 5a22c000 37266650 5a22c000 00000000
0x0033d310: 00000001 372f6778 00000001 00000001
Backtrace:
=>0 0x10b489bb in libcef (+0xb489bb) (0x0033d2c8)
1 0x10b48fc8 in libcef (+0xb48fc7) (0x0033d2f4)
2 0x10ab113c in libcef (+0xab113b) (0x0033d51c)
3 0x10ab577c in libcef (+0xab577b) (0x0033d568)
4 0x10b555a5 in libcef (+0xb555a4) (0x0033d670)
5 0x10b55ca2 in libcef (+0xb55ca1) (0x0033d794)
6 0x10aecb9e in libcef (+0xaecb9d) (0x0033e1b8)
7 0x10aec945 in libcef (+0xaec944) (0x0033e330)
8 0x10aec59d in libcef (+0xaec59c) (0x0033e3c0)
9 0x10adcbfe in libcef (+0xadcbfd) (0x0033e454)
10 0x10adc045 in libcef (+0xadc044) (0x0033e478)
11 0x10acc1b0 in libcef (+0xacc1af) (0x0033e490)
12 0x10adc3d9 in libcef (+0xadc3d8) (0x0033e4e4)
13 0x10adc90b in libcef (+0xadc90a) (0x0033e518)
14 0x10adcc0e in libcef (+0xadcc0d) (0x0033e5ac)
15 0x10adc045 in libcef (+0xadc044) (0x0033e5d0)
16 0x10acc1b0 in libcef (+0xacc1af) (0x0033e5e8)
17 0x10adc3d9 in libcef (+0xadc3d8) (0x0033e63c)
18 0x10adc90b in libcef (+0xadc90a) (0x0033e670)
19 0x10adcc0e in libcef (+0xadcc0d) (0x0033e704)
20 0x10adc045 in libcef (+0xadc044) (0x0033e728)
21 0x10acc1b0 in libcef (+0xacc1af) (0x0033e740)
22 0x10adc3d9 in libcef (+0xadc3d8) (0x0033e794)
23 0x10adc90b in libcef (+0xadc90a) (0x0033e7c8)
24 0x10adcc0e in libcef (+0xadcc0d) (0x0033e85c)
25 0x10adc045 in libcef (+0xadc044) (0x0033e880)
26 0x10acc1b0 in libcef (+0xacc1af) (0x0033e898)
27 0x10adc3d9 in libcef (+0xadc3d8) (0x0033e8ec)
28 0x10adc90b in libcef (+0xadc90a) (0x0033e920)
29 0x10adcc0e in libcef (+0xadcc0d) (0x0033e9b4)
30 0x10adc045 in libcef (+0xadc044) (0x0033e9d8)
31 0x10acc1b0 in libcef (+0xacc1af) (0x0033e9f0)
32 0x10a93824 in libcef (+0xa93823) (0x0033ea2c)
33 0x108612e6 in libcef (+0x8612e5) (0x0033ea80)
34 0x108605fc in libcef (+0x8605fb) (0x0033eaf8)
35 0x106aafc1 in libcef (+0x6aafc0) (0x0033eb10)
36 0x106ab072 in libcef (+0x6ab071) (0x0033eb24)
37 0x10692340 in libcef (+0x69233f) (0x0033eb3c)
38 0x10c49bf6 in libcef (+0xc49bf5) (0x0033eb48)
39 0x1050e67e in libcef (+0x50e67d) (0x0033eb74)
40 0x103fe969 in libcef (+0x3fe968) (0x0033ebd0)
41 0x103fdfca in libcef (+0x3fdfc9) (0x0033ec00)
42 0x105137e2 in libcef (+0x5137e1) (0x0033ec58)
43 0x10513ba5 in libcef (+0x513ba4) (0x0033ecc0)
44 0x0d80ad56 (0x0033ece0)
45 0x2d27e82a (0x0033ed0c)
46 0x0d80b03b (0x0033ed24)
47 0x0d84ca50 (0x0033ed48)
48 0x2d27de72 (0x0033ed68)
49 0x2d27dbf4 (0x0033ed84)
50 0x2d27d972 (0x0033eda4)
51 0x0d80b03b (0x0033edc0)
52 0x2d27d521 (0x0033edd8)
53 0x0d80b03b (0x0033edf0)
54 0x0d84a7b0 (0x0033ee10)
55 0x0d81a76a (0x0033ee4c)
56 0x1041d8cd in libcef (+0x41d8cc) (0x0033ee90)
57 0x1041cb2c in libcef (+0x41cb2b) (0x0033eec4)
58 0x103d8f74 in libcef (+0x3d8f73) (0x0033ef0c)
59 0x10d99c4c in libcef (+0xd99c4b) (0x0033ef4c)
60 0x10bdb957 in libcef (+0xbdb956) (0x0033efb8)
61 0x10bdb75b in libcef (+0xbdb75a) (0x0033efe4)
62 0x10dbc230 in libcef (+0xdbc22f) (0x0033f014)
63 0x10dbbeb3 in libcef (+0xdbbeb2) (0x0033f07c)
64 0x10dbbdaa in libcef (+0xdbbda9) (0x0033f0a8)
65 0x106c2d70 in libcef (+0x6c2d6f) (0x0033f0e0)
66 0x106c2ec2 in libcef (+0x6c2ec1) (0x0033f110)
67 0x10684631 in libcef (+0x684630) (0x0033f124)
68 0x106e881f in libcef (+0x6e881e) (0x0033f13c)
69 0x106d03a9 in libcef (+0x6d03a8) (0x0033f1bc)
70 0x106cfcab in libcef (+0x6cfcaa) (0x0033f1c4)
71 0x106d01c2 in libcef (+0x6d01c1) (0x0033f1f8)
72 0x10683940 in libcef (+0x68393f) (0x0033f214)
73 0x106a1273 in libcef (+0x6a1272) (0x0033f248)
74 0x108e3a8d in libcef (+0x8e3a8c) (0x0033f26c)
75 0x108e5d6e in libcef (+0x8e5d6d) (0x0033f2c8)
76 0x108e51cc in libcef (+0x8e51cb) (0x0033f348)
77 0x1082c7db in libcef (+0x82c7da) (0x0033f378)
78 0x1082cc78 in libcef (+0x82cc77) (0x0033f384)
79 0x109210dd in libcef (+0x9210dc) (0x0033f39c)
80 0x11464ec3 in libcef (+0x1464ec2) (0x0033f470)
81 0x1145b1e3 in libcef (+0x145b1e2) (0x0033f4dc)
82 0x114582e0 in libcef (+0x14582df) (0x0033f534)
83 0x1145a2cd in libcef (+0x145a2cc) (0x0033f5f0)
84 0x1145a612 in libcef (+0x145a611) (0x0033f61c)
85 0x11437fd8 in libcef (+0x1437fd7) (0x0033f6a8)
86 0x10ed6cee in libcef (+0xed6ced) (0x0033f700)
87 0x1142cea6 in libcef (+0x142cea5) (0x0033f710)
88 0x1014d141 in libcef (+0x14d140) (0x0033f7b8)
89 0x10124df8 in libcef (+0x124df7) (0x0033f8a8)
90 0x10124606 in libcef (+0x124605) (0x0033f940)
91 0x1014ea97 in libcef (+0x14ea96) (0x0033f964)
92 0x10124bb0 in libcef (+0x124baf) (0x0033f994)
93 0x10124b66 in libcef (+0x124b65) (0x0033f9b8)
94 0x11c40ebc in libcef (+0x1c40ebb) (0x0033fc30)
95 0x114e4bee in libcef (+0x14e4bed) (0x0033fc50)
96 0x114e4aa6 in libcef (+0x14e4aa5) (0x0033fcb0)
97 0x114e3de3 in libcef (+0x14e3de2) (0x0033fcc0)
98 0x10078eec in libcef (+0x78eeb) (0x0033fd84)
99 0x10046fcd in libcef (+0x46fcc) (0x0033fda8)
100 0x004908e5 in battle.net helper (+0x908e4) (0x0033fdcc)
101 0x00401f98 in battle.net helper (+0x1f97) (0x0033fdf4)
102 0x004a57a9 in battle.net helper (+0xa57a8) (0x0033fe40)
103 0x7b45fbac call_process_entry+0xb() in kernel32 (0x0033fe58)
104 0x7b460bda in kernel32 (+0x50bd9) (0x0033fe88)
105 0x7bc7ff5c call_thread_func_wrapper+0xb() in ntdll (0x0033fea8)
106 0x7bc82f2d call_thread_func+0xfc() in ntdll (0x0033ffa8)
107 0x7bc7ff3a RtlRaiseException+0x21() in ntdll (0x0033ffc8)
108 0x7bc524c7 call_dll_entry_point+0x3d6() in ntdll (0x0033ffe8)
109 0xf757fb7d wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000)
110 0xf757fce0 wine_switch_to_stack+0x1f() in libwine.so.1 (0xffa9b6b8)
111 0x7bc584a9 LdrInitializeThunk+0x228() in ntdll (0xffa9b6f8)
112 0x7b466cfa __wine_kernel_init+0xa69() in kernel32 (0xffa9c868)
113 0x7bc59383 __wine_process_init+0x152() in ntdll (0xffa9c8d8)
114 0xf757dd37 wine_init+0x2c6() in libwine.so.1 (0xffa9c938)
115 0x7c000ac2 main+0x81() in (0xffa9cd88)
116 0xf7395637 __libc_start_main+0xf6() in libc.so.6 (0x00000000)
0x10b489bb: movl 0x49c(%eax),%ecx
Modules:
Module Address Debug info Name (184 modules)
PE 340000- 3ad000 Deferred msvcp140
PE 3b0000- 3c5000 Deferred vcruntime140
PE 3d0000- 3d4000 Deferred api-ms-win-crt-runtime-l1-1-0
PE 3e0000- 3e3000 Deferred api-ms-win-core-string-l1-1-0
PE 3f0000- 3f3000 Deferred api-ms-win-core-timezone-l1-1-0
PE 400000- 573000 Export battle.net helper
PE 580000- 65c000 Deferred ucrtbase
PE 660000- 664000 Deferred api-ms-win-core-file-l1-1-0
PE 670000- 673000 Deferred api-ms-win-core-namedpipe-l1-1-0C:\Program Files (x86)\Battle.net\Battle.net.7730\api-ms-win-core-namedpipe-l1-1-0.dll
PE 680000- 683000 Deferred api-ms-win-core-handle-l1-1-0
PE 690000- 693000 Deferred api-ms-win-core-file-l2-1-0
PE 6a0000- 6a3000 Deferred api-ms-win-core-heap-l1-1-0
PE 6b0000- 6b3000 Deferred api-ms-win-core-synch-l1-1-0
PE 6c0000- 6c3000 Deferred api-ms-win-core-datetime-l1-1-0
PE 6d0000- 6d3000 Deferred api-ms-win-core-localization-l1-C:\Program Files (x86)\Battle.net\Battle.net.7730\api-ms-win-core-localization-l1-2-0.dll
PE 6e0000- 6e3000 Deferred api-ms-win-core-sysinfo-l1-1-0
PE 6f0000- 6f3000 Deferred api-ms-win-core-synch-l1-2-0
PE 700000- 703000 Deferred api-ms-win-core-console-l1-1-0
PE 710000- 713000 Deferred api-ms-win-core-debug-l1-1-0
PE 720000- 723000 Deferred api-ms-win-core-file-l1-2-0
PE 730000- 733000 Deferred api-ms-win-core-profile-l1-1-0
PE 740000- 743000 Deferred api-ms-win-core-memory-l1-1-0
PE 750000- 753000 Deferred api-ms-win-core-util-l1-1-0
PE 760000- 763000 Deferred api-ms-win-core-rtlsupport-l1-1-C:\Program Files (x86)\Battle.net\Battle.net.7730\api-ms-win-core-rtlsupport-l1-1-0.dll
PE 770000- 774000 Deferred api-ms-win-crt-string-l1-1-0
PE 780000- 783000 Deferred api-ms-win-crt-heap-l1-1-0
PE 790000- 794000 Deferred api-ms-win-crt-stdio-l1-1-0
PE 7a0000- 7a4000 Deferred api-ms-win-crt-convert-l1-1-0
PE 7b0000- 7b3000 Deferred api-ms-win-crt-locale-l1-1-0
PE 7c0000- 7c5000 Deferred api-ms-win-crt-math-l1-1-0
PE 7d0000- 7d5000 Deferred api-ms-win-crt-multibyte-l1-1-0
PE 7e0000- 7e3000 Deferred api-ms-win-crt-time-l1-1-0
PE 7f0000- 7f3000 Deferred api-ms-win-crt-filesystem-l1-1-0C:\Program Files (x86)\Battle.net\Battle.net.7730\api-ms-win-crt-filesystem-l1-1-0.dll
PE 800000- 803000 Deferred api-ms-win-crt-environment-l1-1-C:\Program Files (x86)\Battle.net\Battle.net.7730\api-ms-win-crt-environment-l1-1-0.dll
PE 810000- 813000 Deferred api-ms-win-crt-utility-l1-1-0
PE 1f10000- 20b5000 Deferred ffmpegsumo
PE 10000000-12408000 Export libcef
ELF 7b400000-7b7e2000 Dwarf kernel32
\-PE 7b410000-7b7e2000 \ kernel32
ELF 7bc00000-7bcf5000 Dwarf ntdll
\-PE 7bc10000-7bcf5000 \ ntdll
ELF 7c000000-7c004000 Dwarf
ELF 7cf5e000-7cfc0000 Deferred dwrite
\-PE 7cf60000-7cfc0000 \ dwrite
ELF 7cfc0000-7cff8000 Deferred uxtheme
\-PE 7cfd0000-7cff8000 \ uxtheme
ELF 7cff8000-7cfff000 Deferred libxfixes.so.3
ELF 7cfff000-7d00a000 Deferred libxcursor.so.1
ELF 7d00a000-7d01d000 Deferred libxi.so.6
ELF 7d01d000-7d021000 Deferred libxcomposite.so.1
ELF 7d021000-7d02e000 Deferred libxrandr.so.2
ELF 7d02e000-7d03a000 Deferred libxrender.so.1
ELF 7d03a000-7d041000 Deferred libxxf86vm.so.1
ELF 7d041000-7d045000 Deferred libxinerama.so.1
ELF 7d045000-7d04c000 Deferred libxdmcp.so.6
ELF 7d04c000-7d050000 Deferred libxau.so.6
ELF 7d050000-7d076000 Deferred libxcb.so.1
ELF 7d076000-7d1c1000 Deferred libx11.so.6
ELF 7d1c1000-7d1d6000 Deferred libxext.so.6
ELF 7d1d6000-7d266000 Deferred winex11
\-PE 7d1e0000-7d266000 \ winex11
ELF 7d266000-7d27c000 Deferred libgpg-error.so.0
ELF 7d27c000-7d2f1000 Deferred libpcre.so.3
ELF 7d2f1000-7d30e000 Deferred libgcc_s.so.1
ELF 7d30e000-7d3bd000 Deferred libgcrypt.so.20
ELF 7d3bd000-7d3e3000 Deferred liblzma.so.5
ELF 7d3e3000-7d3ec000 Deferred librt.so.1
ELF 7d3ec000-7d412000 Deferred libselinux.so.1
ELF 7d412000-7d4a0000 Deferred libsystemd.so.0
ELF 7d4a0000-7d4a9000 Deferred libffi.so.6
ELF 7d4a9000-7d4c2000 Deferred libresolv.so.2
ELF 7d4c2000-7d4c7000 Deferred libkeyutils.so.1
ELF 7d4c7000-7d521000 Deferred libdbus-1.so.3
ELF 7d521000-7d5ad000 Deferred libgmp.so.10
ELF 7d5ad000-7d5e2000 Deferred libhogweed.so.4
ELF 7d5e2000-7d61e000 Deferred libnettle.so.6
ELF 7d61e000-7d633000 Deferred libtasn1.so.6
ELF 7d633000-7d667000 Deferred libidn.so.11
ELF 7d667000-7d6c9000 Deferred libp11-kit.so.0
ELF 7d6c9000-7d6d6000 Deferred libkrb5support.so.0
ELF 7d6d6000-7d6db000 Deferred libcom_err.so.2
ELF 7d6db000-7d70c000 Deferred libk5crypto.so.3
ELF 7d70c000-7d7e3000 Deferred libkrb5.so.3
ELF 7d7e3000-7d7f7000 Deferred libavahi-client.so.3
ELF 7d7f7000-7d805000 Deferred libavahi-common.so.3
ELF 7d805000-7d95d000 Deferred libgnutls.so.30
ELF 7d95d000-7d9af000 Deferred libgssapi_krb5.so.2
ELF 7d9af000-7da36000 Deferred libcups.so.2
ELF 7daa6000-7dad0000 Deferred libexpat.so.1
ELF 7dad0000-7db19000 Deferred libfontconfig.so.1
ELF 7db19000-7db44000 Deferred libpng12.so.0
ELF 7db44000-7dbf4000 Deferred libfreetype.so.6
PE 7dc1a000-7dc2f000 Deferred api-ms-win-core-localization-l1-
PE 7dc20000-7dc2f000 Deferred api-ms-win-core-localization-l1-C:\windows\system32\api-ms-win-core-localization-l1-2-1.dll
ELF 7dc2f000-7dc43000 Deferred api-ms-win-core-fibers-l1-1-1
CriticalSection deadlock should be fixed in 1.9.16
by Chris Rankin on Friday August 5th 2016, 8:45
bugs.winehq.org/show_bug.cgi?id=41054

Apparently due to a problem in DLL load order.
catch 22 between performance and Battle.net launcher
by Insilico on Wednesday August 3rd 2016, 0:50
For those of you running the stable 19.5 version and receiving horribly unplayable framerates, I can attest to a large performance gain by using wine-staging and CSMT (22fps with massive stutter on low with stable vs 50 frames on medium with staging+CSMT.) The drawback to that is it the battle.net launcher does not work under staging for me.
Battle.NET update problem (solution)
by Falko on Sunday July 31st 2016, 6:04
If you have problems starting the Battle.NET Launcher after the recent update then try the following:

- Download and activate PlayOnLinux 1.9.15
- Open "Configure Wine" and add the following overrides to the "Libraries":

ucrtbase
vcruntime140
api-ms-win-crt-runtime-l1-1-0.dll
api-ms-win-crt-stdio-l1-1-0.dll

- Start the Battle.NET Launcher and enter your password.*

*If you notice display issues (blank screen) after entering your password then use the Mobile Authenticator and click the invisible link on the bottom of the window and a authorisation request should appear on your smartphone which must be simply confirmed.
nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed.
by Gethin Llyn on Friday July 29th 2016, 4:47
Running wine-staging, csmt ticked, overides in the first post enabled as native, then built in dbghelp disabled, got game running through scripts in 32bit and 64bit, but game freezes with this excerpt from terminal nouveau/pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed. Any ideas? running ubuntu 16.04 on lenovo w510 i7 1.6 ghz 8gb ram . I can't run the game with nvidia drivers, but this is a problem with the nouveau driver. Graphics card is nvidia quadro fx 880m.
July 27th workaround for Battle.Net issues
by Brian Morris on Wednesday July 27th 2016, 8:00
WoW users seem to be having more issues with the Battle.Net launcher than the users of other Blizzard applications are. As such, I chose to post this here rather than on the WineHQ page for Battle.Net.

I am up and running again, but only after setting many overrides. This is due to some of the DLLs that came with this new Battle.Net version. Here is a list of my overrides, all of which are from today, using WINE v1.8.1:

api-ms-win-crt-convert-l1-1-0
api-ms-win-crt-heap-l1-1-0
api-ms-win-crt-locale-l1-1-0
api-ms-win-crt-runtime-l1-1-0
api-ms-win-crt-stdio-l1-1-0
api-ms-win-crt-time-l1-1-0
ucrtbase
vcruntime140
Unable to launch battle.net, reinstall fails
by Lars Norberg on Wednesday July 27th 2016, 6:23
I was unable to launch battle.net, happened all of a sudden today. When trying to reinstall it, which usually has solved this kind of bug, I'm getting the following error:

Unhandled exception: unimplemented function api-ms-win-crt-runtime-l1-1-0.d._get_narrow_winmain_command_line called in 32-bit code (0x7b43bfac).

The files appear to install when I'm looking at the folder content, but both running the setup and the launcher file itself causes the exact same error. Any ideas? :/

I'm also unable to run World of Warcraft directly after this started happening. It exits with the omnious #132 bug which according to Blizzard could mean anything. But for now I'm focusing on the battle.net bugs, as I believe solving these will solve the latter too.

by Wontez on Tuesday July 26th 2016, 22:45
I'm guessing I need to install from source and to be honest I suck at that.
New Connection Error
by Colin on Tuesday July 26th 2016, 20:01
I was playing today and it was working fine, but after an update I can no longer connect. When I do, I get a fatal error notice.

The error says:

wine: Call from 0x7b43d34c to unimplemented function api-ms-win-crt-runtime-l1-1-0.dll._get_narrow_winmain_command_line, aborting

I don't know what has changed, but this is a bummer. Anyone else having this issue?
low fps
by diego on Tuesday July 26th 2016, 18:19
buongiorno a tutti, mi trovo a un bivio... le mie due passioni sono wow e linux, ma purtroppo le due cose non possono convivere, o scelgo di giocare con windows, e devo lasciare al contempo linux, oppure lasciare wow. sinceramente, non ho mai usato windows a casa un po' per lavoro, e non ne ho mai sentito il bisogno.
Ma ora dover fare a meno di linux, nonostante i grandi passi fatti sul gaming recentemente mi dispiace molto, e non capisco questa linea dura della blizzard sul non fare un client per linux. Non so veramente che fare.


good morning to all, I find myself at a crossroads ... my two passions are wow and linux, but unfortunately the two can not coexist, or choose to play with windows, linux, and I have to leave at the same time, or leave wow. frankly, I have never used windows home a little 'for work, and I've never felt the need.
But now I am having to do without Linux, despite the great strides made recently on gaming I am very sorry, and do not understand this hard line of the blizzard do a client for linux. I not really know what to do.
BLZ51900007
by Evan Burkey on Sunday July 24th 2016, 14:10
I'm getting the BLZ51900007 error whenever trying to login. On Arch Linux, with wine-staging installed to latest version. Running on x86 version with -d3d9. Installed libldap. Any ideas would be appreciated
Legion requires GLSL 4.2.
by Chris Rankin on Saturday July 23rd 2016, 9:03
My problem with Legion with Mesa's radeonsi driver is that Legion needs GLSL 4.2, which in turn requires LLVM >= 3.9. However, Fedora is currently shipping with LLVM 3.8, which limits Mesa to GLSL 4.1.

Recompiling Mesa against the very latest LLVM allows the radeonsi driver to support GLSL 4.3, which enables Legion to run.
No luck with Mesa and AMD cards yet
by Chris Rankin on Saturday July 23rd 2016, 6:20
I have managed to get Legion running with Mesa and OpenGL using both Intel Broadwell and NVIDIA 920M. However, I have no success yet with AMD cards. I am suspecting that the lack of support for GLSL 4.2 may be the issue here, based on output from apitrace.
Worked Prepatch now not so much
by Marc on Friday July 22nd 2016, 17:11
Running Ubuntu 16.04, Wine 1.9.14, on a system76 High End Laptop. Before the patch everything ran amazing at highest quality. Now after the patch the ground is missing, NPC's and other players are mostly not there. I was running wine 1.9.13 before the patch and it worked like I said amazingly. I have tried removing WoW and reinstalling it, and then I upgraded to wine 1.9.14. If anyone has any ideas on what might be the problem I would love to hear them, I really don't want to dual boot my laptop!
New/updated OpenGL render
by Björn Bidar on Wednesday July 20th 2016, 12:23
Has anyone tested it? is it how far is it better than the old one?
Game is buggy on legion prepatch
by ragnarokio on Tuesday July 19th 2016, 19:52
Keyboard inputs seem to bug out at times. If i move in one direction long enough and then let go, my character will continue moving in that direction. The exit and logout buttons and commands aren't working.
PTR crashes
by Pavel R on Monday July 4th 2016, 2:36
I'm using Fedora 23. Legion PTR immediately crashes after start. I tried switching to different video settings: OpenGL, D3D9, D3D11 - it crashes all the same with FLT_DIVISION_BY_ZERO.

by starless on Friday June 17th 2016, 14:50
PTR Experience: The game now defaults to DX11 mode instead of DX9. The former seems to cause serious graphical glitches and occasional crashing. After changing this back (under system->advanced), I did not see a notable decrease in performance compared to live. I was not playing on ultra to begin with, though, but on medium–high settings. Running wine 1.9.12.
Legion on Haswell
by Guti on Wednesday June 15th 2016, 8:38
I'm getting CGxOGLShader errors when I try to use OpenGL renderer on Intel Haswell under Arch. I've tried with mesa from repos, mesa-git, wine, wine staging - same shit.

Any ideas?
Back