World of Warcraft

Thanks for your post.
coolmaps.io : position the path correctly!

I', newbie, please help how can fix it!

On a new Arch install, I was unable to connect to Battle.net. After switching to the staging version of wine, that was solved. However, now that it connects, it doesn't render. There are large gaps in the color, and some things don't show up at all. It is completley unplayable right now.

I am using nvidia, if that matters. I am also using the proprietary drivers. Anyone else having issues like this?

Yep, the same problem. Also unable to use fullscreen mode.

The word on the street is that the opengl backend (which you might be using) was rewritten as a side-project of one of the devs. It's unsupported, and it seems to be responsible for the tearing.

I switched over to direct x 9, and things work okay: no horrendous flickering. Performance is a little slow.

Initially, I was unable to manually select DirectX 9 (System->Advanced tab). I also was unable to set it by changing WTF/Config.wtf. I'd edit it, and every time I ran the wow launcher it'd revert to opengl.

It turns out that my wow launcher settings were the culprit. There's a setting in the wow launcher for extra command line flags for specific games (e.g. WoW). Apparently I had added -opengl a long time ago and forgot about it. Thus the launcher kept overwriting my settings when I tried to change to D3D9. Doh! Hopefully this helps someone with a similar problem.

Anyway, with WoW in DirectX 9 mode, the flickering is gone, and fullscreen mode works. Things aren't super fast, but with the settings cranked down, it seems okay for now. The old opengl's performance might have been better, but it's gone. The new opengl might get fixed, so I plan to play around with it from time to time.

This is what happens every time I try to open battle.net.exe:

when I do: wine --version I get:

wine-1.8

but I feel like I have a newer one on here.

OS- Mint 17.3 Rosa, Cinnamon 64-bit


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:0033d574 EBP:0033d57c EFLAGS:00010246( R- -- I Z- -P- )
EAX:00000000 EBX:4a866770 ECX:35628a48 EDX:3563b8a0
ESI:0033d618 EDI:4a918960
Stack dump:
0x0033d574: 3322c000 0033d618 0033d5a8 10b48fc8
0x0033d584: 0033d618 3322c000 4a866770 35606d5c
0x0033d594: 00000001 4a8f6660 00000001 00000001
0x0033d5a4: 00000000 0033d7d0 10ab113c 0033d618
0x0033d5b4: 3322c000 4a866770 3322c000 00000000
0x0033d5c4: 00000001 4a8f6660 00000001 00000001
Backtrace:
=>0 0x10b489bb in libcef (+0xb489bb) (0x0033d57c)
1 0x10b48fc8 in libcef (+0xb48fc7) (0x0033d5a8)
2 0x10ab113c in libcef (+0xab113b) (0x0033d7d0)
3 0x10ab577c in libcef (+0xab577b) (0x0033d81c)
4 0x10b555a5 in libcef (+0xb555a4) (0x0033d924)
5 0x10b55ca2 in libcef (+0xb55ca1) (0x0033da48)
6 0x10aecb9e in libcef (+0xaecb9d) (0x0033e46c)
7 0x10aec945 in libcef (+0xaec944) (0x0033e5e4)
8 0x10aec59d in libcef (+0xaec59c) (0x0033e674)
9 0x10adcbfe in libcef (+0xadcbfd) (0x0033e708)
10 0x10adc045 in libcef (+0xadc044) (0x0033e72c)
11 0x10acc1b0 in libcef (+0xacc1af) (0x0033e744)
12 0x10adc3d9 in libcef (+0xadc3d8) (0x0033e798)
13 0x10adc90b in libcef (+0xadc90a) (0x0033e7cc)
14 0x10adcc0e in libcef (+0xadcc0d) (0x0033e860)
15 0x10adc045 in libcef (+0xadc044) (0x0033e884)
16 0x10acc1b0 in libcef (+0xacc1af) (0x0033e89c)
17 0x10adc3d9 in libcef (+0xadc3d8) (0x0033e8f0)
18 0x10adc90b in libcef (+0xadc90a) (0x0033e924)
19 0x10adcc0e in libcef (+0xadcc0d) (0x0033e9b8)
20 0x10adc045 in libcef (+0xadc044) (0x0033e9dc)

