World of Warcraft

I was hoping that when they fixed the Mac clients that used OpenGL, it would be fixed for us aswell. But today I'm still missing certain grounds effects, so I have this feeling they fixed it only in their OpenGL backend for Mac.

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.

which ground effects are missing for you?
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.

I'm not talking about testing with OpenGL on Windows, but with DX9 on windows.

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.

Could be that a lot of stuff missing, but i cant tell cos i just came back, and its my first time in ToS... and never used Linux.

S

What i meant to say was that i just came back from a 6 month break, and last week was my first in ToS... so i am not that familiar with how the ground effects SHOULD be..

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

ah than we mean the same things, before 7.3 the ground a affect for example at mistress had worked.
Also some ground effets look rather limited like this at harjatan:
www.dropbox.com/s/v761x9cnmsv3ky9/WoWScrnShot_090717_220546.jpg?dl=0

Yes, that weird shit! This was fixed for Mac users yesterday. But since we had exactly identical graphics as Mac users, I had hoped they would fix DX9 at the same time. Unfortunately no.

But I was assured it was going to get fixed. It is already pushed up the the developers.

at for me was an update like now: build number 24976 and now build number 25021

That was the fix for the Mac users.

I found this in forums, someone talking about it happening under Windows aswell:

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.

Good news! Talked to GM using Live Chat. A fix for DX9 is still incoming, developers are looking into it. He just couldn't give me a timeframe.

So we wait, again.

Nice!

Lets not hope it turns out to be one of those Blizzard oh' so often used "Soon" terms then :P

S

Patched Staging 2.0 with only the "ntdll" patches from Awesie. This allows you to log in with 64bit using DX9 with CSMT, this time without crashing when liquid detail is set to Fair/Good/Ultra. Use "-d3d9" as additional command line argument, because DX11 doesn't work yet on 2.0.

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

Did a "git pull", and saw something update, but was not the usual ++++ ---- lines i tend to see when i do a pull..

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

I started fresh. It is a new branch, I also set that branch as main branch. Just get a new copy. (Easiest)

(If you don't want to download again, just fetch the repo changes, and create a new tracking branch for wow-2.0 locally.)

The difference to the compiled binaries in /bin/ between the yesterdays just "git pull" compile vs. the "git clone" compile from the link you posted is none.

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

I have a slight feeling that the previous "overwatch" source gives a bit better FPS overall than your patched version, so im currently back to using that. Especially it feels smoother when on Argus. Maybe some function with effects there?

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

On the page here on WineHQ it sais:

"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

I cannot. I have a 970GTX with 4GB, and if I understand correctly, support for that has only just been added to Kernel 4.12. On top of that, it won't have power management, so it will run at lowest possible speed.

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.

sorry, but good stories and nouveau, not two things that ever happen. fedora in release 27 will be using Nvidia proprietary, with nouveau as fallback. Most of the decent performance, including my own system is nvidia proprietary. I run 384.69 64 bit only, no 32 bit moudles, dkms installed for kernel updates, and currently running 4.12.11-300 on Fedora 26. I have 24 addons installed, used the self compiled patch from the 2.0 staging with liquid detail fixed overwatch patch, linked by Dox in a previous comment here. Dalaran sees me around 30 fps, Argus sees 45-65 even in combat, with several demons at once. DX9 Setting in game at 7, SSAO disabled is the only adjustment, since opengl does not seem to like SSAO. running 64 bit client, and command line launcher. Battle.net also installed, and works, but i prefer the command line launcher, for better control. I have created a desktop shortcut, and I run the GTX 970 4gb OC. I used sudo nvidia-xconfig --cool-bits=12 in terminal to enable power and fan speed control in nvidia settings. my command line for my desktop shortcut is:

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.

I basically run it the same, but through Blizzard App for easy login. I have the same 970GTX with 4gb as you, with the same 384.69 nvidia prop driver. However I use DX9, since CSMT only has use with DX9. 2560x1440 with basically 7 aswell, capped at 66 fps seconds most of the time, running OpenGL triplebuffer from Xorg.conf. Scaling down doesn't seems to have an effect at all on fps. I do have a raid setting to lower shadows and particle density during raids.

I'm just going to repeat, the Overwatch branch is the old branch. The WoW-2.0 branch fixes the liquid detail crash.

I'll try the "export STAGING_WRITECOPY=1" to see if it has any improvements..

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

As to the liquid "fix", i dunno, but i have never instantly crashed either with 2.16-staging or the Overwatch branch, or the new wow-2.0 branch when setting liquid to higher than "Low". When i started playing again couple of weeks ago i started with 2.15-staging and had to use 32-bit, and tested both DX11, and DX9. Not that huge a difference, but set the liquid to recommended "Good". Had some random crashes and memory errors after playing a while... usually like 2-3 hours or so.

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

Trying to shortly cover all your points:

- 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/)

1. I do not crash instantly when setting liquid to Fair/Good/Ultra. The water effects do indeed change as it should. Tested multiple times at several places in StormWind (Assuming you mean the fountain in the dwarven district?), and by the canals in SW. No problem switching back and forth. This is with the "Overwatch" branch, BUT this is compiled from YOUR previous github BEFORE you changed the "master branch" thingy to the "wow" version.

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

Ooo...

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

IF = Ironforge, fountain just outside after you leave the portal room.

Hehe.. yeah... Doh, sorry :P

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 :)

I think you are experiencing a placebo effect. They are both the same source:

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?

I least for instances like Firelands wow crashed for ever when entering it when using the overwatch branch.

Just going to repeat, the Overwatch branch is old. Just rebuild, with a new build, the wow-2.0 branch from the repo:

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).

"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?"

As i wrote before, i did a new clone from the link you posted :)

S

Do you have a complete overview over what is the total difference between "your" wow-2.0 patched version vs. the previous 2.0-overwatch version that used to be available?

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

This is the repo I got the patches from Awesies repo, it is based on Wine 2.0 (so not on staging): bitbucket.org/awesie/wine-overwatch/commits/all

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.

Seems indeed like a daunting task, to commit all those patches, so id rather not figure out how to do that exactly...

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

I am running from the link Dox shared, with 2.0 staging, and liquid detail fixed. Downloaded and compiled the using the wow64 build setup linked in the winehq.com website, on my AMD FX 6300 6 core. I have a GTX970 4G DDR5. I compiled the system, after using export CFLAGS="-march=native -O2" so that the compiler built the binaries for my cpu. I run 24 addons in game, same as my windows 10 setup, and I manage 35 FPS in Dalaran, 50+ on argus, even in combat, and no drops in dungeons or raids. Settings are at 7 and I even left ssao enabled. I see slightly lower FPS than my windows 10 WoW experience, but not enough to bother me. I have csmt on, glsl disabled, and other env var on my command line. see one of my previous comment in this thread for the desktop shortcut command line that I use. Hope this clears up some confusion. I ran against 2.16 and the fps in DX9 was worse on 2.16. Even compiled the source, and it still was not as good. See that 2.17 is out, may try it this weekend.