Using Debian 8, POL and wine-staging 1.13 with csmt patch I'm getting graphic glitches.
This did not happen with wine-staging 1.9.8 (where csmt was disabled, since 1.9.6) and before 1.9 (which I can't test anymore because of the libgnutls-problem). I know the csmt patch, enabled again with 1.9.10, has been completely redone.

Framerates are a lot better with csmt so I would like to use it.
Does anyone else see this?

What is the benefit to use wine stagging instead of the wine-dev i think CSMT has been dropped from CSMT is CSMT still worth it ?

from Wine stagging

It was dropped in between v. 1.9.6 and 1.9.9 and rewritten in the meantime.

Currently:
Fedora 22
wine 1.9.11
nvidia 358.16
Authenticator bolted to account

Wow-64.exe in DX9 mode.
All works except for sound (pulse -- tested from winecfg works)
attempts to modify sound settings in game lock the game - (don't have a log handy for that yet)

World of Warcraft Launcher:
wine set to Win7 -> starts up, with browser accellerations off it displays, login is accepted but a few seconds after the page displays all data:

fixme:ver:GetCurrentPackageId (0x215e9c8 (nil)): stub
fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455
fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455
fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455
fixme:dwrite:get_name_record_locale failed to get locale name for lcid=0x00000455
fixme:system:SystemParametersInfoW Unknown action: 116
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:advapi:UnregisterTraceGuids deadbeef: stub
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f278
fixme:heap:GetPhysicallyInstalledSystemMemory stub: 0x33f278
fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
fixme:ntdll:NtQuerySystemInformationEx Relationship filtering not implemented: 0x3
fixme:mpr:WNetGetUniversalNameW (L"Z:\\opt\\windows\\Games\\World of Warcraft\\Data\\data", 0x00000001, 0x67da4e4, 0x67da4e0): stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
< I see deadbeef in there .... is that bug filing time? >

wine set to winxp -> Launcher starts up and login is accepted and can launch the game.

____

so far in *all* cases backing out from the game hangs, and requires wineserver -k to shut down - there is no clear message logged in default -- haven't turned up the logging.

New PC build, CPU i5-6600, GTX 1070, 16g ddr4.New to FreeBSD, Presently studying the OS and plan to complete the build by late August launch of Legion. Had Battle.net and WOW installed with Wine 1.8 but it would fail to launch. I'm on a older test machine running PC-BSD trying to get the bugs out before setting my 4k dream machine. Any help would be most helpful.

Hi,

As of the Battle.net update last night (7505), the WoW launcher has started to crash for me as soon as it tries to display the clickable "content panels" on the "Games" tab.

I have discovered that it stops crashing if I configure Wine to emulate Windows XP rather than Windows Vista, 7, 8.x or 10.

I have also noticed that the "Log in to Battle.net" button on the login dialogue box is not rendered at all for Windows >= 7 if the "Use browser hardware acceleration where available" option is enabled.

Is anyone else seeing this please? Is there a better workaround than configuring Wine to be WindowsXP?

Cheers,
Chris

Hi,
Which version Wine and distr have you installed?
I am running Debian jessie 64bit multiarch on 2 systems. My desktop, AMD FX8320 2x HD7870 in Crossfire (doesn't work in wine) has wine-staging 1.19.12 installed from winehq and the winetricks package from Debian stretch. If wine-staging is correctly installed you don't have to mess around with wineprefixes, unless you are using more than one.
Winecfg is set to windows 2008 (win 7 doesn't show the banners in the Battlenet launcher, game runs though) only installed vcrun2013 with winetricks no further overrides. Wow 64 bits runs great in OpenGL or D3D9. I also play Diablo 3 and EVEOnline (with the new evelauncher for linux) all run excellent.

Just for fun I downgraded my notebook, Lenovo y50-70, to wine 1.8.2 from the jessie backports to test if the issues with gnutls ahd been resolved. Battle net starts up and shows but when I try to play wow it still just hangs in connecting.

Cheers

Anyone was able to workaround the BLZ51900007 error and got WoW 6.2.4 working using the stable 1.8 Wine (with patched GnuTLS)? I don't want to use the dev/staging Wine version.

See my reply to Chris Rankin abt "WoW Launcher now crashes unless for WindowsXP"

Wine-staging 1.19.12 from WineHQ works fine. If there are regressions to try to resolve it asap.

Unless you have a compelling reason to stay at Wine 1.8 I suggest to update to Wine-staging.

Cheers

it is the only thing that works for me. I have both a US and EU region accounts.
I was running wine-1.9.14 very nicely, when...
I upgraded my Slackware64-14.1(Alien Multilib) to 14.2 and all hell broke loose. First I got the BLZ51900007 error, so I reverted to wine-1.8-alien_x86_64
and it works.
the US prepatch broke something and I am currently doing a 37Gb download.. :(

If anyone has any idea please help me. I've tried everything. I have a fresh install of wine 1.9.6, I tried running wow with my usual script which is "MESA_GL_VERSION_OVERRIDE=3.3COMPAT
export MESA_GL_VERSION_OVERRIDE
WINEDEBUG=-all __GL_THREADED_OPTIMIZATIONS=1 wine "/home/*/.PlayOnLinux/wineprefix/WorldOfWarcraft/drive_c/Program Files/World of Warcraft/WoW.exe" -opengl", I've tried without the script setting config.wtf to opengl, and it always says I need directx installed. I can't even launch battle.net because it says: "Failed to create graphics content." (Error Code: BLZBNTBNA0000000A) I really don't think it's a driver problem because I can play the game in POL (with really poor performance). POL uses the same version of wine that I have installed. So I just don't get this.

It looks like your GLX isn't working.
try running glxinfo from terminal.
If it says that GLX extension is missing, you have to fix your graphics driver installation. In my case, it was secure boot which prevented proprietary nvidia drivers from loading.

Installing and using Wine 1.9.7 fixed it for me. Running Linux Mint 17.3 64bit 3.19-33 kernel

Can anyone testing windows version of Legion confirm update of opengl backend and possibly new effects matching directx?

I just started the beta test today. I'll get your data very shortly.

Well, on Ubuntu 16.04 using the binary driver supplied by Ubuntu the 3D screens are fine BUT all 2D objects and text are upside down and backwards. This is using the OpenGL switch on the executable. The D3D switch works fine. There are a lot more supported options in the System > Video settings now.

It seems Leigon is borked under Wine-staging 1.9.9 and nVidia's Drivers (358.16) right now. I just did a fresh install of Fedora 23 for testing. OpenGL gets to the Character Selection screen with the above mentioned errors. D3D9 doesn't get to the character loading screen but looks correct.

Thx for checking! Good to know blizzard didn't remove opengl backend from windows version.

As of this morning OpenGL rendering seems to be disabled or gone completely. The -opengl switch does nothing and changing the API in the config.wtf to "OpenGL" also does nothing.

On a side note Legion seems to be running under wine-staging 1.9.9 now, I had to switch it to fullscreen (windowed) to get it not to crash. Normal windowed works too.

Wonder whats up with opengl.

Strangely this after noon OpenGL seems to be back, but still not working properly. It has the same graphical rendering glitches as before. Direct3D 9 is still working for playing under wine/Linux. Performance isn't that bad, considering.

There was a 3GB patch when I woke up this morning. I didn't notice a changlog posted. And it didn't seem to do anything for the OpenGL rendeder. 2D elements are sitll upside down.

So... having similar issues. Switching to D3D 9 (and setting winecfg to Windows 10) seemed to do the trick.

It seems OpenGL support is almost working. With the -opengl switch everything is now rendered properly but it will not connect to the server. When looking over the Graphics and Advanced options in the System menu it looks like all the same visual options are available as the Direct3D renderer.

The OpenGL renderer now seems to be working as of Legion build 7.0.3.21911 with wine-staging version 1.9.10. There is some graphical corruption every now and again, but it works.

Thank you for constant updates :) What's the difference in fps between opengl and directx?

Honestly I haven't tested the difference between the two renderers yet. I'll do it a little later today. I did make a video of showing the options in the System > Graphics and System > Advanced menus. All of the options are enabled except MSAA related ones. MSSA requires a shader model 5 graphics card, I guess wine doesn't support shader model 5 yet. That or the version of OpenGL WoW is using doesn't. Anyway, here is the link to the video I made if anyone is interested. www.youtube.com/watch?v=0MR586mY798

It seems as of today (07.02.2016) both the PTR and Legion: Beta will not go into the character screen from the server connect screen. Sometimes either one will crash when you hit play from the launcher. This is with -d3d or -opengl switches. It happens also with the 32bit or 64bit clients. I'm not sure what went down over the past couple of patches.

I can confirm the game crash. It seems to have other causes, possibly with network encryption issues given the log messages I saw. I suspect this will get fixed at some point.

New patch dropped over the last couple of days.
> D3D-9 : Works properly now.
> OpenGL : Didn't test.
> D3D-11 : Unplayable graphical glitches. Thankfully, the UI stuff works so you can easily switch to D3D-9 mode and restart the client.

Hello,
i followed the way by Alberto i installed gnutles, deinstalled
wine, installed wine again and now i cannot start wow. If i start with Battle.net the Play Button is always grey. I dont know what i should do.
Sorry for my bad english.
Best greetings from Austria.

I use Linux Mint and a big thanks to all

Ok Now I installed Wine not right. Now im able to start wow but its the same. I cant connect to wow server

My steps work well in openSUSE Leap 42.1.

Others I don't know.

In this thread:

us.battle.net/wow/en/forum/topic/20742995286

starting at page 11 begin to appear solutions for Mint, Debian, Ubuntu. In OP there are solutions for Ubuntu, Debian and Gentoo.


Good luck

I also use Linux Mint, 13.2 64bit, and got it working.

I use the wine-builds ppa, and used patched secur32.dll.so files from here: us.battle.net/wow/en/forum/topic/20742995286?page=16#312

The patched files were compiled against wine-devel, not wine-staging, and I could not get them to work with wine-staging.

So I removed wine-staging, installed wine-devel, and replaced the files with the patched ones as described on that forum post. It now works for me.

Hopefully that helps you.

Hello, thanks for your answers
this evening i will try to copi the secure32.dll.so file
But one question,
If i download the File from Dropbox the file is called secure32.dll.so.32 or secure32.dll.so.64.

Should i delete the File without 32/64 at the end and add the new file with 32/64 at the end of File?

Or should i rename the file and delete 32/64 at the end of file?

THanks

In Opensuse (verify your Mint) the structure is:

In /usr/lib/wine this is the file secure32.dll.so

In /usr/lib64/wine this is the file secure32.dll.so

The first is the file for 32bits and the second the file for 64bits.

Maybe you must rename secure32.dll.so.32 to secure32.dll.so and put in the directory for 32bit and the same for the file 64 bit.


Regards

Thanks to all it runs i only copied the files in my Lib deleted 32/64 at the end and it runs wonderfull.

Thanks to all

I installed 1.9.6 via apt from winehq. When I fire up winecfg and test sound, it works fine.

If I fire up Wow (wine64 Wow64.exe) it WOW opens in a small (tiny) window. I double-click on it and it opens full screen and I can play, but no sound at all. I checked the sound and volume settings in WOW.

If I start via battle.net app, I have sound, but I can't switch to another desktop, etc. because WOW captures the mouse. If I alt-tab I can move to another screen, but it locks up wow

disable d3d11

Didn't help. Actually, it's worse. When I disabled the library and start Wow via wine64 Wow64.exe the cursor is stuck in WoW, and I can't move to a different monitor/desktop.

Before the last patch (6.2.4) I've had no problems whatsoever with running the game.
I didn't have a lot of time last week so I only tried playing once, but it was stuck at connecting, I figured it's something with the servers and went to do something else instead. I tried playing again yesterday, and the game itself started, I just couldn't log in, it gave out Error Code BLZ51900007. I googled it and figured I had to update wine so I did a fresh install of 1.9.6.
Now my game doesn't even start, it says "World of Warcraft requires the latest version of DirectX Runtime to be installed".
For some people upgrading distribution seemed to work so I upgraded to Ubuntu 15.10. It's still not working. I managed to get it to work in PlayOnLinux, but it's unplayable, I get terrible fps and something's off with the graphics (action bar glitches out all the time).
I was thinking maybe it's something with my drivers so I updated with the Intel Graphics tool.
Does anyone have any idea about this?

I recommend to you to read de OP of this thread:

us.battle.net/wow/en/forum/topic/20742995286

Especially the section Issue #2 Update Method for Ubuntu

I've tried almost everything written in that thread. Now the problem seems to be DirectX for some reason. I wish I had that connecting issue again since there's a solution to that now.

Don't use DirectX 11

I have a completely clean wine install. Not only that, but I can run the game in PlayOnLinux (with the same wine 1.9.6 version), the fps is just really low.

If you are on OpenSUSE Leap 42.1, just follow these steps (thanks to Alberto):

Install libnettle-devel and gmp-devel

wget ftp.gnutls.org/gcrypt/gnutls/v3.3/gnutls-3.3.15.tar.xz

unxz gnutls-3.3.15.tar.xz && tar -xvf gnutls-3.3.15.tar

cd gnutls-3.3.15

./configure && make

sudo make install

Now, uninstall wine in your packagemanager
Then go back, and install wine again.
Installing wine makes it see your new gnutls files.

Now everything should work. I can confirm on 3 installations.

Make sure you at ftp: / / before the download address for gnutls

Works for me

/cheers

OpenSUSE Leap 42.1 (64)
Using authenticator

Hello:

I follow the steps from the review of Thelostman from 25 March.

wget ftp.gnutls.org/gcrypt/gnutls/v3.3/gnutls-3.3.15.tar.xz

sudo apt-get install build-essential nettle-dev libgmp-dev

unxz gnutls-3.3.15.tar.xz && tar -xvf gnutls-3.3.15.tar

cd gnutls-3.3.15

./configure && make

sudo make install

All OK until here.

Problem is now:

sudo unlink /usr/lib/x86_64-linux-gnu/libgnutls.so.26
sudo ln -s /usr/local/lib/libgnutls.so.28 /usr/lib/x86_64-linux-gnu/libgnutls.so.26

sudo unlink /usr/lib/x86_64-linux-gnu/libgnutls.so.28
sudo ln -s /usr/local/lib/libgnutls.so.28 /usr/lib/x86_64-linux-gnu/libgnutls.so.28

sudo unlink /usr/lib/i386-linux-gnu/libgnutls.so.26
sudo ln -s /usr/local/lib/libgnutls.so.28 /usr/lib/i386-linux-gnu/libgnutls.so.26

¿What is the correct replacements to the links and unlinks?

I have /usr/lib/libgnutls.so.28.30.6 and simbolic link /usr/lib/libgnutls.so.28 pointing to /usr/lib/libgnutls.so.28.30.6

I have /usr/lib64/libgnutls.so.28.30.6 and simbolic link /usr/lib64/libgnutls.so.28 pointing to /usr/lib64/libgnutls.so.28.30.6

I have /usr/local/lib empty.

I have /usr/local/lib64/libgnutls.so.28.41.7 and 2 simbolics links: /usr/local/lib64/libgnutls.so and /usr/local/lib64/libgnutls.so.28. Two simbolic links point to /usr/local/lib64/libgnutls.so.28.41.7

Sorry for the comment above.

I switched to winesnapshot and with build 1.9.6.20160325.1435-1.1, WoW works again with openSUSE Leap 42.1.


Regards

Hi Alberto,

Did you do anything else? You were rebuilding gnutls in your previous post. Did you clean this up or are those files actually in your installation now?

I also run Leap and I downloaded the same Wine snapshot as you did. I still get the forever connecting.

As far as my research goes, we need gnutls 3.3 or higher for this to work. Leap comes with gnutls 3.2

Could you give more info about your system?

Thanks in advance :)

Hello:

My only steps were:

1 - Download and ./configure && make and with sudo, make install as above. Nothing else, only until my line "All OK until here". The rest of comment it's for forget.

Now I have 2 gnutls: 3.2.15 with Leap (libgnutls.so.28.30.6 at /usr/lib and /usr/lib64) and gnutls compiled (libgnutls.so.28.41.7 at /usr/local/lib64)

2 - After testing diferents secur32.dll.so (at /usr/lib64/wine) reworked (fixing the problem with SSL3 connections refused at Blizzard servers) from Ubuntu and Mint (I save original file), finally I left the original secur32.dll.so with Wine 1.9.6 because the other files switch the eternal connecting to BLZ51900007.

I change from wine 1.9.6 to wine-snapshot 1.9.6.20160325.1435-1.1 and works again.

I imagine that gnutls compiled help plus the fix from WINE team at this snapshot.

Good luck

If I understand you ok, you compiled gnutls in step 1.

In step 2 you actually did nothing? You tried several secur32.dll.so files but none worked so you restored the original file.

Then you went to the wine-snapshot.

I don't understand how this worked for you (but I am happy for you it did :) ). Basically wow needs to use those compiled gnutls files and that is the problem.

Correct.

Compile gnutls as in comment 1 without delete anything (you'll have all files of gnutls that I say before) and change to wine-snapshot.

Good luck and tell me if works for you.

Ok, what I did:

I compiled gnutls as you said, but I did it in a virtual machine.
Once I had the files I copied them to my WoW machine.

What I am not getting, how does wine know to grab those new files over the ones that come with Leap?

I don't used virtual machines to do this.

Wine that I have (and your name also in YAST) is wine-snapshot 1.9.6.20160325.1435-1.1. Remember tick to remove wine and wine-32bit.

Direct links if you need are:

download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.1/x86_64/wine-snapshot-1.9.6.20160325.1435-1.1.x86_64.rpm

and

download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.1/x86_64/wine-snapshot-32bit-1.9.6.20160325.1435-1.1.x86_64.rpm


Regards

Ok,

Then I will compile them on my WoW machine. One more question (and thank you so much for your help so far).

You said in a post that when you did make install the files were installed in /usr/local/lib64

When I did it the files were installed in /usr/local/lib

I tested the files with 'file' and they were all 64bit. They just didn't end up in lib64 but in lib instead.

Any idea on that?

My WINE Prefix and Leap (of course) are 64 bits (Prefix is 64bits if you have .wine/drive_c/windows/syswow64).

Don't need anything in /usr/local/lib. My directory is empty.

Make install only copy to /usr/local/lib64.


Regards

You are the hero of about 4 people today. Be proud, walk tall.

IT WORKS!!!

All you have to do is your first steps with compiling and installing GNUTLS

THEN: reinstall wine. Reinstalling it make it finding the new files.

THANKS!!

For those using Ubuntu 15.10 and can get it running through WINE but not PlayOnLinux, here's how to fix that:

PlayOnLinux has it's own libraries that it links against. For example, when I install WINE 1.9.6, it's got that version of WINE linked against libgnutls.so.26.22.4 rather than any libraries included with the system.

Fix it:
cd /home/$USER/.PlayOnLinux/wine/linux-x86/1.9.6/lib
mv libgnutls.so.26.22.4 libgnutls.so.26.22.4-ORIG
mv libgnutls.so.26 libgnutls.so.26-ORIG
ln -s /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 ./libgnutls.so.26.22.4
ln -s /usr/lib/i386-linux-gnu/libgnutls-deb0.so.28 ./libgnutls.so.26

Note that I'm running Ubuntu 15.10 x64 with WoW in a 32bit WINE Prefix in PlayOnLinux. If you were running some other combination, like WoW in a 64bit WINE Prefix in PlayOnLinux or maybe just 32bit Ubuntu, those paths would change a little. I don't know exactly what they would be off the top of my head but maybe others can chime in, if they know. I can guess... but it just may make the post confusing.

This is for the "Stuck at Connecting..." problem with patch 6.2.4 BTW.

Hi! This solution works on:

* Debian Stretch (actual testing)
* Wine 1.9.6

And WINE Prefix x86_64.. commands executed:

cd /home/$USER/.PlayOnLinux/wine/linux-amd64/1.9.6/lib
mv libgnutls.so.26.22.4 libgnutls.so.26.22.4-ORIG
mv libgnutls.so.26 libgnutls.so.26-ORIG
ln -s /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28 ./libgnutls.so.26.22.4
ln -s /usr/lib/x86_64-linux-gnu/libgnutls-deb0.so.28 ./libgnutls.so.26

Thanks buddy!

Many thanks to anyone who added information how to compile libraries. Also to Chris and Rafael for perfect solution with replacing just PoL libraries.

I can confirm WoW again running on Xubuntu 14.04 x64.

Thanks for this info, did just the job! A note to others: don't try and be clever like me and try and overwrite any other library files, especially the file libgnutls.so, otherwise this fix won't work.

Don't just copy this without thinking. On my uptodate stretch gnutils had the version number 30. Took me several days to figure that out. Check the link.

Since it seems that I can't edit my previous comment: gnutls v. 28 as given above is for debian jessie - so without further updating the problem can be fixed on jessie! - and v. 30 is for stretch but here the number might change with every update.

The problem is in gnutls, which provides SSLv3 handshake by default. This "feature" removed in newest versions of gnutls, so if you have possibility to update your package, just do it. If you can't do this, download new libraries (for example, for Ubuntu 14.04 you can get packages for Ubuntu 16.04 and extract libgnutls.so.30, libnettle.so.6 and libhogweed.so.4) and run WoW with this libraries using LD_PRELOAD.

Thanks for this solution to Товера from russian WoW forums: eu.battle.net/wow/ru/forum/topic/17611002208?page=1#3

#I tried LD_PRELOAD with the chosen libraries and even trying to run 32-bit,
# it fails (it runs but still stuck at "Connecting").
#Although running 32-bit gives me ELFCLASS32 wrong class error messages..
# even when trying to run `wine Wow.exe -noautolaunch64bit' with 32-bit
# libraries.
sudo apt-get update
sudo apt-get install atool
cd ~/Downloads
wget mirrors.kernel.org/ubuntu/pool/main/g/gnutls28/libgnutls30_3.4.10-4ubuntu1_amd64.deb
wget mirrors.kernel.org/ubuntu/pool/main/n/nettle/libnettle6_3.2-1_amd64.deb
wget mirrors.kernel.org/ubuntu/pool/main/n/nettle/libhogweed4_3.2-1_amd64.deb
for i in *.deb ; do aunpack $i ; done
cd ~
LD_PRELOAD=`find Downloads -type f -iname "*.so*" | grep amd64 | perl -pe "BEGIN{$/=''}{s#Downloads#/home/mint/Downloads#g;s/\n/ /g}"` wine64 '.wine/drive_c/Program Files (x86)/World of Warcraft/Wow-64.exe' -d3d9
#LD_PRELOAD = /home/mint/Downloads/libnettle6_3.2-1_amd64/usr/lib/x86_64-linux-gnu/libnettle.so.6.2 /home/mint/Downloads/libhogweed4_3.2-1_amd64/usr/lib/x86_64-linux-gnu/libhogweed.so.4.2 /home/mint/Downloads/libgnutls30_3.4.10-4ubuntu1_amd64/usr/lib/x86_64-linux-gnu/libgnutls.so.30.6.2
#still stuck at "Connecting"
#using Linux Mint 17.3 with wine-1.7.50

above, i meant to respond to this

the wine-development package currently in debian sid (1.9.6-1)

@Kari Hazzard can you post your configuration please. I'm not sure why you've posted Gold status for this patch when so many of us are still having the exact same issue that was posted a few days ago: us.battle.net/wow/en/forum/topic/20742855183?page=14

I used the Gold rating because the definition of Gold is "Application works flawlessly with some DLL overrides, other settings or third party software."

This is the current state of the game in Wine when installed on a fresh Ubuntu 15.10 partition and running in Wine 1.9.6. I didn't spend much time testing it without DLL overrides, but it seemed to work out of the box, may even qualify for Platinum.

It is believed at the moment that the issue you are having is something specific to your installation and, while nearly ubiquitous, is not inherently a wine issue. On older installations which are not not using the most up-to-date libraries, one of wine's runtime dependencies (currently suspected to be gnutls) is causing the client (via wine) to incorrectly establish its cryptographic connection to the server. Due to the error, the server then drops the connection.

In non-technical terms, on your computer specifically (and those of a lot of other people with older libraries), your computer is giving the wrong secret handshake and consequently the server is slamming the door on you.

The exact method to fix this is still being worked on, but several people have been able to evade the issue by doing a clean install or a total system update to the latest version of everything in Ubuntu 15.10.

Please check the main thread on the issue as it's where a lot of these developments are occurring: us.battle.net/wow/en/forum/topic/20742995286

Confirmed, updating gnutls just fixed it for me.

What are you build, version, wine, guts are you usIng? Some report upgrading certain wine / kernel / build workers and for others it doesn't.

OK, firstly, my apologies. Perhaps I wasn't clear enough with my words. What I was after was HOW you got the game running (not "what is Gold status?").

Secondly, thank you, thank you, thank you, for providing that information. It has been extremely helpful. I can confirm that I now have World of Warcraft 6.2.4 running through Wine 1.9.6 on Ubuntu 15.10.


Points of Note:
My system was already up to date with all the latest Ubuntu updates/upgrades before the latest World of Warcraft patch was rolled out. I've not made any specific changes to the OS to get this issue sorted.

Following the instructions posted from your link (thank you again), I found that the first three packages to be purged were not installed on my system anyway (I've been using Play on Linux). The fourth package(winetricks), however, WAS found AND purged(and has not since been re-installed).

Following those instructions further, I've added the repo's and installed wine (as a stand alone package, not part of Play on Linux).

After copying a reasonably clean (read: minor changes to config.wtf for OpenGL along with some gfx settings) install of the game to the 'Program Files (x86)' directory (inside '~/.wine/drive_c'), I'm now able to run World of Warcraft without the 'Connecting' problem by executing 'wine Wow.exe' via the command line from within the World of Warcraft directory (still no dice from Play on Linux).


System specs:
Ubuntu 15.10 (x64): definitely not a 'clean' or 'new' install, but updated regularly.
Wine 1.9.6: I assume 64 bit due to the existence of a 'Program Files (x86)' directory.
World of Warcraft 6.2.4: fresh download with some small system specific changes to config.wtf (for my older onboard gfx).


Conclusion:
Installing wine 'fresh' would, I'm sure, sort the possible 'gnutls' problem. However, as previously noted, part of the process I've followed also removed winetricks from my system. I don't know enough about this to draw any conclusions from that, but, suffice to say, since the game is working again I'm not about to go and try to break it by installing things it's currently running perfectly fine without.

I hope everyone else experiencing the 'Connecting' issue finds your information here and enjoys the same success.

And thank you to Blizzard for not completely ignoring, what is for them, an unsupported platform. Some of those GM's have been quite helpful.

Please, open ticket bug reporting the problem and the solution (with links and atachments). Maybe devs puts into a new wine version.

For a lot a people that no have experience in compile programs (and less in big programs with a lot of dependecies) only can wait a packet for distribution.

Is my case with openSUSE Leap 42.1


Regards

Previous configuration:

Xubuntu 14.04 LTS
3.13.0-83 kernel
1.9.4 + 1.9.6 wine
problem: hang on "Connecting"

I tested running via PlayOnLinux and separately via wine, nothing helped. Then I upgraded kernel but no help.

Upgraded configuration:

Xubuntu 14.04 LTS
4.4.0-13 kernel
1.9.4 + 1.9.6 wine
problem: still same

Again tested with and without PoL on different versions and had no luck. Still hang on "Connecting".

Do you use battlenet key ?

Did you tried to deleted the /home/$USER/.wine/drive_c/users/$USER/Application Data/Battle.net/ directory while testing the new kernel?

There was a blue post in a french forum, saying this is not against linux.

ups, sry, i missed the correct thread ...

This thread eu.battle.net/wow/fr/forum/topic/17610932102 ?

- my france is even worse than my english, but thats how I did read it.

I'm french and I can say that's a good reading.

When I try to log in it hangs at "Connecting" after patch 6.2.4 today. Using wine 1.9.3 on Ubuntu 14.04, other Battle.net games work but not Wow.

Same here and only as of last nights patch (6.2.4). Running Ubuntu 15.10 and tried Wine 1.9.3 as well as 1.9.6. The Battle.net app seems to run perfectly, but when launching World of Warcraft, the game hangs at the main login screen with a window that says "Connecting". I believe this is the point where the game is authenticating the account. Attempting to log in from the game's own login screen (as opposed to the Battle.net app) produces the same result. It doesn't even get so far as to ask for my authentication code. Others appear to be having the same issue: us.battle.net/wow/en/forum/topic/20742855183

I also have an issue with logging in (EU) after the patch. Wow tells me "You have been disconnected. (BLZ51900007)"

WoW 32-bit
Wine 1.7.29, also tried various other versions, like 1.8.1 and 1.9.3, but 1.7.29 was the one that worked yesterday.

Users getting the BLZ51900007 error should update to the latest version of Wine. There are (at least) two different problems with Patch 6.2.4; several users who were receiving this specific error message reported that updating wine fixed the issue in this thread: us.battle.net/wow/en/forum/topic/20742845120

If you continue getting BLZ51900007 after updating Wine, please post as much; if the error changes to the "connecting" issue, please state that as well.

Thanks, with wine 1.9.6 it now waits at "connecting".

We have a long (and growing) thread trying to identify the root cause of the hang on "connecting".

us.battle.net/wow/en/forum/topic/20742995286

A few people have been able to resolve the issue by diverse methods, but it hasn't been determined what the cause is specifically other than it's probably not a Wine issue. The current going hypothesis is that it's probably related to a library wine is linked against, but we're still actively trying to figure exactly which library it is or if there may be more than one thing causing the "connecting" hang.

Same problem here since WoW-patch 6.2.4
- Debian 8 - Jessie
- Wine-version: wine-1.9.2 (staging)

Confirmed, same debian, same wine version.
Could it be that blizzard is banning linux for some reason?

Same here.
Ubuntu 14.04
Wine 1.9.2

Same here.
Ubuntu 14.04 LTS
Wine 1.8.0
Failure started with WoW Version 6.2.4; game currently unusable.

Everything was working fine until the update yesterday. Now I can't login. It just hangs at "Connecting". It seems that at the point of failure in the login precess, my client sends login data (is all binary data) to "us.actual.battle.net:1119" and the server sends 3 packets back in response, an ACK, then a FIN/ACK, and lastly a RST/ACK, and theres no data in those packets from the server. At this point the client just hangs at "Connecting" and doesn't even seem to notice that the connection has been terminated.

Same Problem.

Ubuntu 14.04 / Wine 1.7.55.

tried different wine versions, different simple settings, no result :/

I started Wow from the shell and tried to resolve this err

"err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution."

My naive thought was, to install secur32 with Winetricks

But surprise:

"sha1sum mismatch! Rename /home/whitey/.cache/winetricks/secur32/Windows2000-KB959426-x86-ENU.EXE and try again."

Could it be that this has something to do with this bug?

Probably not. I have the same error when I run the program but can get in just fine.

I have Linux mint 17.3 and wine 1.9.4 and the same problem (Hangs at "Connecting"), but i have too the installed game in a laptop with Windows 7, and the game runs perfectly. So, the problem is wine.

Conecting...
openSUSE Leap 42.1, kernel 4.1.15-8-default, Wine 1.9.6-549.1 from download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.1/

From all Posts I've read, Wine could fix the problem, but in my humble opinion Wine is not the part of the puzzle that causes the trouble.

Some Ubuntu Users can play on Wine. The same Wine, as I got on my Mint 17 with Kernel 3.x - so again - the Problem is not Wine, even if a Wine patch might help.

My best guess is, the Issue must be in some librarys used to compile.
The Kernel isn't the solution. Some people installed a newer Kernel with wine staging, but get no connect.

agreed truly. check out this site www.worldworx.tv for more information

Hey All,

I am having a problem when Launching WoW from the Battle.net App.

1. I have to update every day & between every launch. For some reason it always thinks there is an update out there but there isn't. Not the huge problem.
2. I have a dual screen set up for my system. WoW only launches is one but I don't care about that. When I ever I decide to Alt-Tab to get at something in another window, the whole game just locks up. So while I can get at the other window, I now have to Kill the game and relaunch winch means going through an update again given the previous problem (1) Again not the largest Problem.
3. The Bigger problem and most relevant to this post. Since the update to gnome I had to install the latest invidia driver 361.28. Which then made me update mutter cause I couldn't see my mouse in some cases. Since then when I launch WoW I get this error that "World of Warcraft" Is not responding. You can wait a short while or quit. or something to that effect. This comes up just before the game windows launches. Before the window launches I can''t even respond to it. it floats above the game. To respond to it I need to Alt-Tab out of the game. Which gets me problem (2) and then Problem (1)

How can I get rid of this error. I don't care that Wow takes a second or two to load. I just want to play it.

Ubuntu 15.10, upgraded from 14.04
Wine 1.7.55 from PPA
WoW 6.2.3
Computer Intel Pentium (R) D CPU 3.00 GHzx2 Dual Core 64 bit, but listed as 32 bit for some reason
Graphics card GeForce GT630 (w/proprietary driver ver 304.131 from Nvidia 304 updates)

After update, battle.net was opening to white screen so in Wine, I changed the Windows version to Windows XP, as someone recommended, which fixed it immediately.

HOWEVER...
When I launch the game, the regular screen opens just fine and says Connecting like usual, but the game itself opens in a tiny 1/2" box in the upper left corner above the WoD logo. The cursor can only move in that tiny square. The big screen will say, "Connecting..." until I finally Restart.

I've looked all over online trying to find someone else with this issue to no avail. Any ideas on a fix? Thank you in advance for your brain power!

Try "Emulate a virtual desktop" in winecfg.

Hey,

i have the same problem but with wine 1.9.6 and 64 bit prefix for WoW.

Tried the virtual desktop but it did not help at all.


Thx in advance for any help

I have the same issue. upgraded to 1.9.6. Didn't have in on 1.7.*

I take that back -- kind of. I can fix it (in ubuntu) by doing the following

sudo apt-get install compizconfig-settings-manager

Run compizconfig-settings-manager

Go to the Workarounds plugin and enable Legacy Fullscreen Support

Which allows me to play in full-screen. It however will not let me switch to my second monitor (which emulate virtual desktop did). It I alt-tab, I can switch but I can't get back to WOW. It locks up, or doesn't accept any mouse/kbd input.

Just double click inside that tiny window and everything is fine again. At least that worked for me.

Yep, that works great. thanks

Here is the error I got after I was told the launcher needed an update and needs to restart.

This application failed to start because it could
not find or load the Qt platform plugin "windows".

Reinstalling the application may fix this problem.


Not sure why this happened...

In winecfg add battle.net.exe with windows version 2003 or WinXP, that should do the trick. I also don't use redirects.
Running Debian jessie with wine 1.9.1 with bumblebee/optirun.

I had this exact same problem on a fresh install of Fedora 23. I have not found a solution, and adding battle.net.exe to the application field didn't help. I also already had the windows version set to XP.

If your distro (I know fedora is one of them that does) has the staging release of WINE in it's repo, or comes with the normal release of 1.9.0, you need to use a version above or below 1.8-staging/1.9 to install the bnet app.
This is simple for fedora, open a terminal and do:
sudo dnf config-manager --add-repo repos.wine-staging.com/fedora/23/wine-staging.repo

sudo dnf install wine-staging

WINEPREFIX=~/.wineBnet /opt/wine-staging/bin/wine "/path/to/Bnet/Setup.exe"

After it is done installing, you may cut and paste the Battle.net folder in ~/.wineBnet/drive_c/Program Files into your normal wine prefix, or leave it there.
You may now use your normal repos wine to run the bnet app.

If you are not on fedora 23, you may use this site to assist you in adding the wine-staging repo.
*Note: the wine-staging repo will install to /opt/wine-staging on all distros, to avoid conflicts with your repo's wine. Anything you need to run through the newly installed wine-staging version needs to be done via /opt/wine-staging/bin/wine and NOT wine or /usr/bin/wine.
Also - wine-staging comes in a i686 format from their repo. As such it cannot run in a 64-bit wineprefix, hence why the above commands have it create a new prefix to install bnet in.

Technical explanation: wine 1.8-staging and 1.9 support proper file-attribute saving. When the Bnet launcher installs, it creates various temp files with "." infront of the name. When it moves these files to it's install location, even though it renames them to remove the "." the "hidden" tag in the file metadata remains, this confuses QT as it's not designed to use "hidden" files, and causes the QT Platform crash.

There is information about it on the Blizzard Forums too: eu.battle.net/wow/en/forum/topic/17288641908

However I get the same error he mentions so I am not sure how others have gotten it to work :-/

Found a Bug report that has a great solution. Run this in the Battle.net Dir: "setfattr -x user.DOSATTRIB ./Battle.net.6734/platforms/qwindows.dll"

Found the Information here: bugs.winehq.org/show_bug.cgi?id=39985

This fixed it for me. Many thanks!

Thank you. I was resigning to use unstaged wine. My old HD7770 is kinda enough again :D

Just use normal wine, staging gives this error since a couple of days... not sure why...

For those running older, Debian-based distros who want a newer version of Mesa, I generated the required package files for installing Mesa 11.2. I've posted them, along with a discussion of what I did to create them, here: mattspraggs.co.uk/blog/posts/upgrading-mesa-debian-stable-jessie.

I was able to get it working in windowed mode (you'll see why that is needed below).

My hardware: Clevo gaming laptop. Nvidia/Intel hybrid graphics (which may be complicating this all, so YMMV.)

I used the same Wine prefix I use for normal WoW, and made no changes to config, running Staging (1.8 RC-1)

When launched, game starts messing with screen resolution, eventually requiring me to kill Wine from a text console to get control of the X display back. I noticed that it never saves the WTF/Config.wtf file that is used for startup, so I created one with the line:
SET gxWindow "1"
in it (nothing else.) And started the game.

This time, I get a Blizzard bug window (selected 'close') followed by a WINE nonfatal assertion error (selcet OK.) Game... then starts (!) but is running in 1024x768 sized tiny window. Attempts to change the resolution crash the game, so quit the game and go back and edit the now correctly populated Config.WTF to insert:
SET gxResolution "1440x900"
(Or whatever you want your game window to be) and restart. Same drill with Blizzard bug and the Wine assertion, then... Game On.

If there is any testing folks want me to try and do, let me know, just know it does run fine.

Heck, I wish I could get the game to work with a flip on my desktop @ home. I tried ArchLinux (my preferred desktop and could never get it installed) I then tried OpenSuse Tumbleweed and could get it installed and running, but the framerate was like 18FPS max.

GeForce GTX 760 card. I used to play under linux for like 5 years back in the day: i.imgur.com/N8khZ.jpg (Multiboxing even lol)

If anyone is bored and wants to come chat about WoW under Linux, hop by my IRC channel on Freenode: #ExInferno I have a gaming community of about 100 active members a lot of us play WoW.

exinferno.com/ Hope to see some of you guys around! (Sick)

I'm using wine 1.7.51 to run WoW on Linux Mint Debian Edition. I find that after playing for around 10 to 20 minutes, the game starts to lag for a second or two every few seconds (around five seconds).

This only occurs on my laptop, which has an intel i915 graphics chipset. I'm running the stock LMDE 2 kernel: 3.16.0-4-amd64, and mesa 10.3.2. As a result I'm constrained to using directx as the engine.

In an ideal world I'd have a newer version of mesa, such that I can use OpenGL as the renderer and potentially get more consistent performance.

Part of the problem is that I'm not sure exactly what the cause of the problem is. I've read that this could be a CPU scheduling problem, but I've tried tinkering around with the scheduler options and haven't had much success. Furthermore I suspect that the advice on changing the processor scheduling is out of date. The other advice related to having an nVidia graphics card, which I of course don't have.

Does anyone have any ideas that I can try to get this working properly? I can play the game, but it's quite annoying to have it lag so frequently.

I had this happen on an older laptop I was using. It was caused by thermal protection throttling. Opened up the box, removed years worth of cat fur from the cooling blades and it was back to fine.

I gave this a whirl and it _seems_ to have done the trick. I played the game for a bit until the problems started happening, all the while following the system log. Sure enough, I saw quite a few thermal throttling events showing up in the logs, so I opened up the case and gave the fan/heatsink a good old blast with some compressed air.

My CPU thermometer is still up in the mid to high 80s (that's Celcius, around 180 to 190 Fahrenheit), but I don't get nearly as many thermal events, and the game doesn't lag anymore :-D

Thanks for the advice!

Xubuntu 15.04, intel i915 Mesa. wine-1.7.54 (with staging and without), x86 wineprefix.

Got this error i.imgur.com/m6kfjpd.jpg and output is pastebin.com/ATGp8MaK . But it runs with DirectX, even though very slow.

Does enyone know how to fix it?

Well, two things. First you need more up to date Wine and Mesa, that shit you got there is really old. Second, you have to tell WoW that you are using OpenGL 3.3, which is now required by OpenGL renderer:

MESA_GL_VERSION_OVERRIDE=3.3COMPAT
export MESA_GL_VERSION_OVERRIDE

ok, ok...loads of you are saying you got it to work under fedora, 22 even.

Whats the catch? Open ATI drivers are not it.They work = to or better than the closed ones, and waaaay better than anything debian can hand you.

Ive copied the files needed into the folder, Ive installed DX9 outright...all to the same failpoint....

"Please install DirectX." Keeps popping up.The game refuses to launch even the title screen. I could tweak it if I could at least get there.

Ive never had this issue and often run WoW under wine for Monster.Its as easy as copying a BDROM onto the HDD and running it in place. Well, v6 broke that requiring 2 discs, but anyways...never had an issue until Fedora.

Debian obviously requires flgrx installed.Fedora does not.
And its not a matter of DX not working because Oblivion and nulldc are working(if you could call it that) and both require 9 or above.

Audio sttuttering is either a wine issue or a pulseaudio one.Maybe an alsa one as well(most cards have 5.1+ audio out).Im noticing it with multiple apps.

Ive flushed my wine prefix a few times, so I dont think thats it either.

Any help is appreciated.

¿With "Audio sttutering" you refer to an increase of a lot of work of mixer (a lot use of CPU) and trunk Audio 10-30 seconds?

If yes, I have this problem a lot time ago with kmixer and Alsa or Pulseaudio. Other mixers don't resolve the problem.

This doesn't work for me:

"run winecfg and “disable” the “d3d11” dll in library tab."

Try also disabling d3dx11_36 and d3dx11_42
Also, if worst comes to worst, you can manually edit the config file (located inside the WTF folder inside the wow directory) and change the line "SET gxApi "D3D11" to "D3D9" or "OpenGL"

So I try to start WoW with OpenGL:
cd ~
MESA_GL_VERSION_OVERRIDE=3.3COMPAT wine64 '.wine/drive_c/Program Files (x86)/World of Warcraft/Wow-64.exe' -opengl

And I get this:

ERROR #132 (0x85100084) Fatal exception!
ProcessID: 8
Exception: ACCESS_VIOLATION
The instruction at "0x00007fb77eccd955"
referenced memory at "0x000000000000"
The memory could not be "read".

This is my computer:
Xubuntu 14.04
wine-1.7.50
GFX card Intel HD4000
WoW 6.2.2 Build 20490

WHAT BROKE OPENGL?! I don't wanna play D3D9 :(
wine64 '.wine/drive_c/Program Files (x86)/World of Warcraft/Wow-64.exe' -d3d9

It's an issue with wine-1.7.50 and wow. Either upgrade wine versions or do the workaround I referenced here:

appdb.winehq.org/commentview.php?iAppId=1922&iVersionId=32314&iThreadId=95436#Comment-95466

This doesn't work for me:

"run winecfg and “disable” the “d3d11” dll in library tab."

OpenGL still fails as usual.

When I run WoW in d3d mode, all text is displayed as gibberish messed up characters. This includes almost ALL in-game text. Interestingly, results are varied on the login and character selection screens.

When I try to switch to OpenGL mode (using "-opengl" with wine OR "SET gxApi "opengl"" in config.wtf) it crashes at startup with error #132 and error message "instruction at 0x000000 failed to reference 0x00000" or something like that

My system info:
Dell Precision M6600 Laptop
Intel i7 quad core 2.8 GHz CPU
8GB RAM
NVIDIA quadro 4000m graphics card
Ubuntu 14.04

My config info:
wine 1.7.50
WoW 6.2.2
Nouveau display driver

Here is what I have tried (in almost every combination):
- WoW-64.exe AND WoW.exe (using "-noautolaunch64bit")
- disable d3d11 dll- NVIDIA binary driver 3.46.82
using winecfg
- with and without "-opengl" (d3d and opengl modes as I understand it)
- add Fonts folder with 4 .ttf entries to WoW folder
- install MS using winetricks
- Playonlinux install
- add "SET ffxGlow "0"" and "SET ffxSpecial "0"" to Config.wtf

Also used NVIDIA binary driver 3.46.82. This fails at startup using wine manually, but INTERESTINGLY this worked for the PlayOnLinux install. This fixed the fonts in d3d mode, but many other graphics would not render at all....this leads me to believe it may be a graphics card driver issue.

Planning to try:
- Older versions of wine using PlayOnLinux (1.7.29, 1.7.49)
- Bashing my head into my desk repeatedly

I am noticing some similar problems out there with openGL but I haven't seen anyone with this issue with fonts in d3d mode. Any tips would be greatly appreciated.

Have the same problem. Full mesage is:
"The instruction at '0xf701946e' referenced memory at '0x00000000'. The memory could not be 'written'". Have you any workaround?

This may be a different issue because the "instruction" on mine was 0x00000000 and it said memory could not be "read".

I still have no fix for the OpenGL bugs....but as a temporary fix, I have switched to an NVIDIA binary driver and I am now able to run the game in d3d mode.

For the OpenGL crash, since you're using 1.7.50, you're probably running into this issue:
appdb.winehq.org/objectManager.php?sClass=version&iId=32314#95365

If so, as Stefano says you can "run winecfg and “disable” the “d3d11” dll in library tab.". This worked for me.

"If so, as Stefano says you can "run winecfg and “disable” the “d3d11” dll in library tab.". This worked for me."
It's work for me too, thanks.

Hey!

Since wow patch 6.2.2, I get a message before the login, complaining about my graphics card doesn't support shader-modell 3 and that the support will be dropped with the next patch.

I run wow with opengl as with d3d the FPS outside of buildings are lower than 10. Although d3d would support shader-model 3, so better graphic support. :(

Any Hints what I can do?

Regards,
Thilo

Card: NVidia GeForce GT 640

This is very disconcerting. I really hope this isn't the case, because I'm not playing wow in d3d mode. It would be annoying if after 10 years of playing wow on linux, it stopped working due to this restriction. We should post something in the wow forums and see what comes of it.

I too am having the same issue. Did you post in the WOW forum?

My WoW broke after the flying patch today. Keeps crashing on strartup.

Wine version: 1.7.50
Linux Mint Cinnamon 17.2
64-bit
dx3d11 is already off.

Error message: puu.sh/jXhXd/9e62a09aaf.jpg

Anyone else experiencing the same?

I had the same problem, I ran the battle.net client from inside my WoW bottle instead of running the battle.net client from the Wow-64.exe iteself. Then it updated and all is good.

Ah, yes thank you. This fixed it for me. Seems the issue was with the patching, and not with wine itself.

I had the same issue.

My fix was to disable dbghelp.dll in the winecfg library list. The crash seems to occur in that dll after about 4 other levels of crashes before that (dbghelp.dll assists with stack tracing and other debugging features, I'm guessing they are using it to do some kind of dump for a recoverable crash and then it crashes in the dll so it fails the program)

Error

User1:~$ wine /home/User1/.wine/drive_c/Program\ Files/World\ of\ Warcraft/Wow.exe > Bug.txt

fixme:advapi:RegisterTraceGuidsW (0x44f7d0, 0x5056d0, {468db73b-6e55-4231-9607-a22d08feaecf}, 1, 0x33fd90, (null), (null), 0x5056d8): stub

fixme:advapi:RegisterTraceGuidsW register trace class {468db73b-6e55-4231-9607-a22d08feaecf}

fixme:ver:GetCurrentPackageId (0x71e504 (nil)): stub

fixme:win:RegisterDeviceNotificationW (hwnd=0x130f78, filter=0x71e92c,flags=0x00000001) returns a fake device notification handle!

fixme:winsock:WSAIoctl SIO_GET_EXTENSION_FUNCTION_POINTER: unimplemented TransmitFile

fixme:ntdll:server_ioctl_file Unsupported ioctl c8000006 (device=c800 access=0 func=1 method=2)

fixme:winsock:server_ioctl_sock Unsupported ioctl c8000006 (device=c800 access=0 func=1 method=2)

fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (_WSAIORW(IOC_WS2, 6))

fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046}

fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub

fixme:heap:RtlSetHeapInformation 0x16d0000 0 0x32fdc8 4 stub
err:winediag:schan_imp_init Failed to load libgnutls, secure connections will not be available.
err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform

fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported

fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform

fixme:mpr:WNetGetUniversalNameW (L"C:\\Program Files\\World of Warcraft\\data\\data", 0x00000001, 0x18de940, 0x18de93c): stub

fixme:win:EnumDisplayDevicesW ((null),0,0x18df578,0x00000000), stub!

fixme:d3d11:D3D11CoreCreateDevice Ignoring feature levels.

fixme:dxgi:dxgi_device_init Ignoring adapter type.

fixme:d3d11:device_parent_create_swapchain_surface device_parent 0x146d00, container_parent 0x17ea80, wined3d_desc 0x18df4b8, surface 0x18df4a0 partial stub!

fixme:d3d11:device_parent_create_swapchain_surface Implement DXGIwined3d usage conversion

fixme:win:EnumDisplayDevicesW ((null),0,0x18dcdb8,0x00000000), stub!

fixme:win:EnumDisplayDevicesW ((null),1,0x18dcdb8,0x00000000), stub!

fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub

fixme:process:GetLogicalProcessorInformationEx (3,(nil),0x33ef54): stub

fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform

fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported

User1:~$ fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB!

User1:~$

System

System information report, generated by Sysinfo: 8/12/2015 11:12:47 PM
sourceforge.net/projects/gsysinfo

SYSTEM INFORMATION
Running Ubuntu Linux, the Ubuntu 15.04 (vivid) release.
GNOME: 3.14.1 (Ubuntu 2015-03-18)
Kernel version: 3.19.0-25-generic (#26-Ubuntu SMP Fri Jul 24 21:16:27 UTC 2015)
GCC: 4.9.2 (i686-linux-gnu)
Xorg: 1.17.1 (19 March 2015 09:27:07AM) (19 March 2015 09:27:07AM)
Hostname: XXX
Uptime: 3 days 1 h 20 min

CPU INFORMATION
AuthenticAMD, AMD FX(tm)-6100 Six-Core Processor
Number of CPUs: 6
CPU clock currently at 1400.000 MHz with 2048 KB cache
Numbering: family(21) model(1) stepping(2)
Bogomips: 6644.14
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall

MEMORY INFORMATION
Total memory: 1996 MB
Total swap: 2027 MB

STORAGE INFORMATION
SCSI device - scsi0
Vendor: HL-DT-ST
Model: DVDRAM GH60N
SCSI device - scsi2
Vendor: ATA
Model: WDC WD10EADX-22T
SCSI device - scsi3
Vendor: ATA
Model: WDC WD15EARS-00Z

HARDWARE INFORMATION
MOTHERBOARD
Host bridge
Advanced Micro Devices, Inc. [AMD] Family 15h Processor Function 5
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx0 port B)
PCI bridge(s)
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) (prog-if 01 [Subtractive decode])
Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port B) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port D) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (PCI express gpp port H) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] RD890 PCI to PCI bridge (external gfx1 port A) (prog-if 00 [Normal decode])
Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge (rev 40) (prog-if 01 [Subtractive decode])
Advanced Micro Devices, Inc. [AMD/ATI] SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) (prog-if 00 [Normal decode])
ISA bridge
Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller
IDE interface
Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller (rev 40) (prog-if 8a [Master SecP PriP])
Subsystem: Gigabyte Technology Co., Ltd Device 5002

GRAPHIC CARD
VGA controller
NVIDIA Corporation GF119 [GeForce GT 520] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. Device 1529

SOUND CARD
Multimedia controller
NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
Subsystem: eVga.com. Corp. Device 1529

NETWORK
Ethernet controller
Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Motherboard

NVIDIA GRAPHIC CARD INFORMATION
Model name: GT520
Card Type: unknown 16x
Video RAM: 2048 MB
GPU Frequency: 270 MHz
Driver version: NVIDIA UNIX x86 Kernel Module 346.59 Tue Mar 31 13:19:00 PDT 2015

The only new from last build to this one is the patch update from Blizzard not sure what but last patch unable to play wow. But I also installed Simple Screen Saver witch only turned off flipping is what the message said in SSR but I then re-enabled it still no wow any hints on how to fix this?

pastebin.com/6e43YQeE
postimg.org/image/uqyyn7hkf/

Some information I got from running WoW in OpenGL mode. This issue has existed in 1.7.4x wine versions and I don't think this issue has been elevated enough in order to be fixed as an issue.

Sinds 1.7.5 Battle.net not working anymore, white screen. WoW direct start works but it has problems to exit, hanging lang black screen.

(Diablo works as before. StartCraft II has the same problems as before, it runs, blizzard-bug after exit.)

Ubuntu 15.04 64bit.

commit b2f5fad4b640e178a1d9d04bec5a7c218045b9ad just prior to 1.7.50 release introduced a regression that causes WoW to crash immediately at launch. commit 4cf1bb929fad3b898050ae8d305e5c8a8948ca2a just after the 1.7.50 release seems to have fixed the regression.

WoW players should be cautious about updating to 1.7.50 unless their distro maintainer has backported the latter commit to the release or if they are comfortable compiling from source.

This happend to me, in 1.7.50 the game just crash, but Heroes of the storm and Hearthstone works fine, and i have no idea what to do

I solved installing wine-snapshot (find in your distribution). Is the actual development version of wine. In this, the problem with WoW is solved.

Regards

Thanks, that work

The regression also occurs compiling wine from source.

In 1.7.50 “What's New” it is reported:

What's new in this release (see below for details):
- New version of the Gecko engine based on Firefox 40.
- First steps of the Direct3D 11 implementation.
- Better font matching in DirectWrite.
- Support for OpenMP on ARM platforms.
- Various bug fixes.

The problem seems to be the second point: “Direct3D 11 implementation”,

Launching “Wow.exe” under 1.7.50 in the output immediatly appear these errors:

fixme:d3d11:D3D11CoreCreateDevice Ignoring feature levels.
fixme:dxgi:dxgi_device_init Ignoring adapter type.
fixme:d3d11:device_parent_create_swapchain_surface device_parent 0x1412d8, container_parent 0x171308, wined3d_desc 0x18df430, surface 0x18df46c partial stub!
fixme:d3d11:device_parent_create_swapchain_surface Implement DXGIwined3d usage conversion
fixme:win:EnumDisplayDevicesW ((null),0,0x18dcb90,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),1,0x18dcb90,0x00000000), stub!
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
fixme:process:GetLogicalProcessorInformationEx (3,(nil),0x33ef54): stub


my workaround:

run winecfg and “disable” the “d3d11” dll in library tab.

Wow starts correctly.


This is only a workaround, i think the problem is a regression bug of this versions of wine.
I hope that the developers of wine can solve it quickly,

enjoy

I can confirm this workaround.

i reinstall the 1.7.50 version, disable d3d11 and it works fine again, thanks a lot

It is already fixed (in trunk) as I mentioned in my first post. If you compile the 1.7.50 release from source the regression will still be present since the fixing commit (4cf1bb929fad3b898050ae8d305e5c8a8948ca2a) was pushed to trunk after the 1.7.50 tag.

If you are aiming to get a proper fix by building from source, you will need to grab several commits after the 1.7.50 tag that include the fixing commit. Basically since the fixing commit missed 1.7.50, the issue will not be fixed for people pulling binary packages until the 1.7.51 release unless distro maintainers choose to backport commits or if a distro offers some sort of wine-snapshot package that is rebuilt outside of the wine release cadence.

Big thanks to Chris Rankin for comment #5 here
bugs.freedesktop.org/show_bug.cgi?id=91600#c5
I can finally again run opengl mode on Intel integrated card without error #132.

add this to startup script:

MESA_GL_VERSION_OVERRIDE=3.3COMPAT
export MESA_GL_VERSION_OVERRIDE

And now WoW is running successfully in OpenGL mode. It appears that WoW *requires* OpenGL 3.3 over 3.0."

Seriously. This made my laptop run wow with ~70fps.
Thanks a lot!!

Holy crap,

THANKS a lot!! I was having the same issue and adding the commands you posted fixed the OpenGL mode in WoW on my system (Intel HD Haswell)!

Cheers,
Alex

Can confirm this fixed the "access violation" crash-on-launch for me, on my 4th-gen i5 with integrated graphics.

MESA_GL_VERSION_OVERRIDE=3.3COMPAT WINEDEBUG=-all wine "Wow-64.exe" -opengl

Successfully launches WoW for me.

Can confirm this worked for me, Ubuntu Mate, I3 Intel, HD4000 integrated graphics, Wine 1.7.44

Neither wine nor wine-staging (64 or 32) actually run this.

I don't know WHAT it is, but nvidia-driver, nuveou-driver, -noautolaunch64bit, -opengl, editing the config.wtf, and nothing really gets me past installing the bnet client.

The FURTHEST I get is running the game by just clicking the Wow.exe - It warns me about Graphicsdrivers being out of date and then crashes after a few seconds in character selection.

I can run the Battle.net client... and get an info about not being able to find the graphics context...

And I can start the World of Warcraft Launcher.exe... telling me it wants DX...

---
How again is this platin (it might be, once installed, configured manually, ... )? At least point out that it's basically a PAIN to install on a 64 bit system. :/

People tend to overrate their test results - I get reports claiming that are several problems which are rated "platin" at the same time (as long as there is only a single flaw, it isn't platin per definition). In that case I will rate them down of course - but if someone claims "It's all perfectly working" there is nothing I can do ;-)

As for your problem - I don't know if Ubuntu's wine is 64-bit only - in that case you could try to run wow-64.exe. For me both 32 or 64 bit run fine (with several minor flaws), but I don't know if the installer still runs.

Well, I really don't know what to do. Out of ideas and even the most recent guides implicate it should be working. (i.e. webupd8)

I've tried the 32bit wrapper version, the 64 bit version, really - done it all beyond downloading the whole thing again (I'm on 300kb here, so that would take me roughly a WEEK of downloading).

Maybe it's my system, maybe it's the install... But I do know: It doesn't work.

Last idea could be that it's that source-of-all-happiness of having an onboard graphics adapter present as well as the (only used) dedicated nvidia. But then again - rebooting to the games launcher called "windows" takes only seconds. I would have loved to wipe it, though.

BTW, if your laptop has both an on-board (Intel?) graphics chip as well as an NVIDIA chip then maybe WoW is actually trying to run with the on-board graphics really? To use the NVIDIA chip, you would need to install Bumblebee:

github.com/Bumblebee-Project/Bumblebee/wiki/FAQ

And then run WoW as:

$ optirun -b primus World\ of\ Warcraft.exe

Blizzard lists the compatible graphics cards here:
eu.battle.net/support/en/article/world-of-warcraft-supported-video-cards

You don't say what your graphics hardware actually is, but I would have expected WoW to run fine in either 32 bit or 64 bit mode with an NVIDIA chip and their binary blob.

Fedora has just updated to 1.7.46-staging and now Battle.net just shows a blank white window. The console fills up with messages like these:

fixme:d3dcompiler:make_assignment Check for casts in the lhs.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
fixme:hlsl_parser:declare_vars Complex initializers are not supported yet.
fixme:hlsl_parser:hlsl_parse Array.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
fixme:hlsl_parser:hlsl_parse Array.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
fixme:hlsl_parser:declare_vars Complex initializers are not supported yet.
fixme:hlsl_parser:hlsl_parse Array.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
fixme:hlsl_parser:hlsl_parse Array.
fixme:d3dcompiler:make_assignment Check for casts in the lhs.
err:d3dcompiler:compile_shader HLSL shader parsing failed.

All of my Radeon cards display this behaviour: RV790 and RV730

Same problem with 1.4.47-staging and nvidia.

It works fine if you change the OS to Windows XP.

I've now found this bug in the database:

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

Disabling d3dcompiler_46.dll in winecfg allows me to keep Wine configured as Windows 7.

I dont believe i ever tried CSMT on my laptop. Going to try it out. :)

Running Wine-staging 1.7.47 with CSMT enabled, it only seems to freeze in Tanaan when Liquid Detail graphical option is set to something higher than low.

Perfect! Changing the setting solved the problem entirely.

Confirming Steve's report, running 1.7.45-staging w/ CSMT enabled I get a hard freeze in Tanaan. Other places I tried seemed fine; performance with CSMT was a good deal better than without it, but if it freezes when the newest area loads it's not of much use.

When I get into game any time I see players the environment goes all rainbow colored. what do I do?

This also happens to me, and I'd be interested to know what to do. I'm running Intel graphics with driver i915.

After further investigation, I found this: www.linuxquestions.org/questions/fedora-35/wow-and-intel-hd-problem-4175483355/

Don't know if it's any help.

Not sure if your fix worked... did as the instructions stated, but now when I try to click play it wants an update. When I click update it wants me to open with admin rights and since I am new to linux I have no idea how to accomplish this task. I have done research and not found much help.

Resolved:

The problem is because Fedora did not ship "S3TC texture compression". This is a non-free package.

fedoraproject.org/wiki/Forbidden_items?rd=ForbiddenItems

You can get this package from RPM Fusion : rpmfusion.org/

sudo dnf install libtxc_dxtn libtxc_dxtn.i686

Running Wine-staging 1.7.46 with CSMT enabled, and the game freezes in Tanaan Jungle.

Nowhere else, everything runs smoothly with 60 fps or thereabouts, but as soon as I look at Tanaan, it freezes up and must be force quited.

I believe this is the terminal output when that happens, though there may be more.

fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:advapi:CreateRestrictedToken (0x2414, 0x0, 3, 0x2fe7e980, 19, 0x41359c04, 5, 0x22bc50, 0x22bb10): stub
fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x22ba68,0,(nil),0x41359c00,0x22ba50,0x22ba38) stub!

For me it freezes with:
err:ntdll:RtlpWaitForCriticalSection section 0x100a8 "heap.c: main process heap section" wait timed out in thread 0009, blocked by 0015, retrying (60 sec)

It seems to work fine with PlayOnLinux's wine 1.7.47 - no crash after 5 mins in tanaan. From looking at the performance it seems to have CSMT enabled too.

I couldn't try wine staging 1.4.47 yet. I'll report back if I run into any problems.

WoW 6.2 is crashing on start-up with every PC I have using Radeon / Mesa. Currently working around by switching to D3D9.

Interesting, I also have access to a Fedora 22 laptop with NVidia graphics and the binary blob, and WoW 6.2 runs fine on that machine with OpenGL.

I have discovered that this crash with Radeon/Mesa is because WoW uses a "compatibilty" OpenGL profile, which in my case is only OpenGL 3.0. It would seem that WoW now *requires* OpenGL 3.3.

I am working around the problem by setting this environment variable before launching WoW:

MESA_GL_VERSION_OVERRIDE=3.3COMPAT
export MESA_GL_VERSION_OVERRIDE

My NVIDIA machines all advertise OpenGL 4.x Compatibility profiles, and so are unaffected.

I submitted a new version but its not showing up yet. However now the sound is all choppy and i dont know what to do for fix. :(

Ok so it does not seem limited to wow. When into wine configurationn and when i click test sound its all distorted. This is on wine 1.7.35

Okay this is wierd... the soudn actually works through the speakers and my jack headphones but it doesnt work well on a usb headset. I dont know how to submit a bug for that. When i try to switch to OSS the sound driver in wine doesnt even load any sound devices. Rawr!

Okay the game runs fine on my laptop and running in opengl. However sometimes when I try to open a ticket, it doesn't show... so I have to restart the game (no biggy). However when I do submit a ticket I cant view the ticket responses in game. Anyone ever got this working?

Hi,
does anyone else received a 6 month ban and the only "strange" think done was using Wine to play World of Warcraft?

No, i always used wine to play World of Warcraft and never get banned for this.

Been playing WoW under Wine since about patch 1.4, no ban here.

nope. was never banned for that. but there are plenty of free servers. I know its a hassle until you go free, like monster but what can you do? Its blizzards at fault.

I am running ubuntu 14.01 just got a new video card a navdia geforce 740 serious. i am not sure if i loaded the drivers right, but wow doesn't so any text for me now... does anyone know what is going on?

Ubuntu 14.04, Intel i5, nvidia 346.59 Geforce gtx670, wine 1.7.38

Just today WoW has started freezing my screen and forcing a reboot periodically. I tried updating the video drivers and wine and got the same result. These freezes are similar to lockups I previously experienced with D3 and Heroes of the Storm; the music keeps playing, I can move the mouse but can't click anything, the keyboard is inactive, and I usually manually reboot before the music stops, the screen goes black, and the fans run like crazy.

Running two monitors 1920x1080 each, tried lowering graphics settings in wow to "good" but still got freezes.

Anyone else having problems?

I think I might have. For me, WoW itself freezes up but the rest of my system is fine. I don't lock the cursor to WoW, so I can move my mouse to my second monitor and use that monitor just fine. If I send a SIGSTOP to WoW it stops, and my system is back to normal. Is that what you get, or is yours different?

Does anyone else have an issue with the minimap not being accurate when indoors and running with opengl? Even zooming the minimap in and out (while indoors) shows it jumping around. If I use D3D instead of opengl it works fine, and this does happen on a clean install.

Yes, my position on the minimap is "off" by quite a bit.

Same issue here too. Also tried wine-staging, but it suffers from the same problem.

The offset is different at every minimap zoom level but seems consistent at each level. It might be possible to work around it with a LUA addon.

test csmt activated always FPS: min max medium
1: /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 0, 9, 8
2: force_s3tc_enable=true taskset -c 0, 1, 2, 3, 4, 5, 6, 7 /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 0, 9, 8
3: force_s3tc_enable=true taskset -c 0, 1, 2, 3, /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 30, 65, 55
4: STAGING_SHARED_MEMORY=1 LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 force_s3tc_enable=true taskset -c 0, 1, 2, 3, /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 0, 9, 8
5: __GL_THREADED_OPTIMIZATIONS=1 force_s3tc_enable=true taskset -c 0, 1, 2, 3, /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 10, 15, 9
fps: 30, 65, 55
6: force_s3tc_enable=true /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 30, 65, 55

For about three weeks now I have been having problems playing because the client keep freezing.

The screen become completely still, but I can move the mouse (with WoW cursor) and I can alt-tab out of the game without problems.

I cannot find any in-game pattern that may cause the problem; some time I can play for two hours and some time it freezes after few seconds after login. Wednesday I raided Black Rock Foundry and it freezed only while walking between bosses, but not during the bosses fights themselves (that I assume it is more resource intensive).

The most frustrating part is that I do not get any error message that may lead to the cause. If I run the game from the command line I get: pastebin.com/CXWCbt55
as you can see, they are just fixme messages.

I get NO error in either:
- the game itself;
- dmesg;
- /var/log/messages
- /var/log/Xorg.0.log

System Monitor (KDE Task Manager) does NOT report WoW as a zombie process.

I use the following script to run the game: pastebin.com/2aEixtfJ

The game config is the following: pastebin.com/anL26pkv

I tried to run the games without any addons and I tried to delete the cache and WTF folder.

During the week-end at the end of the first week I did a complete re-install of the whole system in case that there was some config/update that may be the cause: for few days in the second week the game seemed stable again, but eventually the problem resurfaced (and I did NOT do any particular update or config change). During the first week and after the system re-install, I re-installed the game from scratch, but it didn't help.

I am running Gentoo 64 bits with kernel 3.18.11-gentoo, Nvidia drivers 346.47 and Wine 1.7.40 (and I did tested with few previous releases). I have Intel i7-4790K 4.00GHz, 16 GB of RAM and a GeForce GTX 980.

Any idea?

Thanks in advance.

lately I too have the same problem ....

I don't have this problem.

I noticed that WoW runs much better with -d3d when you use CSMT patches (wine staging). I get almost the same FPS as on windows, and can raid just fine (which previously never worked).

You can try force_s3tc_enable=true, which did fix freezes on my intel card. I'm using my Nvidia card now though.

Here is my launch script:
WINEPREFIX=~/.wine64 force_s3tc_enable=true taskset -c 5,6,7,8 wine64 wow-64 -d3d11

Works fine with -opengl too, I prefer to assign CPUs directly because CPU1 is usually utilized by the window manager etc.

ma... I tried, but I 9 fps ....

Try wine staging ( www.wine-staging.com/ ). Also make sure you check the option for CSMT in winecfg. Fedora uses Wine Staging by default. I get ~60 FPS everywhere prior to WoD, and 30-60 FPS in Draenor, 40-50 FPS in Draenor raids. But that's due to my crappy 550Ti. I wouldn't get more on Windows either. And as a bonus you also get Water effects etc.

test csmt activated always FPS: min max medium
1: /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 0, 9, 8
2: force_s3tc_enable=true taskset -c 0, 1, 2, 3, 4, 5, 6, 7 /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 0, 9, 8
3: force_s3tc_enable=true taskset -c 0, 1, 2, 3, /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 30, 65, 55
4: STAGING_SHARED_MEMORY=1 LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 force_s3tc_enable=true taskset -c 0, 1, 2, 3, /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 0, 9, 8
5: __GL_THREADED_OPTIMIZATIONS=1 force_s3tc_enable=true taskset -c 0, 1, 2, 3, /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 10, 15, 9
fps: 30, 65, 55
6: force_s3tc_enable=true /opt/wine-staging/bin/wine64 wow/Wow-64.exe fps: 30, 65, 55

Does it still crash?

Seems like __GL_THREADED_OPTIMIZATIONS=1 was the culprit. Does it still crash?

Hi all,
sorry for the late answer.

Personally I tested by forcing the 32 bit client (-noautolaunch64bit) and for these few days the client.

I will now try the staging patches and the force_s3tc_enable; I'll report in a couple of days (so to have various tests).

I tried the various combination as diego did, but they all eventually freeze on me.

There is one thing I just noticed: when the game freezes, one of my CPU cores get used at 100%; I confirmed it also in the System Monitor that the WoW process actually go to 100% (I didn't noticed it before because, for some strange reason, by default System Monitor display the usage of a process by dividing the workload by the number of all cores available even if the process is not using all of them).

I just noticed that my original answer of an hour ago got truncated.

I was saying that I tried to force the 32 bit client for few days and it has been stable (I even raided yesterday night without issues).

after three days of testing ..
1) in raids sometimes stops the game for a few seconds ... do not know why but the fps suddenly fall to 5 and then back to 20-25
2) the cpu gets to temperature values impressive ... last night came after a session raid of two hours and a half ... at 73-76 ° C ....