I have set my viewdistance down to 3 to not get those dips when i fly over large zones.

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

Viewdistance issues, try fiddling setting:

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

SET worldPreloadNonCritical "0" improves loading times when zoning into eg. Dalaran and such.. With the default "1", wow loads a lot slower. From what i gather is that it kinda loads textures "on the fly" a bit more after you move in, rather than load everything before you zone in.

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

Since the latest update (2.16), Wow works again with normal wine-staging and liquid effects can bet set to more than low (for the 64bit client).

Good to know. I'll build it later.

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.

Well, I tested Staging 2.16. d3d11 feels really smooth atm. Even though it give only around 30 fps for me. It even feels better then d3d9 with the same 2.16.

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.

Thanks a lot.
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.

"It's a bit annoying that ppl doenst read."
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.

I went to the same round of testing as you. I'll summarize:

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".

I also used the following additions to Config.wtf:

- 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)

Link in last post didn't format correctly, because of the ) at the end: wowwiki.wikia.com/wiki/CVar_gxTextureCacheSize

running 2.0 with ow patch, seems to do fine. Just a question, are the Staging settings env or reg?

Hey! I'm glad someone is using it. I see you are maintainer of the App WoW here aswell. Perhaps we can get together a good howto, and consolidate some settings for increasing FPS?

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.

Running nvidia proprietary 384.69. according to readme in the driver, the threaded is now enabled by default, so the env var is not needed.

Thanks a lot for your instructions Dox!

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

You're welcome. I didn't do the patching, the credit goes to Gamax92. If you want to clone out of his repo, you have to clone with "-b branch --single-branch", I just forked the repo and made it the main branch to make it easier for people. And what do you know? It does!

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.

Yeah, i am using the different nVidia tweaks, as you posted and a few custom ones in my xorg.conf :)

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

My repo is just a clone of Gamax's repo, just with another branch set as master. This branch won't be changed at all. It is just a branch based on Staging 2.0 with all OW patches applied.

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.

When i try to start Wow.exe (the main game, not the launcher) i get the error
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