script start:
force_s3tc_enable=true taskset -c 0,1,2,3 /opt/wine-staging/bin/wine64 wow/Wow-64.exe

Hi,

I got exactly the same problem on exactly same configuration:
- Gentoo 64 bits
- kernel 3.18.11-gentoo
- ati-drivers 14.12-r3
- Wine 1.7.41

I thinks this start freezing after multilib change (abi_x86_32 use flag). Before that i add no problem.

I tested a lot of combinaison and a finally find one working : run in 32bits mode.

I now got no freeze since a while with:
WINEARCH=win32 wine .wine/drive_c/Program\ Files/World\ of\ Warcraft/Wow.exe -opengl

Just wanted to add, this seems to work for me too. I was getting freezes and pauses within 30 seconds of logging in when running a 64 bit wine prefix, but a 32 bit wine prefix has had zero pauses or freezes for a while now.

There are (unfortunately) many kinds of "freezing". The one that I am experiencing right now is happening because the full-screen WoW window (OpenGL, GNOME3) loses focus. The game unfreezes again after I hit the "Windows" key on my keyboard and jump to another workspace and back.

This bug has been infuriating me ever since Fedora "upgraded" to Wine 1.7.41.

'wine World-of-Warcraft-Setup-enGB.exe'

Prompts to install Battle.net, installs it just fine.
Prompts to install game and that it will require 28gb. 203gb free space.

After a while the installer dissapears with the following error:

fixme:wtsapi:WTSRegisterSessionNotification Stub 0x30086 0x00000000
fixme:d3d9:D3DPERF_GetStatus (void) : stub
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Value in failed request: 0x0
Serial number of failed request: 3482
Current serial number in output stream: 3483

[ jkw@magni Downloads]$ glxinfo | grep glx
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4
server glx extensions:
client glx vendor string: NVIDIA Corporation
client glx version string: 1.4
client glx extensions:

OpenGL support in 6.1 seems to have been fixed up. In 6.0.3 and earlier, I was noticing that WoW was running slower after and hour or two of play, but I'm not noticing that any more. Also, 6.1 no longer renders distant textures incorrectly, and the occasional flickering I used to notice with my Radeon HD6450 is gone too.

On the downside, I am still seeing a lot of deadlocks between threads (I am using the Fedora 1.7.36-2 RPMs, which are built from the "wine-staging" tree):

err:ntdll:RtlpWaitForCriticalSection section 0x9a4b8 "mmdevdrv.c: ACImpl.lock" wait timed out in thread 0038, blocked by 0030, retrying (60 sec)

This particular deadlock *seems* to be with the "alsa" driver, on hardware where there's a "mult-channel" output device.

Good morning, I think we can define gold, when you can play with the graphics D3D11 thing for now you can not do, in d3d9 is as prohibitive and there is not enough thrust hardware .. and above all do not see improvements for at least two years even in opengl ... I probato ubuntu with gallium but nothing to do ... and the game has been around for 10 years ...
if we have a hope that Linux will become the first choice of people gaming is a key part of this hope ....