Temporary workaround for 2.14-staging and 2.15-staging is to run the 32-bit client, or run in XP mode (which forces the 32-bit client implicitly) but then the memory leak returns. :(

Update to wine-2.15 and use the 32bit client, it works fine (bad performance though).

Just adding some information that is in my brain here at the WineHQ WoW page. Feels like this is a good as place as any to post it. I cannot post in US forums, and EU forums linux talk is minimal. I'm sure someone will spot this.

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".

Lutris is not my program O.O. I literally organised then copy and pasted the comments from the WoW forum... because it worked for me and I thought hq-people wanted a quick fix for the patch.

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.

What solved the crashes to me is putting my water to low. See also: bugs.winehq.org/show_bug.cgi?id=43641

I don't know if this helps anyone or not, but here are my observations..... I run on Ubuntu xenial with a Nvidia GTX 560. Have had 64-bit Wow running great for years.

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.

This mirrors my own experience with Debian Jessie based antiX Linux. WoW 7.2 worked perfectly well with reasonable to good performance, comparable to Windows with my creaking Nvidia GTX790. All was good until 30th August: Patch 7.3. With Wine 2.16. Launcher worked, WoW wouldn't start from the launcher. Starting it directly with Wow-64.exe (or Wow.exe) returned a dialog box saying "Game Initialization Failed!"

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.

It's a bit annoying that ppl doenst read.
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.

"The 64bit Client works with direct X 9 render as long liquid details are up to low. "
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 -.-

AMD 8350
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.

Still crashing for me (same error 132.) I do have a Radeon card. Might this be the issue? Someone else (windows) was having a problem here, too: us.battle.net/forums/en/wow/topic/20758887160

try to look at this bugs.winehq.org/show_bug.cgi?id=43641

You might be onto something. Although I set detail to good (it was on fair), and I'm still crashing.

OK. I'm playing, water set to "fair," and I'm able to play. Haven't crashed yet. And i'm in the area where I normally am.

Sorry Atonner, you say "* env variables or hide them in a script" and "i have all the above wrapped up in a shell script". Where how would I use/set env variable and/or could you suggest how the shell script would be written (with example I could edit?)

Thanks for your help!

These are just variables for the Nvidia libraries to give better performance.
(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).

I downloaded wine-overwatch-2.15, and the game actually works, yay! I removed all my library overrides to see if they're still needed, and apparently not. But are there some that still improve something? Anyone using anything?

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?

I don't even see DX11 as an option.

Hi,

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.

I think it's a WoW bug. There are numerous posts in Tech Support and General about people crashing to desktop randomly. I can reproduce it near the keep in Stormwind and in Broken Shore.

But for me this crash is not random, but every time within the loading screen as soon as it finishes up.... I dont even get to crash somewhere :(

The randomness is the location at which you will crash, not when you're going to. Once you run into such a location, the game will just freeze and the access violation will pop up (as you explained). If you try to load that character again, the game will crash as soon as loading's finished (so you're still on the loading screen when the access violation pops up). What you can try to do is log into another character, play a bit, then log into your crashed character and move away from wherever you were. Chances are however that you will still crash whenever you zone, load, or move into range of something.

I've found if I switch to DX11, I can play fine (but get a weird blue sheen to everything, along with odd text.) But if I switch back to dx9, I crash again (access violation.)

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?

Switch to Dx11, that solved all my problems with crashing in some places... But its slower than Dx9, at least it works.

Posted by Pontudinho
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.

This version works for me, but is very slow and high CPU consuming ...

Copied over from: us.battle.net/forums/en/wow/topic/20758857016
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]

Its nice that you want to help others with your guide, but some other just don't want your advertise for your program.
Can You point out whats the error and show the patch(es) that it?

bitbucket.org/awesie/wine-overwatch/commits/ check the ntdll patches.
Not a proper solution, so they won't become upstreamed.

bugs.winehq.org/show_bug.cgi?id=40479 is likely the error

Are these compiled like Staging is? (That is, patch the source, compile WINE?) Or are they compiled separately from WINE? (It says it needs a shared WoW64.)

github.com/gamax92/wine-overwatch/issues/5

Answered my own question, for anyone else looking.

Is it possible to use gallium nine withim wine-overwatch?

Patch 7.3 came out today and as it is closes with a "Game failed to launch" error. The battle.net launcher works fine still...

They switched to the same protection like Overwatch and SC1 have.
Post logfiles and try gamac version for overwatch.

Hello, guys! I've decided to play wow a bit again. Been struggling with battle.net all day with no results.
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!

Please ask at the appdb entry of the battle net app

apparently i'm an idiot yet once again! wine-2.14 staging works just fine.

Does someone faced with very slow loading especially in Dalaran?

It happens in windows or linux. happens on other computers here in the house. first load into dalaran takes a very long time. Definitely not a problem on our end, as quite a few people in my guilds are also having the same issue.

Steve

But in windows my loading to much faster...

Then try this. Put elevator=deadline on the grub command line, and reboot.

This don't help me.
# cat /sys/block/sda/queue/scheduler
noop [deadline] cfq bfq
I noticed when I play with DX11 my loading becomes a bit faster.

Add
SET worldPreloadNonCritical "0"
in Config.wtf. That fixed it for me.

Yes, it works! Thank you. Now my HDD fully used on loading.
Without this option HDD periodically don't used while loading.

After installing the Development 2.12 my FPS in wow dropped to 1 and the game became completely unresponsive. Switched to DX9 and set GLSL to disabled with winetricks. FPS now around 45-50 in world, 20-22 in Dalaran-Broken Shores, 18 in combat, solo or raid. Running Fedora 26, kernel 4.11.9-300 selinux set to permissive.

Which settings/hardware do you use?
I play at 4k and play just fine with staging, csmt and d3dx9

in game setting level 7 for everything. even leave ssao enabled, and seems to work fine. Like I said, DX11 is where the problem lies. I can run DX9 in game, and get good fps and the game is playable. Legion is optimized for DX11 and until 2.12 Development from wine, worked good with DX11. Reverting game client to DX9 until the next wine release. GTX 970, Nvidia proprietary 384.47 and 4gig on card. AMD FX 6300 six core, 16GB ddr3 1600. Kernel 4.11.9-300 on Fedora 26.

I have been using staging just fine with DX11 and although I get FPS dropouts in Dalaran and raid or PvP environments it's pretty stable with decent output. I recently updated the WoW client (and perhaps wine) but now I can login but after 10-20 seconds on the character screen my game locks up.

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.

I have the same issue here.

And I too.

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).

Been having this issue with the 64-bit live client, it started about a day before the 7.2.5 patch dropped: 5-10 seconds after login, the game freezes (need to kill with xkill or wineserver -k).

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?

Same problem here. Wow either locks up on the character select screen or stops at 90% load bar. The 32-bit also works for me atm. And like you said running out of memory which makes playing really annoying.

-mtune=native is the issue, look at the bug report bugs.winehq.org/show_bug.cgi?id=42805

Thanks for the info! I've tried building with 'march=bdver2' (for my processor) as well as 'mtune=generic' and it still freezes in both builds. Perhaps I'm doing something wrong? Or this solution doesn't help with my processor? Let me know if there is any useful output I can contribute.

Which gcc version to you use? I've got some issues with builds from gcc 7.1.
Generic did the trick for me (my cpu is broadwell ep).

using gcc 7.1.1 20170528
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

I am experiencing the same issue, if I roll back to 2.8.x it's fine (as of a week or so ago) but anything later than that locks up shortly after opening the Char Select Screen or if I try to sneak in a quick selection it will lock up at ~90% in the load screen.

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.

Try to build with GCC 6.3 and mtune generic.

I've tried the latest wine-stating and hit the same issue.
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.

i compiled your PKGBUILD on my system, as-is, and the game runs fine with no freeze.

I've found the patch that makes issues.
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.

I do not know how to install this patch, could anyone help me please?

The simplest thing would be to downgrade to wine-staging 2.8 until this problem gets fixed in the latest wine-staging. Exactly how to do this will depend on your distro, but it's easy to look up. Otherwise, you can compile wine + the staging patches (excluding the patch that causes the issue) from source using these instructions: github.com/wine-compholio/wine-staging/wiki/Packaging

Thank you for responding. I tried to install the patch and mention above: github.com/wine-compholio/wine-staging/blob/ee5545a45f164d640c9b1cd6575a5645afaeb4a9/patches/patchinstall.sh

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

Has this been reported in the bug? It would be nice if the next release fixes this issue.

I run Fedora 25, can not use pkgbuild, can you give me something, that lets me compile please. I miss being able to play WoW. Thanks.

Would you mind showing the steps used to build the wine with the package build. I am on 64 bit and need WoW64 windows support as well. Any help is greatly appreciated.

had the same problem with wine-staging. wine-devel (& wine-stable) seems to work for now, but the performance is not as good.

I'm having the same issue. I tried wine-devel, and it does work with no hang, but it's unplayably slow.

Issue is sorted for me, Wine-Staging 2.11, WoW 7.2.5

Since my Windows PC died I've been able to get onto private servers of various expansions just fine, but the battle.net launcher, I cannot get to run, does nothing but crash. I think if I had all of the game files for 7.2.5 I should be able to connect to live without the launcher, but I need those. If anyone could help out by either directing me to a direct download of the files, or uploading your wow directory to some google drive accounts. I think I can get this to work if I can avoid the launcher.

i've had success using 'winetricks corefonts vcrun2015' on a clean 64-bit prefix and then launching the blizzard app installer. Currently using wine-2.10 (Staging) with CSMT enabled.

I have a "5.1" channel speaker setup on a "7.1" onboard soundcard. Regardless of my ALSA configuration, WoW only recognizes 2 channels. The console tool "speaker-test" and numerous other programs confirm ALSA is configured correctly. The audio tab in winecfg recognizes 5.1 availability and I set all the outputs to 5.1 from the default of stereo. I even tried to put this in my ~/.asoundrc:

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

Do native apps recognize 5.1?
I'm using pa with a 5.1 profile and Wow sets the sound to 5.1.

Yes, and like I said, I can confirm with speaker-test that it's not just 5-channel stereo. It has worked in native games for years now. A long time ago, it used to even work for me with wine in WoW too, in fact. But it's been broken in all Blizzard games for a while now.

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.

No just installed it with Linux. But this makes no difference.
Maybe there's an issue with alsa and wine.
Check the sound tab of winecfg.

I've definitely done that too. I'm really out of clues. I suppose pulseaudio could be adding something... but I've started to suspect it's actually a registry thing.

Then try a new prefix.
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.

New prefix?? Do you really think I didn't try that about a thousand times? Do you realize I've been playing WoW in wine since release?

"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.

>New prefix?? Do you really think I didn't try that about a thousand times? Do you realize I've been playing WoW in wine since release?
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.

You're right. I didn't need to be rude. I'm sorry. I know you were just trying to be helpful. It didn't seem like you read my initial post very well though, because twice before I snapped, you asked about things I'd covered in the post.

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.

I installed the 4.12-rc4 kernel and Noveau driver with latest wine with Gallium 3d support -
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 .

Well . Wow runs better with Noveau (padoka) and wined3d9 pacth than wine staging with nvidia 382.22 drivers . Today i tanked all raids with 1080 P with the lowest settings .9-30 dps boss fights . Thats playble - But if nouveau driver could clock my card it had been over 100 fps - ;( Im ordered a budget gaming card Msi rx 560 4gb oc to see if AMD cards with open source driver are better . Fingers cross that my 100 dollars are well spent ;)

wine-staging-nine on Arch linux .

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 .

Running wow-64.exe, all the reg hacks worked except useglsl disabled. when i try that, wow-64.exe complained about no 3D. set to enabled, game works. decent performance on my amd fx-6300 with geforce gtx 970 and nvidia proprietary version 381.22. No more logging to windows to play one game. game config is using DX11, and i am running wine staging 2.8, linux kernel 4.10.17.

I used the same reg edits and the 381.22 nvidia drivers, but I used D3D9 instead of D3D11 and it works with useglsl disabled. Windows 10 option, Wine Staging 2.8, kernel version 4.10-21. Geforce 1050ti, intel e8400 cpu. Not that great FPS (30ish in dalaran), almost to a crawl in big raids, but not bad overall for a computer that is largely 8+ years old.

You don't mention, are you running wine64 to launch wow64.exe? Also, I have gone into grub and set elevator=deadline on the linux command line. and that seems to help with disk access. Dalaran for me, on Uther, around 55Fps, graphic setting is 6 but SSAO needs to be off. Drops to 35Fps in combat, regardless of group size. Join groups to kill world boss, no fps drops. Did have to disable one addon, that was dropping me to 5fps in combat. Once I did that the game got really playable. I no longer log to windows, to just run the game. I am thinking I may never have to touch windows again. I am working with the addon author of the one that killed my fps, to see what can be done. Legion is optimized for D3D11 and when I do try it with D3D9, the fps suffers. I have 17 addons installed, and no problems with them. I log to windows, to update them, as curse has no linux client. I could use the website, to download and install the zip files, but I am lazy. Prefer just to copy the addons folder once it us updated in windoze. Have fun.

it is wine64 to launch wow-64.exe. i also set elevator=deadline in grub and it seems to have helped as well, also switched over to enabled glsl and D3D11, seems to work better overall. Less slowdowns. probably as good as it will get for me until i either buy a new mobo/cpu/ram or do the gallium-nine route again like i had with my older AMD card before.

I think as the work on the dx11 api progresses, we will see more improvement in game performance across the board for linux based systems. I would dearly love to tell Windows where to go, but for now, I do have to use it occasionally. At least I can limit that some more, since WoW is working in wine. Also fixed the addon that was causing my fps to drop in combat. I stay around 40Fps even in world boss raid groups. i am glad that my suggestions aided you in some small way as well. Enjoy!

What is the addon you needed to disable? I have the same issue. The game (on my aging hardware) is quite playable, but, in large World Boss groups or large raids, I don't know that I hit even 5 fps...


M.

Carbonite main module, which is required for the quests, notes, and warehouse modules that I run. I would drop to 0 fps in combat and my character moved like a claymation stick figure. I found that if I went to the carbonite world map, right click, select Show... and unchecked the Show Guides POI that I could keep using carbonite. I am currently working on a fork of the main addon, to see if I can get the guides back. Not a deal breaker, as I can see the fp on the map, so still know where everything is. Graphics set at level 5 but turn off SSAO since the opengl render that is emulating the dx11 calls, does not support that feature. Have fun.

Alternatively, you can use the Lcurse python script at github.com/ephraim/lcurse to update your addons on linux. It is very clean and simple, and can update addons directly from curse or github. I use it and it works superbly! Open source and doesn't require windows :)

Tried it. Won't build on fedora 25, missing PyQt5 and can not find a repo that contains that one package, so source does not compile.

@ Steve Ebey

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).