I have a hard time understanding why we would rate it at gold? I can't even get the game running after 6.1-patch. Worked flawlessly before.

Are you aware that 6.1 silently resets gxApi in the Config.wtf file to "D3D9"? Perhaps you are running with DirectX instead of OpenGL, and you are suddenly hitting a DirectX bug?

hem, I mean that the game is garbage ....

sorry my english is bad.

I have a launcher-script with -opengl flag. Tried both with and without. Removed my entire "~/.wine" now and starting from scratch.

Fresh reinstall with wine 1.7.33 on Gentoo ~amd64, Intel core i7-2600 with nvidia geforce gtx 770, and using opengl renderer results in inconsistent FPS varying anywhere between 10 and 60 (my frame rate cap is set to 60).

Multi-core affinity appears to be the culprit, top shows wow process jumping between cores. Using 'SET processAffinityMask "1"' in Config.wtf fixes the problem and FPS is stable at frame rate cap (60).

Not sure if this is a bug in WoW or Wine.

SET processAffinityMask "1" doesnt need to be used anymore. All it does is screwing up. It is still written in many "How to get more FPS in wow tutorials" but it is WRONG WRONG WRONG!

Dont use SET processAffinityMask "1"

Dont use SET processAffinityMask.......accidently wrote the 1.

The cvar should do nothing anymore ...for years

I am aware of a bluepost that said the cvar "affinityMask" doesn't work anymore, but actually it still *does* - at least in wow under wine/linux. Just try it and observe the per core cpu usage with something like htop.

I use a value of 3, which confines WoW to the first 2 cores, to get slightly higher and more stable fps.

The cvar appears to have been last updated with patch 3.3.2 which removed the need for it to be manually set due to hardware detection. The cvar still exists in usable form and setting process affinity masks according to the table hosted at www.wowwiki.com/CVar_processAffinityMask show matching results using process monitoring tools.

The only official reference to possible removal I can find is a green post located at us.battle.net/wow/en/forum/topic/10160035925
This is a "MVP" user stating an opinion that may be, and in this case apparently is, incorrect.

The fact remains that a problem exists and setting this cvar appears to resolve it.

It seems to be right...it doesnt do anything on my i7-4930 while on my i5 (without HT) it DOES indeed help....(i used 3)

WOW was running very nicely until I did this week end some upgrades on @world and nvidia-drivers, both 343.36 and 346.35. It ends with wow freezing a few seconds after logging into a character. Killing the process and relaunching it ends at loading, stuck at 90%, not able to get back to the character. I had some success by downgrading my driver to 340.76. But finally had the same problem. It's a bit weird.

346.35 appears to work correctly here. Process affinity proved problematic instead.

I used to use fglrx under Fedora 20, and wow worked great.
When I upgraded to F21, I was not able to load the amd driver anymore.
The stock "radeon" driver may be the culprit, but now I'm experiencing crashes 10 seconds into the game.