tried your steos, tells me no such directory, when I try to import addons. I have set the directory, and made sure it is correct.

Any suggestions?

Oh, you need to point at the directory with wow.exe in it. For me it is set to:

/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.

Got it working, had to match the exact spelling of the folder, for the addons. When i copied the installed wow from windows, the names went lowercase, so since I know linux is case sensitive, I had to modify application.py to match the spelling. Now it works, thanks for the help.

Same problem here. I couldn't log in later in the same day. p11-kit can't be located or something.

at least in EU, blizzard has some issues with their login servers.

I'm currently running F24, and wine-staging from the WineHQ repo. (currently 2.7)
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?

Okay -> I'm going to conclude this is a wine-gecko issue :


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.

I had this issue, How I resolved it was:

Change Windows Version to Windows XP

Open Wine configuration (winecfg) and change setting at the bottom

In addition to this, after running the Blizzard App and logging in to Battle.net, you can then close it and reset the Windows version in winecfg to Win 7+ again. The Blizzard app willl now display everything correctly, without the limitation of using XP mode, as this will only run the 32-bit WoW client.

Interesting. That worked, actually. I didn't expect it to. A couple other notes about this I just discovered in the process:

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.

Unfortunately, launching the Battle.net client with WinXP mode forcibly disables 64-bit mode too, and seems to re-introduce an old memory leak bug.

Yes, happening here too in 2.6 and 2.8. Gecko was my assumed culprit as well.

I wonder what some of the submitters did for their wow 64bit client to run via wine. For me it always freezes after some times.

How is your wine compiled?

since I use gentoo, it's the basic repo wine, compiled with gcc-6.3 and staging useflag (so wine-staging 2.5 currently)
Since the performance is worse than with wine-staging 2.0-rc6, I compiled that one manually for playing.

do you use -march=native? thats was the issue for me.

oh, didn't even know that command existed. Just tried starting the game using that and it seems to work.

Have been playing wow for the last week, logged on this morning, and the game would get stuck at "retrieving realm list" and not connect. Nothing had changed on my computer since yesterday, and cannot figure out why it has suddenly done this.

Has anyone had this issue and fixed it? I am using wine 2.4

I'm having the same issue as you. I am using the current 2.6 staging version of wine with CSMT enabled. I have set my Windows version to WIndows XP as suggested in another thread, but still the same issue!

Has anyone got the same performance with latest wine-staging as with 2.0rc6?

wine 2.5 staging is very close to the peak of 2.0rc6, but it's still not quite there yet. On the flip side, d3d11 has less fps drops, especially when turning, but Suramar is not very enjoyable with 20 fps on average...

Since april 2nd I encounter sudden and spontaneous reboots; In the middle of running around in a not-too-crowded area, where the system performs smooth, all of a sudden my system reboots. In the past I've seen this as well, but then I related it to thermal issues. I fixed those and monitor my system with monitorix; there I see no enormous spikes in temperature, everything is below 60C. Thermal problems seem unlikely.
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.

Well, thought of setting up a new wine prefix; this time a 64bit (the other one was apparently a bit old already) and now can run the 64 bit client and no longer encounter such issues.

Have to play DX9 though, DX11 is unplayable slow.

I have strange problem, it started today, without any change to computer
If I start game executable, it is unable to connect. I can only start it from launcher.

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?

This is also happening to me. Is it mostly Dalaran/Org/SW? I don't believe this is fixable, it's to do with us communicating with battle.net, and that's always been atrocious. However, if you are ALSO having the issue where your abilities never work, such as when targeting a mob and it says "Invalid Target", hit left alt. It seems that this fixed THAT issue for me.

I have had this for years. Is there a tip to solve this?

Solved, in Ubuntu I disable key setting key keep pressdown.

That's annoying though, especially if you use the terminal and repeating key strokes for other stuff.

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.

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?

Can you describe what you are trying? Because its still hard to find out how you try to run / what you have done/installed until now.

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.

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.

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?

Ohyeah: this is on all of
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

Not sure if 85 is cool enough. My laptop has a 85 as a threshold and starts to drop CPU freq on this temperature.
I have 30fps cap for Legion content and it keeps temperature below the threshold and I'm happy :)

seems pretty hot, agreed, but i think its in spec for this chip. been watching the throttling occur in dmesg, always at the 96-97 point there is a block of text about it, and sometimes i get the crash without getting anything in dmesg.

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! ;)

FX-8120 (8 core to 3.4 GHz)
gtx 1060 (6GO)

16 Go

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

#Multprocessor Free
wine reg add "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion" /v CurrentType /t reg_sz /d "Multiprocessor Free" /f

Looks bedder now - but System Monitoring say that my CPU is to weak

i3 the 2nd gen ;)
Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz


im try to find a i7 3rd gen for my motherboard ;)

Your cpu should perform better then my i7 since I play on laptop with mobile i7 cpu. It designed for power saving, not for gaming)

best for boost fps is usegsl is disabled

wow is work perfectly with D3D9 & gtx 1060

much better with your settings, thanks!

if nothin happend.. its ok...
in Raid ~15 ppls - @ boss pull frames drops

THANKS THANKS THANKS !

Could u Tell smth about your system?

I tried all these settings, but I'm still getting around 20-30fps in a busy Org instead of 80-110 when playing on windows.

6th gen i5
32gb RAM
1060 6GB

edit* GTX 1070 6gb

After trying those registry adds, and starting wow from the desktop shortcut i get a box that says failed to find 3d device. Are you using d3d11 or opengl in the config.wtf?

DX9

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

This is a command I use to run WoW:

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!

Any suggesstions would be helpful. TIA

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

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.

2.2 has been released. Did you try?

I mean wine-staging 2.2

Yeah i did give it a go.

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

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.

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!

i7-3537U @ 2.00GHz up to 3.1 in Turbo Boost dual core with hyper-threading, 8Gb RAM, Nvidia 740M, nvidia-375

Could u send me the Settings (Wine & WOW)

on i3 16GB Ram - Geforce 1060 only get around 25 FPS - and Drops in Raids

Hi, I'll send a bit later.
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

Sure but i

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?

This is not something that i believe is Wine related tbh, but rather some changes made to the wow client as of 7.1.x.

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 :)

Well I guess time will yet tell whether that fixed the zone loading failures, but it made a dramatic improvement in load times, thanks! Even big zones like new Dalaran are loading in less than 1 second.

work, but low fps min 5 max 20.

What's your hardware?

cpu: i5 4690k
gpu: gtx 960

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.

I'm not sure this where I should be asking this but how exactly does one make a symbolic link to the correct library? My issue in particular is that I can't even run the game under DX11 even though I do have Wine 2.0 staging. Changing the config in WTF to SET gxApi "D3D11" doesn't help - the game starts with low resolution but the API is still DX9. Starting the game from terminal and adding -DX11 results in the same thing.

You can make a symbolic link by using command 'ln -s '.
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.

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?

I had the same problem with the same version of wine on Debian (unstable/sid) and discovered that contrary to other statements on this wiki, I still required at the very least the msvcp140 (native, builtin) dll override just to be able to log in. Some of the other formerly-advised dll overrides however, while no longer required, still seemed to improve the speed of the Battle.net client start-up and authentication. The same issue seems to be happening still with Starcraft II but people on that page of the wiki have already started figured it out.

This didn't help me. Can you list all your dll overrides?

I could have sworn I replied to this later that evening, but I must have merely dreamed that I'd done so after falling asleep. Anyway, here they are. Sorry for the unnecessary delay. I think I got these from the "Starcraft II" winehq page:

api-ms-win-crt-math-l1-1-0
api-ms-win-crt-stdio-l1-1-0
msvcp140
ucrtbase
vcruntime140

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.

Ah, ignore this. It has just updated silently, without progress bar or showing it any other way. Just had to give battle.net some time.
Now everything works.

I updated yesterday. Battle.net needed to update itself first. WoW update paused itself stating "other software is currently being upgraded" or some similar.

Try the latest wine staging version 2.0-rc3. It gave me a giant fps boost, now the game is actually playable again! :)

Can you go to you garrison, turn around and note fps? Do you experience any lags/major fps drops when moving camera in a garrison? What's your resolution?

I am using 1600x900 windowed mode and draw distance set to 4. When standing still in garrison i have 75 fps. But when turning around camera very fast it can drop all the way to 45 fps but no further. I only get some slight stuttering the first 10-20 seconds i enter.
My specs if curious:
AMD FX 6300 and a GTX 960

Also forgot to mention in Dalaran i still get many lag spikes, but in most of broken isle lag spikes are very minimal compared to what it used to be.

I think I get 10-20FPS boost switching from 1.9.17-staging to 2.0-rc3-staging

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

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

Same card, similar issues.

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.

I used the opengl switch and got the same artifacts and graphics issues. However, I usually use the d3d9 switch instead and gets ride of the graphics issues. I have GTX 970 and using 375.26 getting 50 to 90 FPS in Dalaran (Broken Isles). You can change the setting in the WTF file or adding it to the command: wine Wow64.exe -d3d9

and you dont get any freezes using the 64bit version of wow?

No, I don't get any freezes.

which wine version and distro?
with or without csmt?
got an NVIDIA card and __GL_THREADED_OPTIMIZATION=1 ?

Fedora 24 wine rc 2.0, running nvidia 375.26 with debugging off and __GL_THREADED_OPTIMIZATION=1. Not sure about cmst but it's the wine version that's is currently in the fedora repo

what do you mean with debbugging off?
I you open winecfg and look for staging you'll see if csmt is enabled.

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.

Depends on how you define "mostly working".

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.

Thanks for the reply, this was one of the most informative posts here.

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 =)

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.

They do not know how the game works, so their tests are useless.

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

Yeah, I'm getting this too. Will look deeper.

Re-entering my e-mail address in the WoW login screen gets me to 'retrieving Realm List' and then it errors out again.

Debug output shows:

fixme:secur32:schannel_get_mac_algid unknown algorithm 200

which may or may not be related.

I'm using arch (with wine-staging-git) and I don't have the issue.
Do use the launcher?

Using Xubuntu here. Have tried with and without launcher.

So, this seems to be an issue with the Ubuntu builds of Wine 2.0rc2, which Mint uses as well. They were uploaded to the repo on the 21st of December 2016, right about when you started having issues, and I upgraded a few days later and am having the same issues.

I'm currently seeking older packages to downgrade to and retest. I'll fill you in when I have news.

So I found a copy of Wine-Devel 1.9.24 in my apt archive and installed it.
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.

So you can go look it up and whatever.

The RC5 builds seem to fix this.

Hi,

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


-Dave

In openSUSE Leap 42.2 work as a charm.

Thanks, David

32 bit just disconnects and wont log in any one know how to fix it?

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.

I had the same issue. Try to install the 'libtxc_dxtn' package (or one with similar name), it fixed the issue for me.
It's a library for some texture compressing format, probably used by Blizzard.

Thanks! After installing libtxc_dxtn.i686 and libtxc_dxtn.x86_64 I no longer see this issue.

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?