The open source AMD driver should run good with directx mode. Which mode are you running wow in?

I'm using it in OpenGL mode; as running it in directx mode slows it down very much..

if u use the open source AMD driver try use Directx it is reported that for AMD the open source driver does very well with WOW.

My 64 bit wow fails to start giving me an error box:
The CAS system was unable to initialize:

My Wine version is 1.7.30
Fedora 19 64 bit.
(This is both on a machine with a nvidia card and the proprietary drivers and one with AMD and the catalyst drivers)

This started happening just before New Years.

Very rarely it will start. It did this once after I recopied wow and once after I deleted my .wine directory tree. But it is not repeatable.

The 32 bit version starts but seems to be slower then it used to be.

Any one else having this problem? Anyone have suggestions?

Angus

Launch the Battle.net Launcher > click on Options > select Scan and Repair.

Affter that everything should work

I would like to remind people Blizzard did update textures and did for a short time break the B.net App. It wouldn't surprise me if the culprit is the dual core function is broken again,

was having issues low fps since starting back up with the new expansion (usually had 5-10 d3d9, 20-30 opengl low settings when previously i had 50+fps on opengl). finally have something that appears to be working great for me (~70-80FPS med-high settings).

running on arch, Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz, GTX750M, nvidia driver 343.36.

using patched wine from: aur.archlinux.org/packages/wine-gaming-git/ with a 32 bit prefix

d3d9 gfxapi, csmt enabled, and the following launch command: LD_PRELOAD="libpthread.so.0 libGL.so.1" WINEDEBUG=-all __GL_THREADED_OPTIMIZATIONS=1 wine Wow.exe

opengl had higher fps, but i stuck with d3d9 for the spell effects since the fps was holding out well

Process affinity may have been broken with WoD. Tried putting 'SET processAffinityMask "1"' in Config.wtf?

Running on relatively old Hardware (Phenom X2, 4GB RAM, Geforce 295GTX) with Arch Linux. Playing WoW through wine was never a problem with OpenGL. Since WoD they've dropped below 15fps for me. I just found out that switching to D3DX9 boosts fps for me, that i am able to play WoD with a more satisfying frame rate over OpenGL.

Would be interesting to know what driver you use? The Nvidia or the opensource driver?

Nvidia (nvidia-340xx on arch actually)

This is really strange.....what is your average FPS?

PvP (BG)
5man (dungeon)
Open World (questing etc)
Mass (Ashran+Raiding)

And Also since you use D3D what are ur settings (effects etc)

Thx in advance

Maybe a silly question. But are you sure?
I only ask, because then it would make perfectly sense what you describe, because direct 9 support was added to the open source drivers recently.

Try
lsmod |grep nv
lsmod |grep no

I tested it now on 2 Systems one with a Titan and one with a 780 TI
I lose HALF fps average with Direct3d and it becomes unplayable in 40 Player+ situations.

While in OpenGl even in Ashran with 200 Players ill never drop under 25fps (2560*1440).

Thats why im really curious too

nvidia 10512002 108
drm 259106 4 nvidia
i2c_core 50152 3 drm,nvidia,i2c_nforce2
powernow_k8 25396 0
processor 27777 1 powernow_k8

Dunno what the culprit is. Playing Cataclysm through wine, i've almost got about ~50fps with OpenGL. WoD gives me a max of 12-15fps with it, settings to abseloute minimum. Switching to D3DX9 raises this to about ~30fps for me. Not much but playable for me.

After a while the game freezes, you can still move the cursor around but nothing else.

Can u give a little more information? (Ur configuration, are u running in 32 or 64 bit etc pp)

The game actually works okay, I believe it was due to downloading critical files. The problem is that my internet is very limited. So when trying to install from the disc, it doesn't seem to work -- instead downloading from the internet. This is very confusing.

When running Battle.net from the MoP disc to update, Battle.net immediately crashes. How can I install the game?

"It crashes" is not enough information for an appropriate diagnosis.
Do you have the latest wine?
Or try the latest battle.net app from us.battle.net/en/app/

I could run it quite well this year on Windows 8.

NVIDIA GeForce 620
8GB Ram
3.20 ghz Quadcore.

Thank you for any response. My internet is very bad so I cannot download it, so I must know if I can purchase it from the store.

it can ofc. the GPU is pretty weak though, but in opengl mode the game is not using the GPU that much.. so my bet is that with decent quality settings you are able to play just fine

do you use opengl?

Do you have any logs about the memory leak and may report them to stefan?

sry for late reply, seems to be fixed with latest builds - i still had 1.7.24 before.

where you saw the memory leak caused by csmt?
For me csmt is faster the nvidia extension.

it is faster yes.. but it leaks mem... after some time it becomes slow or crashes the game..depends what game.. i have tested with several games.. WoW, War Thunder (back when there was no native), Guild Wars 2, GTA IV

the higher your graphical settings are the faster you get the freeze/crash cause it leaks memory...

well thats what i have experienced with it..so i better use a bit slower GL_THREADED_OPTIMIZATIONS and have stable experience

Has anyone the same issue that the 64bit version of wow freezes after some time?
Using wine 1.7.31-csmt with multimedia patch applied.

csmt patched wine leaks memory imo thats probably why... im using without csmt but with GL_THREADED_OPTIMIZATIONS and its absolutely perfect

I tried copying your command to arguments in POL but it didn't improve anything. No change at all.

export WINEDEBUG=-all
export __GL_THREADED_OPTIMIZATIONS=1

thats what i have before i launch my wow.

my entire script: pastebin.com/i2MjWnFJ

my script: pastebin.com/HBSEWkYm

I figured it out. I use POL. I had GL_THREADED_OPTIMIZATION in aguments in config. I fond that I just needed to add =1 to the end and export_ to the begining. Now the game has stopped freezing and the ALSA buffer underruns are gone.

Yes and it makes the game unplayable at times. I also get lots of ALSA buffer underruns. One time the sound completely stopped! I hope the next version of wine fixes some or hopefully all of this. I am using wine 1.7.32.

Hi all,
sorry for the necroposting, but since a week ago I started to have the same problem.

I use the following in my script (is all on one line):
LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 WINEPREFIX=~/.blizzard WINEARCH=win64 wine /home/marco/.blizzard/drive_c/Program\ Files\ \(x86\)/World\ of\ Warcraft/Wow-64.exe -opengl

And it used to work very well, but now it freeze (but I can still move the mouse).

I have Wine 1.7.39, kernel 3.18.9-gentoo and Nvidia drivers 346.47.

The most frustrating part is that I am not getting any error anywhere. Not on the command line if I run the script from there, not in dmesg, not in /var/log/messages, not in /var/log/Xorg.0.log. Top isn't reporting any CPU spike and the Wow process doesn't become zombie.

Any idea?

Thank in advance.

Hi all,
sorry for the necroposting, but since a week ago I started to have the same problem.

I use the following in my script (is all on one line):
LD_PRELOAD="libpthread.so.0 libGL.so.1" __GL_THREADED_OPTIMIZATIONS=1 WINEPREFIX=~/.blizzard WINEARCH=win64 wine /home/marco/.blizzard/drive_c/Program\ Files\ \(x86\)/World\ of\ Warcraft/Wow-64.exe -opengl

And it used to work very well, but now it freeze (but I can still move the mouse).

I have Wine 1.7.39, kernel 3.18.9-gentoo and Nvidia drivers 346.47.

The most frustrating part is that I am not getting any error anywhere. Not on the command line if I run the script from there, not in dmesg, not in /var/log/messages, not in /var/log/Xorg.0.log. Top isn't reporting any CPU spike and the Wow process doesn't become zombie.

Any idea?

Thank in advance.

Has anyone tried 1.7.32 + OpenGL ? Does the FPS improve or it's the same ?

I just tested this on wine 1.7.32 with opengl on Arch linux. And getting the same thing, low fps. Standing in the middle of nowhere with no players in the old world I barely get 30 fps. Running on an AMD HD 6850.

Same here with 7770 on Arch. WoW on Linux went complete shit now... They must have changed something substantial, cause no way it's only about new player models.

Use TRHIS prefix if u have an Nvidia

export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1

i did. it's not improving at all. it's like is not even working (as it used to)

appdb.winehq.org/objectManager.php?sClass=version&iId=30545&iTestingId=87166

This is in wine 1.7.31, but the FPS issues you are having are most likely due to not having performance enhanced WoW yet.

Follow the instructions there and you should see a massive performance enhancement. The most important one is setting "processorAffinityMask" correctly as this is the difference between the game running on one or multiple cores.

i completely forgot about the process affinity. i will try and feedback.

The problem is that you can either play with crappy graphics (opengl, no shadows, no water, no SSA, no light fractions) and medium fps (still about half the fps than in windows) or good graphics (d3d) and unusable low fps.

For comparison: In Windows I can crank the graphics all up to ultra and still barely drop below 60 fps.

And yes, we are all using __GL_THREADED_OPTIMIZATIONS (I was the one promoting this in the first place) and a patched wine.

So when you rate this performance-wise as platin, it's not because it's so fast, but because it's fast enough for you - but understand that this may not be sufficient for everyone else. For me less than 30 fps during raiding is just not playable.

i can go along with the current state of OpenGL, what i cannot go along is the low fps. I rated this game as bronze, and not platinum. It was rated as gold in MOP (fair rating), right now it needs work.

@hirschhornsalz
1) No need to be a douche.
2) I have 20+ fps, which is more than enough to play any game, your standards are set too high, most movies are only made for 24 fps.
3) Yes it is less than on windows but guess what, you're not on windows anymore.
4) Are you also using processAffinityMask? Or are you blind to anything that isn't you own contribution?
5) Because you supposedly introduced that command other people aren't allowed to spread it without you being an ass about it?
6) We all know what the problem is, no need to tell us.

There is no need for this, polemics belong elsewhere. I do agree with hirschhornsalz that the game needs work. 20 FPS is not enough for a game, you need at least 30 in order for it to run smoothly. The difference Linux / Windows for this game is 3x, maybe 4x FPS with better graphics, so you cannot rate this game as Platinum or Gold.If you want the devs to have a look at it then report the problems, don't cover them up and say everything runs perfect.

I will just leave this here, go check part about 30 vs 60 fps, you will even find there an academic study proving more fps is always better:

www.reddit.com/r/pcmasterrace/wiki/guide

Nvidia 570 + I7 2600k, used to get over 100 fps using openGL, now i'm lucky if i hit 30 (and that is questing). BG's or even instances (basicly everything that brings together over 5 ppl) will drop my FPS to a bearly playable 15. Currently WoW WoD is unplayable under Linux. Switching to DX9 makes things worse. On W8 DX11 i get over 100 FPS with everything on Ultra.

use this prefix when use Nvidia cards and opengl

export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1

Hi.

I am using latest Open source drivers for Radeon R9 280x on Kubuntu 14.10 from oibaf PPA and running WoW in OpenGL (same applies to default drivers).

The problem I am getting is, by using low settings I get 30 FPS, but after 5 minutes of play the FPS drops to 8-10. After I reset the game engine (change vsync or triple buffer settings) it gets back to 30 FPS.

Unigine Valley does not have the same problem. Hope anyone has any info on this.

Best regards.

I don't have any proposed fixes for you but I also have the issue with the R9 280x on Linux Mint (and all flavors of Ubuntu) of getting around 30fps on low graphics(I get 100fps on ultra in windows).

My FPS does not degenerate over time but I feel that something must not be working correctly to only be getting 3/10th the fps in linux as windows on MUCH lower settings...maybe get 10% the use out of the card as on windows. (I have also tried open source drivers, amd beta drivers, gallium nine drivers) and all of them fell short of providing a flawless gameplay. I don't expect to play at the SAME fps or quality as windows, but this seems extraordinarily low.

I see the same with a Nvidia GTX 660 TI, 80 fps in the world on ultra, 20 fps at the same position with wine and the GPU usage is about 30%.

I suspect the new multicore support in WoW, which seems to have increased the fps in Windows slightly, but has a worse result in wine.

I dunno, I wouldn't call 80fps to 20fps a "slight" gain because of multicores. Whether or not this is the issue, I don't know but it would be nice to know if the issue is gpu or cpu related.

Sorry, this wasn't very clear.

In Windows the fps increased slightly. This is not noticable in the open world, where you have usually constant 60 fps limited by vsync anyway. But in crowded situations with many chars on the screen the fps is better than before, no more drops below 30 fps in a 25 man raid. When I disable vsync I get numbers well above 60 fps in the open world.

In Linux the fps decreased. I noticed a change in cpu load: Now 4 cores are used (before only two and that was with __GL_THREADED_OPTIMIZATIONS=1), and the sys time has increased - WoW spends now a significant amount of time in a spinlock in the kernel scheduler. So I blame the new multicore code in WoW.

Generally WoW is in most situtations cpu limited, in Windows and even more in Linux - I rarely get more than 30% GPU load in Linux, in Windows it stays more close to 90% if I disable vsync.

WoW under Wine with open source drivers and opengl mode runs with vsync on even if you turn it off in settings.

Try running WoW with `vblank_mode=0`.

Hello
So first the problem, when I'm running the game it feels like there are shocks not big ones but small graphics shocks all the time. The game is running about 40-60 FPS but it has these shocks when moving, the greater the speed the more shocks and it hurts my eyes.

Tried a different screen and it has the same issues.

Specs: Wine 1.7.30 OS Ubunti 14.04. (standard)
Running wine + wow opengl settings
And Have the lates catalyst beta driver from AMD

Any options?

Ps.; I tried fullscreen modes, windowed. Also that vertical sync option but none help. Also tried setting the catalyst driver to enhance the program settings.