Sounds like the game is loading into ram. You can make less ram available for WoW and force your computer to fetch stuff from the hard disk more often. You can use swap space instead of ram, so that WoW has to write stuff back to the disk more often too. I only recommend doing this if your drive's speed is much faster than your ram, or if you want the game to be constantly freezing up as it waits to load components from disk.

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.

i dont mind it usuing ram but it shouldnt be going into 6 and 7 gbs to play it. There is a memory leak somewhere .

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.

Yup, seeing the exact same thing. Glad it's not just me. Have switched back to Xorg, although the latest Flash plugin crashes without Wayland.

Just enable virtual desktop in your winecfg
Work perfectly with wayland.

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 !

Install this package: ttf-mscorefonts-installer
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*

Thanks !
That's work now with ttf-mscorefonts-installer ! :)

And this other problem fixed by updates

I have the same problem, started with a BN update about 4 weeks ago. MS corefonts are installed system-wide. I've tried with a new prefix, installing corefonts in POL, different versions, different overrides. Nothing helps.

Some additional info in case somebody knows how to help: Debian Jessie x64, wine-1.9.23 x64
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.

After some more searching I used my old install again and deleted
~/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.

Its worked for me with only installing corefonts and set win version to win7.

Also, you should turn off hw acclareted browser feature at settings, cause it's may cause "err:d3d:context_create Failed to set pixel format 5 on device context" errors.

do you talk about the 64bit ver?
which browser hardware accerlation where?

I talking about the 32bit version. Actually, i wanted to send those posts to the battle.net launcher topic, so the hw acc browser option is on the battle.net settings. Anyway i did ran @ 30 fps on worgen starter zone (phenom II x4 955, radeon hd 5750 512mb, 8gb ram, ssd) with this steps:
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

i only have intel hd 5500, it'll die then

wrong thread, sorries

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.

oh, and when 64 does load, no issues with other players' textures there.

Report: after repair 64 bit version works okayish.

with the launcher or how?

Yes, somewhere in game settings in the battle-net launcher i clicked on 'repair' and freezes stopped. Managed to play withouth problems for about 3 hours yesterday.
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.

Naah, not working today :(
freezes are back, yay..

Okay, I found the way!
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.

does it still works? Could you test the dx11 renderer too? (remember to set the graphics too level 3 or dx11 bugs)

Wine doesnt have full d3d11 implemented so it won't work.

it will if you limit the graphic setings to lvl 3.

Well. No. It still freezes time to time. With or without launcher, with or without scan&repair.
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.

So, I finally managed to get rid of freezes. Update of wine from 1.9.20 to 1.9.22 helped a lot.

did you change anything beside the wine version?

No. I'm even using the same prefix.
Wine is staging with csmt enabled.

You have an Intel HD5500.
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

May I ask you how did you get wine 1.9.22?

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.

The same ebuild works for wine 1.9.22, too.
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.

but does the x64 version work for you?
I'm now at 1.9.23 and still get a freeze.

Sorry for the late feedback, but I have been busy lately.

As for Björn, even in my case it still freeze even with 1.9.23. :(

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?

Yes, this seems to have gotten much worse with Legion.

(woops, was supposed to be a reply to "camera lag" below)

As said below, the solution to the camera issue:
SET gxTextureCacheSize "1024"

I tried that already, it doesn't actually work for me. Maybe its because I only have 1GB of ram to begin with, but I also tried lower values.

I have 6GB and tried different values, no change. I suspect we have more than one issue here...

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.

upgraded to wine-1.9.21 (Staging) and battle.net seemed to be happier.
Still not sure what was broken.

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.

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.

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.

Whops. Meant to reply to the "Extreme Lag Issues" post below.

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

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?

Have you tried going into advanced system options and disable "Reduce Input Lag" it worked for me when I had the same problem.

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.

This helped me out a lot, except in busy places like Dalaran, but at least I can play normally now. Thanks!

Are you monitoring your CPU usage? I have an older discrete graphics card and even it isn't reaching more than 70% utilization (using the aticonfig --odgc command), while the CPU is over 100% (the top utility uses per-core usage so over 100% simply means more than one core is being used). However, if you'll look at the outstanding bugs for WOW you'll see that WINE isn't doing a very good job of parallelling the tasks involved in rendering, so that in reality it's mostly a single core getting used. In other words, you're probably CPU bound. I definitely am... every time there is a lot going on physics wise (e.g. lots of players around, complicated dungeon mechanics) i get slide show FPS. And the gpu usage never gets higher than 70% or so.

"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) "


same problem here!
~5 fps en citys
~40 alone

any solution? :(

heey has this been fixed? :)

bc i have the same problem :(

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.

install with winetricks vcrun.

Try with vcrun2005 or vcrun2010

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...

[UPDATE]

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.

OK... did some more tweaking... pbuff i guess shouldnt be used, FBO gives MUCH better performance... dunno why i chose it honestly...

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 :)

Hi, can you please write down step-by-step which tweaks did you used?

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. :(

Sure

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.

sorry... Arch Linux ;)

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 :)

Thank you very much! I am using Antergos which is basically Arch Linux as well.

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.

I've had some relief from setting "GL_ARB_vertex_buffer_object" to "GL_ARB_vertex_buffer_object2" as GL_ARB_vertex_buffer_object suposedly helps smooth things out by changing the way OpenGL caches things. The appended 2 i believe is suposed to flag some modification to that particular useage that de-syncs it from the framerate which may or may not help depending on your use-case.

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 :)

Thank you very much! I am using Antergos which is basically Arch Linux as well.

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.

Hey Erika!
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

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. :(

I don't know why it came as separate topic; I was anwering the thread "64bit client new update" made by Björn Bidar.

Is it possible to delete this?

Sorry about this.

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

Just for reference the wine version I use:
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

Has anyone tried to client since the new update? I run it currently and it works without issues.

freezes again, am I the only one having the issue?

no and this not wine issue - its network issue i try on windows - same

Were you able to determine what in the network affects this? I'm having the same issue with the latest patch and wine 1.9.18.

nvm
just try repair on WoW its help me
some files broken after last update

Are the benefits of repairing still working?

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.

after repair not recommended run wow via battle.net
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

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"

What do you changed other than the usual settings?

wowwiki.wikia.com/wiki/CVar_processAffinityMask
wowwiki.wikia.com/wiki/CVar_gxTextureCacheSize


SET processAffinityMask "255"
SET gxTextureCacheSize "2048"

Install Wine-staging & winetricks
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\Software\Wine\DllOverrides" /v *wininet /t reg_sz /d native,builtin /f
wine reg add "HKEY_CURRENT_USER\Software\Wine\DirectSound" /v DefaultSampleRate /t reg_sz /d 44100 /f
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\OpenGL" /v VideoMemorySize /t reg_sz /d 2048 /f

wine reg add "HKEY_LOCAL_MACHINE\Software\Wine\Direct3D" /v DirectDrawRenderer /t reg_sz /d opengl /f
wine reg add "HKEY_LOCAL_MACHINE\Software\Wine\Direct3D" /v VideoMemorySize /t reg_sz /d 2048 /f



#Edit path WoW & work +/- 35 fps average
__GL_THREADED_OPTIMIZATIONS=1 wine "/home/drthrax/Documents/World of Warcraft/Wow-64.exe" -opengl

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

980 ti

Do you use the DirectX 11 engine? Currently DirectX 11 is limited use DirectX9 if you want more performance.

Sorry to sound silly, but how do I which I'm using and switch that?

Add -d3d9 after Wow.exe, set it in config.wtf or just change in Wow unter System -> Advanced.

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.

A couple of further information I forgot to mention:
- I tried to run the game without addons and it still freeze;
- I tried to re-install the game from scratch (totally empty Wine prefix) and it still freeze;
- I tried to run other games via Wine and they do NOT have the same issue.

I'm experiencing the exact same problems, completely out of the blue.

My System:
Wine 1.9.18 (but it also happens with 1.9.17)
NVIDIA Driver 370.23
Kernel: gentoo-sources-4.7.2
KDE 5.7.3 with Framework 5.25.0

I'm wondering if KDE is to blame here.. I will do some experiments.

So it's not the fault of KDE, the game also freezes when run under i3.

got the same issue, also I get a dc after loggin after the freeze.

The problem seems to disappear when the 32-bit client is being used.

However this crashes after a certain time cause of out of memory (3840x2160 everything at max, csmt wine-staging-git (wine-git + wine-staging-git).

I cannot confirm that, however I only play at 1920x1080, graphics detail set to 7.

In general, my experience is that WoW runs far worse with CSMT enabled.

For me it crashes when Wow reaches 2700MB-2900MB RAM.

Has anyone an oidea why this happens? I tried downgrading wine recreating my wine prefix but nothing changed.

So what was changed?

I remember that before the first crash on the 9th Battle.net downloaded something (very small as it was very quick) and did a "Reclaiming disk space".

Considering that, as I mentioned, the last update of Wine on my system was already few days old (and I did several hours of game play on it without problems) and there was no other system updates between the 8th and the 9th, my guess is that WoW itself is culprit; maybe the download was some sort of (undocumented or documented with little news about it) WoW engine update that messed up.

But it is just a guess since the above elements may be just circumstantial.

After turning of the new Live Streaming Feature in the battle.net app, the freezes also seem to go away, even with the 64bit client.

False alarm, still freezing.

A possible positive update on the matter.

Over the time I received the following updates:
WoW 7.0.3.22810
Wine 1.9.20 (Staging)
Kernel 4.4.21-gentoo
KDE 5.7.5 with Framework 5.26.0

And I tried to use the Blizzard repair tool again.

With all that, this morning I have been able to play for about 2.5 hours without any freeze.

Since the Blizzard repair tool have been a false positive solution when the problem emerged (I got a couple of hours of playtime after the first repair and then the freeze eventually returned), I will try to play again this evening before confirming that the problem has been solved (at least for me).

I am happy to report that this evening I have been able to play for about 4.5 hours and no crash.

I still don't know what caused the problem, but at least it has been fixed.

Unfortunately I have to report that since yesterday (October, 19th 2016) the problem returned and with all the quirks as before:
- the freeze happens randomly between either the first movement after login to several minutes of various activities (so no pattern on potential game activity that cause the freeze);
- I have tried to let it be for few minutes in case it was just a temporary lag spike, but nothing (permanent freeze);
- both KDE Task Manager and ps -A do NOT report the WoW process as zombie or similar non-running status (so for them the process is fine - and the fact I can alt-tab to these tools means that the whole system is running just fine);
- I have tried to run from the command line and also check dmesg and /var/log/messages and they report nothing unusual;
- I had NO Wine or system updates between the 18th and the 19th and I haven't modified either the Wine bottle nor the WoW configuration, so no chances of regression from the above programs;
- I have tried to reboot to avoid any conflict (i.e. potential bugs on either the kernel or the Nvidia drivers that surface only after a certain amount of uptime), but nothing;
- I have tried to run the Blizzard Repair tools several time: the first time downloaded ~980 Mb of data and later times nothing, and in all cases I still get the freeze;
- I tried to play (using Wine) both Lotro and Kotor 2 (and the later has an hack to force the engine to run on 1920x1080 so it should be more prone to problems than WoW whom support the resolution natively) for various hours and they do not hang.

Unfortunately I haven't paid attention if there was any WoW hotfixes lately (that may have introduced back the issue), but I noticed that the Blizzard Launcher often download something of ~ 190 bytes every time I launch it.

Later on, before leaving to work, I will try to reboot to do a full disk scan just in case the HD is dying (improbable since any tools that can check the HD on runtime report no problem and the rest of the system, including other games under Wine, have no issue).

While I remain deeply grateful to the Wine team for giving us and keep improving Wine, this issue is becoming frustrating; the Legion expansion is still fresh enough that I still have a lot to do and it occupies most of my free time and since I have to use Windows to play the game reliably, I often end up using it also for anything else I do in my free time (and since I love Linux, I don't want to return with the tail between my legs to be a full time Windows user ;-) ).

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.

I had same error #132 in Wine 1.9.17-staging and in Windows 10 when clicked at Enter World button in World of Warcraft client. European Blizzard servers were DDOSed at Sept 1 so it could be reason. I'll try it today and let you know!

This was finally resolved by a full delete / reinstall of World of Warcraft, excluding the still-working battle.net.

The installer/patcher had been running a routine I'd not seen before, "reclaiming disk space" or something like that, so perhaps that doesn't play well with linux.

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!

5 posts below yours on this same page somebody had the same problem. Reading is not that hard ...

That warning by Blizzard tells you nothing because it is coined for MS Windows. On your system something else fails. Check file and directory permissions (which should be right if the game worked until now). Check whether another update is in progress. Try to start WoW using the exe file. Restarting the battle.net app might help.

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!

Did a bit more research and, after screwing around with xorg, wine, and other settings to no avail, I tried disabling repeat keys under system settings > keyboard. Viola! it solves my problem (for the most part). If I happen to hit a severe drop in frames (more than ~10 or so). There still is a slight input lag but its not like it leads me to loosing aggro/ dying as tank so I'm happy with the solution.
Now if someone can fix the choppy-ness of the game through wine......

I came to post the exact same error.

Fresh 16.04 install and the keyboard delay in most heavy populated areas is painful!

Thanks for this. I'll test tonight and report back.

be happy, my opengl just opens up a black screen (sound and game workes well because i know where the buttons are)

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

Try the instruction on the Battle.net DB Entry:
appdb.winehq.org/objectManager.php?sClass=version&iId=28855

BIG THX it works now

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

And in a followup - launching WoW directly from WoW.exe works, but while in game if I alt tab into another window, say, Firefox for example, it will not register and input. It acts as if WoW is still my main screen. Trying to test out some things but if anyone has encountered this any information would be great, thanks!

From John López:

Upon clicking it gives me the error "We tried to make a file writable but failed. Please login as administrator and try again."


This messages normally occurs when the program to update is running.
When I run WoW or D3, after click Play games launch. During the game, in the button I can read Update. If I click, your message is shown.
Always, after the exit of WoW or D3 I need to click Update button. Really does nothing but is necessary if I want to play in other moment.

To solve this: Give WOW it's own workspace. Put all other apps on another workspace. Look up the default keys for "Next workspace" in your distro - if they don't work nicely with WoW define your own (I use ). By default you have 4 workspaces so alt-tabbing should be a thing of your MS past.

Sorry it seems I can't get my key combination to show up: it's ALT and the caret ^

That warning by Blizzard is coined for MS Windows. On your system something else fails. Your wineprefix/WoW folders should belong to you (the user) and not to root.
Generally I only run the BattleNet app when updating - all other times I start the exe.

Hello,

I installed two libs: libwinpr-winhttp01 and
libwinpr-winsock.dll


via the debian packet manager. ,


this solved the problem with the update.


Best Regards
Stefan

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:

I was able to get it to work by adding the msvcp140.dll.

And I was able to remove all of the other DLL overrides too.

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.

I have experienced this too, once every hour or so. If it happens, it's quite a long freeze, very annoying if you are tanking :-/

I'm also getting those, but they happen in other games as well, wine or otherwise. In WoW they're mostly random - can't find a specific trigger for all of them, but I did find a trigger in the new dalaran transmog menu. I stay there too long and it chain freezes for 10 seconds, then recovers, then almost immediately freezes again, etc. until I close the menu.

/var/log/messages shows

Aug 29 19:30:08 anathema kernel: NVRM: Xid (PCI:0000:02:00): 8, Channel 00000018
Aug 29 19:30:10 anathema kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

Xid 8 meaning "GPU stopped processing" according to Nvidia docs, really unhelpful. Might just be a faulty card.

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.

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.

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

Install VCRuntime2015 using winetricks. This is a known issue and that is the workaround for it.

Also ensure that you are running either 1.9.15 STABLE or 1.9.16. the wine-staging branch has a known unresolvable issue with the -staging branch of wine 1.9.15.

bugs.winehq.org/show_bug.cgi?id=41054

Apparently due to a problem in DLL load order.

A lot of thanks for this information. :))

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.

If you use Playonlinux, you can start WoW64.exe with Wine-staging and whenever you need to use the Launcher for updates you just reconfigure POL to use plain wine. That's what I do.

I'm glad I checked this before I tried to boot up the game tonight, because I hadn't considered how I'd handle patching just yet, and lo and behold there's a game patch today. I had completely forgotten about PoL's ability to hotswap wine versions! excellent solution.

No solution without the use of PoL? (I never used and no plans to do)

I guess you could do it by managing two separate wine prefixes and bounce back and forth between two versions of wine manually, but PoL would be the easiest method by a very long shot.

I can't do this.

I'm using openSUSE Leap 42.1 and if I check wine-staging, dependencies uncheck wine and viceversa. Only one version I can have.

Deinstall staging, install wine and reinstall afterwards? Just don't purge.

Probably not very comfortable ... This is exactly the reason why nice people took the effort to develop POL. But you are never going to use it, so you are stuck.

Using Ubuntu and the wine ppa allows me to install both wine and wine staging. The binaries are in separate directories. I use the normal for battle.net and staging for Wow. Works great after following the guide on the AppDB Battle.net page.

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.

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.

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

When you use overrides are you setting them to all to native with winecfg?

Did you have to install vc2015?

I set them as native,builtin. No, I have not installed any extra packages.

With these dll overrides [native,builtin] in wine staging 1.9.15 on openSUSE Leap 42.1:

wine World\ of\ Warcraft\ Launcher.exe
fixme:winediag:start_process Wine Staging 1.9.15 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:ver:GetCurrentPackageId (0x33e464 (nil)): stub
fixme:wininet:InternetSetOptionW Option 77 STUB
err:wininet:open_http_connection create_netconn failed: 12029
fixme:wininet:InternetSetOptionW Option 77 STUB
err:wininet:open_http_connection create_netconn failed: 12029
fixme:ver:GetCurrentPackageId (0x49be9e8 (nil)): stub
fixme:ver:GetCurrentPackageId (0x33e89c (nil)): stub
fixme:wininet:InternetSetOptionW Option 77 STUB
err:wininet:open_http_connection create_netconn failed: 12029
fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll"
fixme:winediag:wined3d_dll_init Experimental wined3d CSMT feature is currently enabled.
fixme:wininet:InternetSetOptionW Option 77 STUB
err:wininet:open_http_connection create_netconn failed: 12029
Object moved
Object moved to here.

fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll"
fixme:winediag:wined3d_dll_init Experimental wined3d CSMT feature is currently enabled.
fixme:wbemprox:wbem_locator_ConnectServer unsupported flags
fixme:wbemprox:client_security_SetBlanket 0x7dd447c0, 0x166f68, 10, 0, (null), 3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7dd447c0
fixme:wininet:InternetSetOptionW Option 77 STUB
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
fixme:wbemprox:enum_class_object_Next timeout not supported
Object moved
Object moved to here.

fixme:ver:GetCurrentPackageId (0x456e9e8 (nil)): stub
fixme:ver:GetCurrentPackageId (0x33e464 (nil)): stub
fixme:module:load_dll Loader redirect from L"wined3d.dll" to L"wined3d-csmt.dll"
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)
Object moved
Object moved to here.