Sounds very similar to the mac opengl bug described in the forums a few weeks ago. The workaround presented was to use the builtin fps limiter with 20 fps or something.

But if the stutter is very regular, an addon could be the cause. Also try to switch off yxour compositing manager.

Hello, do you have a link to this?

Also stutter might not be the right word. It looks like the graphics are not loading fast enough. If I move slow I don't have the problem, but when on a mount it is terrible. While I'm getting 60FPS at ultra. (The "stutter" also happens at low)

Hello, do you have a link to this?

Also stutter might not be the right word. It looks like the graphics are not loading fast enough. If I move slow I don't have the problem, but when on a mount it is terrible. While I'm getting 60FPS at ultra. (The "stutter" also happens at low)

So Im kind of new to the whole ubuntu thing, but got wine to work for LoL, but when trying to install WoW I keep getting an error when battle.net loads up and then the install crashes, any clue on what im doing wrong?

Error message of wine would be nice. Try to execute the installer from console to get it.

There might be missing library overrides (dbghelp comes to mind).

If you playing with different games you might want to think about using PlayOnLinux to manage wine installations. With that you can easily create different wine installations and choose different wine versions for them.
Yet you won't get POL support here.

Ever since I installed the 6.0.2 patch, I've been having this weird audio issues. Everything is slowed and slurred, and each and every sound plays at least twice. It's really weird, unlistenable even, it worked fine before, does any one have any ideas what could be wrong?

Hello, I'm having some troubles with WoW. When I do certain things that involve loading. Like pet battle or when I die. I somethimes have my keys stuck (feels like that) I can't press any keys but I can click on them. Also when I start typing on certain keys it clears the field I'm typing in. For example I want to type /reset ui then on the "u" it clears all I've typed.
Anyone knows what is going on? I use the Catalyst drivers from AMD (got good perf) and Wine 1.7 under Ubuntu 14.04

This is probably going to sound like a broken record answer but...

kernel up to date?
What wine version (just 1.7 is a very very general answer: IE: 1.7.30 is current, vastly improved/different from 1.7.0)

And probably the most likely issue..
Have you tried using a different keyboard?
- It may sound silly, but I've had similar issues to this where certain keys were being sticky/wonky for no apparent reason and it affected other programs in different ways, replacing the keyboard was my solution.

Is the problem readily replicated? IE: 100% chance when X happens to get Y result? or is it random?

Have you tried doing a wineboot (console: wineboot -U)?
Have you tried reinstalling wine and/or changing the version installed?
When did this problem appear? Recently, or ever since you've tried running WoW in WINE?

I'm running wine 1.7.30 and linux kernel 3.13.0-32.57
It happens quite often and always after I die / Take a portal / do a pet battle/ Go into a dungeon. (So a reload/new screen)
I didn't had it on my previous laptop but this is a new one and I clean installed everything. Maybe a setting?

Possibly, but not likely, do you have another keyboard you can try using and see if you can replicate the problem? Or possibly another computer with the same distro/kernel/wine version you can try that keyboard on?

Hello,
Well it is a laptop keyboard so a bit hard to put in another laptop.
Tested out an external keyboard and that has the same. But is seems to be less after latest WoW patch. Only had it once since. What also is strange if I hit Ctrl-Space for a keybind and then press 'm' it doenst open the map but stops the music. When I hit Ctrl again and then press 'm' again it opens my map.
I don't know what is wrong... Maybe a keyboard driver issue? Or something in wine.

Pretty much sounds like what's been happening to me. Posted in reply to a bug: here bugs.winehq.org/show_bug.cgi?id=37263

Generally it forces my character to run in some weird direction non-stop. Often if this happens if you hit enter you can open up the chat and then if you start pressing random keys it will only post what the active stuck key is (generally W in my case). It may then allow you to type for 4-5 keys then it locks up again.

It happens less on 1.7 wine for me but VERY frequently on 1.6.

it sometimes happens for me also that keys dont work.. what helps is to switch workspace and then click on the wowicon to bring it up again... or alt+tab through your windows and back to wow.
its probably like its loosing focus for sec and keyboard is not grabbed anymore.

when i start World of Warcraft Launcher.exe with wine 1.7.28 it always crashes at
fixme:dbghelp:elf_search_auxv can't find symbol in module

it's only the launcher. Wow.exe does run fine, but i can't play due to an outdated realmlist. anyway, anybody got an idea how to fix this error?

same issue

You have to disable dbghelp in the winecfg library configuration

Nothing has changes except the patch yesterday, ever since then, SoO has ALOT of broken textures, floating green boxes, wooden rafters that appear green and choppy looking.

Not sure why, anyone else have this issue? The bnet app launcher repaid thing detected no problems.

Everything works fine here. Are you sure nothing else has changed, like automatic software updates, graphic driver updates?

Literally, nothing. I hadn't even rebooted my computer or anything since sun, which it was working fine then. (I did reboot to see if the problem persists, it did)

I haven't had any problems either with NVIDIA.

Quite the contrary actually. The OpenGL pipeline seems to run at least 10 FPS faster than previously. Not sure what changed.

I'd tried rebooting my comp originally, with no effect.
Over the last 3-4 days since my last raid I rebooted once and changed nothing, no problem last night.

Will attribute it to the tech-gremlins that live in my comp.

I started wow, got the game on the left screen, and the mousepointer locked to the right screen.

Gameplay using keyboard worked fine, but using the menu without mouse was not that easy.

Also the battle.net-client download a bit of data, and then pauses, if i restart it, it continues where it stoped, slowly getting more and more.

Try to switch to "Maximized Fullscreen" or "Windowed". If you can't reach the menu, you can change it in WTF/Config.wtf

SET gxWindow "1"
SET gxMaximize "1"

As for the battle.net launcher, I have this bug too. I start WoW directly using the wow-64.exe.

I recently got back into this game after 2 years and had to re-install everything. Since the re-install everything in game works great, High settings running at 90 FPS, but all of the cinematics are nothing but a green screen with the sound playing in the background. This includes all of the expansion intros as well as the in game cinematics like the wrath gate. Any Ideas whats going on?

I had this issue too. Had to log in to Windows and enable DirectX11 to get any cinematics to play :(

It appears to be due to Blizzards lack of support for opengl. Switching back to D3D9 made the cinematics work again.

Unfortunately with a new expansion coming up i don't really want to miss out on any plot related cinematic.

Will probably switch back to opengl after a few months since this makes my FPS go from about 90 at ultra settings down to 30-40 on medium-high settings. /sigh

I have the same issue but if I reenable d3d then I end up getting sound corruption for some stupid reason. not sure why but it happens.

I recently switched from the proprietary Catalyst driver to the open source radeon, and get overall better performance. I was using the opengl renderer before, but switched to the direct3d renderer as it was now faster.

most places with bad FPS before are now a lot better, but I noticed that areas where WoW reports a high FPS (50-90FPS), it does not appear as smooth as it reports and is a little stuttery. I rarely got FPS that high on Catalyst, but when I did it was definitely apparent.

is there something in my new driver configuration that could be causing this? I'm using an ATI Mobility Radeon HD 5870, tested on GNOME and LXDE.

Try this:

wiki.ixit.cz/d3d9

It's quite awesome, experimental project (which is trying to get into mainline Mesa atm). It pretty much doubled my fps in all Wine games.

GalliumNine doesn't work with Catalyst, so you need latest open source drivers and some recent kernel (3.16 and up should do, though I'd recommend 3.17.1).

debian jessie
Nvidia gtx 770

the game crashes after a while with this error:

err:seh:setup_exception_record stack overflow 1584 bytes in thread 0025 eip 7bc47688 esp 00240d00 stack 0x2400 00-0x241000-0x340000

Since patch 6.0.2 Wow crashes, it might be nvidia related. I've tried several versions of the nvidia driver including nouveau. The results are the same: Wow crashesh after a while

I'm using official NVIDIA drivers (343.22) for my geforce 660 gtx on Gentoo Linux AMD64 and I don't have any crash problem. Have you tried to remove Cache and WTF folders in your WoW directory? Have you tried to re-instal the game after deleting it completely?

I've tried several versions of the Nvidia driver. I hadn't tried deleting the Cache and WTF folders. I tried it but the game crashed again after 30 min. or so. I'm going to try a fresh install now.
Thanks for the advice.

Reinstalling the game fixed it. IIRC the previous install was from the original game disks from 2006 + all the upgrade discs.

Thanks again.

I've tried everything.
I've tried running the game in it's own xserver with no window manager, I've tried overclocking, I've tried making it's nice value 10, i've tried a fesh wineprefix, currently on wine 1.7.14, made new wineprefix, used winetricks to install JUST dx11 dlls.. Start game, still says Graphic API is DX9.

I know DX10/11 isn't fully supported in wine yet but they make it sound like alot of it should work. None of it does for me.

Mostly because of this, I am getting 5-6fps when the same settings on Win7 give me 70+. Even on lowest settings DX9 is giving me 20fps tops, openGL gives me 26 (everything is stuck on lowest settings in OpenGL aswell)

It wasn't so bad until the 6.0 update, the new character models have worsened it abit, but it was still fairly un-playable outside of non-intense small group fights indoors.

Am I the only one experiancing this? What else can i try? What are you guys fulling as far as FPS?

I'm running an NVidia 650 GT with the 340 Nvidia driver (have tried nouveau, it's even worse)
Win 7 DX11 FPS: 70-80avg
Win 7 DX9 FPS: 55-60
Wine FPS: 5(d3d) 27(OpenGL)



Amd Athlon II X2
Fedora 20 x64
8gb RAM(DDR3)
Nvidia 650 GT (1gb ddr5 RAM)
Kernel 3.14
WoW version: 6.0.2 Build: 19034 (Release x86)
Wine 1.7.14 (x86)

Try following commands before running. This helps performance wise on my nvidia card.

export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1

That actually made it alot worse..
Now i'm pulling 2-3fps.. >.>

Script I used to start game..

#!/bin/bash
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
wine "/home/Galaxy/.wine/drive_c/Program Files/World of Warcraft/Wow.exe" &

I updated to wine 1.7.29, and changed to the 64bit version, 1-3fps with threaded optimizations, 20-23 without.. >.>
Not sure why because threaded optimizations helps on most of my other games, not sure why it's making it worse for wow.

Still, 20-23 is far from the 70 I pull in windows. And this is on minimal settings, whereas windows is on ultra..

If only blizzard would get off their asses and make a linux client for us!! OpenGL is such a better graphics engine, but windows don't support it so Blizz don't care.. >.>

There is some issues with mac clients too and Blizzard already working on a fix for that. Blue post in the comments here us.battle.net/wow/en/blog/16561637/

Maybe that's related to your issue.

And are you using the official nvidia driver or nouveau?

Call
lsmod |grep nou

or

lsmod |grep nvidi

to know which is loaded.

Only the official nvidia driver gives real performance.

It DOES say in my post i'm using nvidia 340 driver and that i'd tried nouveau and had worse performance...

But thanks for you're first post, I'll give it a try and see what happens

Can't start the game in opengl mode again :(

Same.
Ubuntu 14.04, wine 1.7.31 without any lib changes.
Changing to OpenGL manually (via config file) gets me stuck on "connecting".

Entering the advance setting in game shows only D3D9 on my graphic options.

Any one knows a solution?
i get 15-25 fps which sucks... (on D3D9)

You have to start the "wow64.exe -opengl" manually. Then you can login and play in opengl mode. Use the battle.net launcher only to update WoW.

The mystery crash directly after login seems to be solved. It's because I probably started the normal wow64.exe instead of the wowB-64.exe

Everythings running fine now using opengl!

I can't seem to find WoWB-64.exe... please explain where this is. It is not in my WoW Folder.

-Thanks

It's called Wow-64.exe

WoWB was only because of the Beta.

1) I had "Unable to validate game Version" Error #112.
This is no longer an issue I believe.
Fix:

You can fix Error #112 by navigating into your Beta/WTF folder and deleting the Config.WTF file.

or

us.battle.net/wow/en/forum/topic/13020802556#14
Check config.wtf for a

SET portal "US"


2) I had problems moving/copying the beta folder. I found out that there are now hidden files, make sure you copy them:
.patch.result
.agent.db
.build.info
.build.db


3) I had problems updating the beta:
I found the fix at:
eu.battle.net/wow/en/forum/topic/11120031916?page=2#33

1. Exit Battle.net app.

2. Rename “World of Warcraft Beta” folder to “World of Warcraft Beta Copy”.

3. Run Battle.net app.

4. Hit start install on beta.

5. Before it starts installing, I change the language from “English (EU)” to “English (US)”.

6. “World of Warcraft Beta English (US)” starts to install but failed after downloading some files and I get 8A4 error code.

7. Exit Battle.net app.

8. Deleting “World of Warcraft Beta” folder.

9. Renaming “World of Warcraft Beta Copy” folder back to “World of Warcraft Beta”.

10. Run Battle.net app again.

11. It now starts to download with no errors.


4) As mentioned, running the beta with opengl meant missing walls and floors.
I just checked with updated beta and opengl. It seems to be working now (no missing walls or floors), I'm not 100% sure. I did change to SET gxApi "OpenGL" in Config.wff.



I run WowB-64.exe with:
wine "/home/USERNAME/.wine/dosdevices/c:/Program Files (x86)/World of Warcraft Beta/WowB-64.exe" -opengl

And with PlayOnLinux, wine 1.7.21

1) Worked for me after the 2nd try.
3) Is a general beta problem. I used the same workaroung.
4) In the last client update this was fixed. But my client keeps crashing after a few seconds in the game using opengl.