krovikan@linux:~/.wine/drive_c/Program Files (x86)/World of Warcraft> err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in thread 005e, blocked by 0000, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in thread 005e, blocked by 0000, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in thread 005e, blocked by 0000, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x10321d8 "?" wait timed out in thread 005e, blocked by 0000, retrying (60 sec)
etc

Solved. With winetricks wininet and change to normal 1.9.15 is solved.

I used all the dll's you listed as well as vcrun2015 and I was able to launch battle.net with no problem. Thanks! I'm running wine version 1.9.15.

ubuntu Ubuntu 16.04.1 LTS
tried this fix on both a 32 bit wineprefix and 64 bit prefix and battle.net launcher still fails

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.

Uh... meant to post this at the bnet app page. /sigh

Oh well, WoW won't start either, so it could have been worse. My apologies! :o

To launch the battle.net client it now needs vcrun2015 in the prefix.

You can install it with winetricks.

Hi,
i use the latest version of Wine.
To solve it install vcrun2013 and wininet with winetricks tool.

I'm guessing I need to install from source and to be honest I suck at that.

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?

I'm having the same problem.

I used winetricks to install vcrun2015 and it seems to be ok now. I still have occasional connection issues but I am able to get back on for now. I will keep this updated.

Exact same error here. I'm currently running wine 1.9.14 since 1.9.15 doesn't appears to be stable yet, also it is not in the official arch repos. Maybe updating it to 1.9.15 should do the job?

Just did what Colin suggested above, great idea:

"I used winetricks to install vcrun2015 and it seems to be ok now. I still have occasional connection issues but I am able to get back on for now. I will keep this updated."

Where did you find the vcrun2015 dll? I just installed winetricks and I the highest I have is vcrun2015. The winetricks version I have is 20140817.