Application Details:
Version: | 6.2.4 |
License: | |
URL: | http://www.worldofwarcraft.com |
Votes: | Marked as obsolete |
Latest Rating: | Gold |
Latest Wine Version Tested: | 1.9.14 |
Maintainers: About Maintainership
What works
Everything
What does not
Nothing
Workarounds
What was not tested
Hardware tested
Graphics:
Additional Comments
DirectX 11 does not work, but both the OpenGL and DirectX 9 engines work well.
Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
Show | Gentoo Linux x86_64 | Jul 29 2016 | 1.9.14 | Yes | Yes | Gold | an anonymous user | ||
Show | Manjaro Linux | Jun 27 2016 | 1.9.12 | Yes | Yes | Platinum | Krogash86 | ||
Show | Debian GNU/Linux 8.x "Jessie" x86_64 | May 15 2016 | 1.9.9 | Yes | Yes | Platinum | an anonymous user | ||
Current | Gentoo Linux | May 11 2016 | 1.9.8 | Yes | Yes | Platinum | Kari Hazzard | ||
Show | Manjaro Linux | Apr 14 2016 | 1.9.7 | Yes | Yes | Platinum | Krogash86 |
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Candylol on Thursday January 9th 2020, 16:08
wormate-io.com/
henrystickmangames.com/
by cool kiu00 on Monday September 2nd 2019, 21:26
coolmaps.io : position the path correctly!
by Adam on Sunday June 3rd 2018, 8:37
by Colin on Sunday July 17th 2016, 21:50
I am using nvidia, if that matters. I am also using the proprietary drivers. Anyone else having issues like this?
by Valentin on Wednesday July 20th 2016, 5:54
by Gob on Friday July 22nd 2016, 21:56
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.
by Eric Neilson on Monday July 11th 2016, 23:56
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)
by kaimon on Sunday June 26th 2016, 11:01
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?
by Krogash86 on Thursday June 30th 2016, 2:19
by Krogash86 on Thursday June 30th 2016, 2:19
by kaimon on Thursday June 30th 2016, 11:08
by Atonner on Tuesday June 21st 2016, 22:57
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.
by Nathan Brooks on Friday June 17th 2016, 2:36
by Chris Rankin on Saturday June 11th 2016, 17:49
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
by DeeDee Ranged on Thursday June 16th 2016, 6:41
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
by AsciiWolf on Monday May 9th 2016, 12:58
by DeeDee Ranged on Thursday June 16th 2016, 6:49
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
by shaheen on Tuesday July 19th 2016, 14:31
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.. :(
by Kin C on Thursday March 31st 2016, 14:42
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.
by Pavel R on Friday April 8th 2016, 7:20
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.
by Metalfyre on Tuesday May 3rd 2016, 7:36
by ergo on Wednesday March 30th 2016, 5:49
by Jeremy on Thursday May 12th 2016, 16:47
by Jeremy on Thursday May 12th 2016, 17:34
by Jeremy on Thursday May 12th 2016, 18:37
by ergo on Saturday May 14th 2016, 10:35
by Jeremy on Sunday May 15th 2016, 13:56
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.
by Jeremy on Sunday May 15th 2016, 18:43
by Jeremy on Saturday May 21st 2016, 6:20
by Ryan Davis on Friday May 27th 2016, 3:55
by Jeremy on Thursday June 9th 2016, 12:00
by Jeremy on Friday June 10th 2016, 21:45
by ergo on Sunday June 12th 2016, 6:55
by Jeremy on Sunday June 12th 2016, 7:54
by Jeremy on Saturday July 2nd 2016, 6:36
by Ryan Davis on Saturday July 2nd 2016, 22:04
by Ryan Davis on Friday July 8th 2016, 3:21
> 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.
by Bigpfeff on Tuesday March 29th 2016, 12:36
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.
by Bigpfeff on Tuesday March 29th 2016, 12:37
by Bigpfeff on Tuesday March 29th 2016, 13:33
by Alberto on Tuesday March 29th 2016, 15:25
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
by D. Wilson. on Tuesday March 29th 2016, 21:06
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.
by Bigpfeff on Wednesday March 30th 2016, 4:35
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
by Alberto on Wednesday March 30th 2016, 8:57
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
by Bigpfeff on Wednesday March 30th 2016, 12:44
Thanks to all
by shawn on Sunday March 27th 2016, 10:58
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
by David Eriksson on Sunday March 27th 2016, 14:04
by shawn on Sunday March 27th 2016, 18:46
by Kin C on Sunday March 27th 2016, 10:02
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?
by Alberto on Sunday March 27th 2016, 10:42
us.battle.net/wow/en/forum/topic/20742995286
Especially the section Issue #2 Update Method for Ubuntu
by Kin C on Monday March 28th 2016, 4:20
by Alberto on Monday March 28th 2016, 4:24
by Kin C on Monday March 28th 2016, 8:32
by Webxorcist on Sunday March 27th 2016, 7:44
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.
by Webxorcist on Sunday March 27th 2016, 7:58
by Feldspar on Wednesday March 30th 2016, 20:18
/cheers
OpenSUSE Leap 42.1 (64)
Using authenticator
by Alberto on Friday March 25th 2016, 17:25
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
by Alberto on Saturday March 26th 2016, 6:43
I switched to winesnapshot and with build 1.9.6.20160325.1435-1.1, WoW works again with openSUSE Leap 42.1.
Regards
by Webxorcist on Sunday March 27th 2016, 5:01
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 :)
by Alberto on Sunday March 27th 2016, 5:43
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
by Webxorcist on Sunday March 27th 2016, 6:48
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.
by Alberto on Sunday March 27th 2016, 6:53
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.
by Webxorcist on Sunday March 27th 2016, 6:56
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?
by Alberto on Sunday March 27th 2016, 7:04
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
by Webxorcist on Sunday March 27th 2016, 7:07
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?
by Alberto on Sunday March 27th 2016, 7:12
Don't need anything in /usr/local/lib. My directory is empty.
Make install only copy to /usr/local/lib64.
Regards
by Webxorcist on Sunday March 27th 2016, 7:27
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!!
by Chris Boyle on Friday March 25th 2016, 9:55
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.
by Chris Boyle on Friday March 25th 2016, 9:56
by Rafael Henrique da Silva Correia on Friday March 25th 2016, 12:54
* 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!
by Marek Toman on Saturday March 26th 2016, 2:20
I can confirm WoW again running on Xubuntu 14.04 x64.
by Matt Spraggs on Sunday March 27th 2016, 9:20
by kaimon on Tuesday March 29th 2016, 23:43
by kaimon on Thursday April 7th 2016, 12:33
by Alexander on Friday March 25th 2016, 6:12
by Alexander on Friday March 25th 2016, 6:23
by Cory on Saturday March 26th 2016, 11:29
# 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
by Jon on Thursday March 24th 2016, 21:19
by Jon on Thursday March 24th 2016, 21:18
by Doug Bailey on Thursday March 24th 2016, 15:10
by Kari Hazzard on Thursday March 24th 2016, 18:02
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
by Jon on Thursday March 24th 2016, 19:47
by Scott Simpson on Thursday March 24th 2016, 20:23
by Doug Bailey on Thursday March 24th 2016, 21:25
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.
by Alberto on Friday March 25th 2016, 5:10
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
by Marek Toman on Thursday March 24th 2016, 6:19
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".
by yt on Thursday March 24th 2016, 6:30
Did you tried to deleted the /home/$USER/.wine/drive_c/users/$USER/Application Data/Battle.net/ directory while testing the new kernel?
by yt on Thursday March 24th 2016, 0:08
by yt on Thursday March 24th 2016, 0:09
by Humphrey on Thursday March 24th 2016, 3:28
by yt on Thursday March 24th 2016, 4:34
by Humphrey on Thursday March 24th 2016, 4:49
by Bryguy on Tuesday March 22nd 2016, 19:51
by Doug Bailey on Tuesday March 22nd 2016, 20:18
by Azathoth on Wednesday March 23rd 2016, 5:16
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.
by Kari Hazzard on Wednesday March 23rd 2016, 8:25
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.
by Azathoth on Wednesday March 23rd 2016, 18:30
by Kari Hazzard on Wednesday March 23rd 2016, 23:15
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.
by Juergen on Wednesday March 23rd 2016, 5:30
- Debian 8 - Jessie
- Wine-version: wine-1.9.2 (staging)
by bas70 on Wednesday March 23rd 2016, 13:35
Could it be that blizzard is banning linux for some reason?
by Andrew on Wednesday March 23rd 2016, 6:02
Ubuntu 14.04
Wine 1.9.2
by Kevin Grittner on Wednesday March 23rd 2016, 8:29
Ubuntu 14.04 LTS
Wine 1.8.0
Failure started with WoW Version 6.2.4; game currently unusable.
by gwnull on Wednesday March 23rd 2016, 10:44
by yt on Wednesday March 23rd 2016, 13:16
by Scott Simpson on Wednesday March 23rd 2016, 13:19
by yt on Wednesday March 23rd 2016, 13:43
by yt on Wednesday March 23rd 2016, 13:59
"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?
by Kari Hazzard on Wednesday March 23rd 2016, 14:04
by yt on Friday March 25th 2016, 0:57
by Erick on Thursday March 24th 2016, 10:47
by Alberto on Thursday March 24th 2016, 11:14
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/
by yt on Thursday March 24th 2016, 11:55
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.
by samual hunt on Saturday April 23rd 2016, 3:03
by Bill on Wednesday March 16th 2016, 8:08
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.
by Cindi Clinton on Monday February 15th 2016, 6:43
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!
by hirschhornsalz on Monday February 15th 2016, 7:27
by Rico on Thursday March 24th 2016, 1:58
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
by shawn on Thursday March 24th 2016, 16:39
by shawn on Thursday March 24th 2016, 16:59
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.
by Tigs on Friday March 25th 2016, 6:54
by shawn on Saturday March 26th 2016, 18:03
by Brad on Wednesday January 20th 2016, 19:00
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...
by DeeDee Ranged on Thursday January 21st 2016, 16:10
Running Debian jessie with wine 1.9.1 with bumblebee/optirun.
by Colin on Friday January 22nd 2016, 18:05
by Josh Raymond on Wednesday January 27th 2016, 21:57
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.
by Bill on Sunday January 31st 2016, 17:46
However I get the same error he mentions so I am not sure how others have gotten it to work :-/
by Bill on Sunday January 31st 2016, 21:15
Found the Information here: bugs.winehq.org/show_bug.cgi?id=39985
by Ryan Davis on Saturday February 6th 2016, 20:27
by Danilo Riffo on Monday March 7th 2016, 18:44
by Ian on Tuesday February 2nd 2016, 17:20
by Matt Spraggs on Wednesday January 6th 2016, 12:02
by Ryan Davis on Sunday December 6th 2015, 11:53
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.
by Sick on Tuesday December 8th 2015, 8:28
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)
by Matt Spraggs on Sunday November 29th 2015, 16:53
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.
by Ryan Davis on Wednesday December 9th 2015, 18:04
by Matt Spraggs on Saturday December 12th 2015, 18:58
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!
by Oleh on Thursday November 5th 2015, 14:07
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?
by Guti on Friday March 25th 2016, 13:12
MESA_GL_VERSION_OVERRIDE=3.3COMPAT
export MESA_GL_VERSION_OVERRIDE
by jazz on Wednesday November 4th 2015, 20:22
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.
by Alberto on Saturday November 7th 2015, 7:05
If yes, I have this problem a lot time ago with kmixer and Alsa or Pulseaudio. Other mixers don't resolve the problem.
by Cory on Saturday September 19th 2015, 17:59
"run winecfg and “disable†the “d3d11†dll in library tab."
by Josh Raymond on Friday October 2nd 2015, 12:26
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"
by Cory on Wednesday September 16th 2015, 20:33
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
by Scott on Thursday September 17th 2015, 20:19
appdb.winehq.org/commentview.php?iAppId=1922&iVersionId=32314&iThreadId=95436#Comment-95466
by Cory on Saturday September 19th 2015, 18:01
"run winecfg and “disable†the “d3d11†dll in library tab."
OpenGL still fails as usual.
by Matthew Tivnan on Tuesday September 8th 2015, 17:52
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.
by Alexander on Saturday September 12th 2015, 6:17
"The instruction at '0xf701946e' referenced memory at '0x00000000'. The memory could not be 'written'". Have you any workaround?
by Matthew Tivnan on Saturday September 12th 2015, 8:09
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.
by Scott on Saturday September 12th 2015, 18:24
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.
by Alexander on Sunday September 13th 2015, 3:19
It's work for me too, thanks.
by Thilo Cestonaro on Thursday September 3rd 2015, 10:59
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
by Thilo Cestonaro on Thursday September 3rd 2015, 10:59
by Scott on Saturday September 12th 2015, 18:26
by Scot on Wednesday September 30th 2015, 19:24
by Fish on Wednesday September 2nd 2015, 6:36
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?
by Wayne on Wednesday September 2nd 2015, 18:18
by Fish on Thursday September 3rd 2015, 2:11
by Arthur Ice on Thursday September 3rd 2015, 12:01
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)
by Merlin@34 on Sunday August 30th 2015, 11:52
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
by Merlin@34 on Sunday August 30th 2015, 11:54
by Alex on Friday August 28th 2015, 9:59
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.
by Wobbo on Friday August 28th 2015, 1:53
(Diablo works as before. StartCraft II has the same problems as before, it runs, blizzard-bug after exit.)
by Wobbo on Friday August 28th 2015, 1:54
by William Panlener on Monday August 24th 2015, 20:24
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.
by Manuel Bernardo Ibáñez Ocampo on Tuesday August 25th 2015, 15:23
by Alberto on Tuesday August 25th 2015, 19:04
Regards
by Manuel Bernardo Ibáñez Ocampo on Wednesday August 26th 2015, 13:41
by Stefano on Wednesday August 26th 2015, 13:39
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
by Manuel Bernardo Ibáñez Ocampo on Wednesday August 26th 2015, 14:08
i reinstall the 1.7.50 version, disable d3d11 and it works fine again, thanks a lot
by William Panlener on Wednesday August 26th 2015, 15:47
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.
by Marek Toman on Tuesday August 11th 2015, 23:06
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."
by Mattis on Tuesday September 8th 2015, 18:48
Thanks a lot!!
by Alexander T. on Sunday September 13th 2015, 12:52
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
by Josh Hertlein on Monday November 23rd 2015, 22:53
MESA_GL_VERSION_OVERRIDE=3.3COMPAT WINEDEBUG=-all wine "Wow-64.exe" -opengl
Successfully launches WoW for me.
by Nemanja Janic on Monday December 21st 2015, 5:26
by Timo on Tuesday July 21st 2015, 9:29
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. :/
by hirschhornsalz on Tuesday July 21st 2015, 10:55
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.
by Timo on Tuesday July 21st 2015, 11:46
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.
by Chris Rankin on Tuesday August 11th 2015, 15:23
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
by Chris Rankin on Tuesday August 11th 2015, 15:10
by Chris Rankin on Tuesday July 14th 2015, 16:38
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
by Fred on Wednesday July 15th 2015, 2:46
It works fine if you change the OS to Windows XP.
by Chris Rankin on Wednesday July 15th 2015, 17:47
bugs.winehq.org/show_bug.cgi?id=38845
Disabling d3dcompiler_46.dll in winecfg allows me to keep Wine configured as Windows 7.
by Alex on Tuesday July 14th 2015, 4:26
by Daz on Sunday July 12th 2015, 15:23
by Steve on Sunday July 12th 2015, 23:06
by harley on Sunday July 5th 2015, 16:50
by Brad on Thursday July 2nd 2015, 18:02
by Matt Spraggs on Saturday August 8th 2015, 17:12
by Matt Spraggs on Saturday August 8th 2015, 18:02
Don't know if it's any help.
by Brad on Sunday August 9th 2015, 17:21
by Michel Blanchet on Tuesday September 8th 2015, 22:18
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
by Steve on Tuesday June 30th 2015, 17:02
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!
by Fred on Saturday July 11th 2015, 17:06
err:ntdll:RtlpWaitForCriticalSection section 0x100a8 "heap.c: main process heap section" wait timed out in thread 0009, blocked by 0015, retrying (60 sec)
by Fred on Sunday July 12th 2015, 5:01
I couldn't try wine staging 1.4.47 yet. I'll report back if I run into any problems.
by Chris Rankin on Sunday June 28th 2015, 18:12
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.
by Chris Rankin on Tuesday August 11th 2015, 15:07
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.
by Alex on Tuesday June 23rd 2015, 13:37
by Alex on Tuesday June 23rd 2015, 13:48
by Alex on Tuesday June 23rd 2015, 14:12
by Alex on Wednesday June 17th 2015, 7:20
by Timothy Redaelli on Tuesday May 19th 2015, 3:42
does anyone else received a 6 month ban and the only "strange" think done was using Wine to play World of Warcraft?
by Elckerlijc on Tuesday May 19th 2015, 11:54
by William on Sunday May 24th 2015, 6:27
by jazz on Wednesday November 4th 2015, 20:14
by Kyle Kuntz on Tuesday May 19th 2015, 2:51
by Bryguy on Monday May 18th 2015, 20:37
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?
by William on Sunday May 24th 2015, 6:31
by William on Sunday May 17th 2015, 4:00
by Chris Rankin on Sunday May 24th 2015, 18:19
by Malstrond on Saturday June 27th 2015, 5:26
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.
by diego on Monday April 13th 2015, 9:14
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
by Dif on Saturday April 11th 2015, 5:35
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.
by diego on Monday April 13th 2015, 7:04
by Fred on Monday April 13th 2015, 7:17
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.
by diego on Monday April 13th 2015, 8:06
by Fred on Monday April 13th 2015, 9:00
by diego on Monday April 13th 2015, 9:15
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
by Fred on Monday April 13th 2015, 9:21
Seems like __GL_THREADED_OPTIMIZATIONS=1 was the culprit. Does it still crash?
by Dif on Tuesday April 14th 2015, 14:20
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).
by Dif on Tuesday April 14th 2015, 15:50
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).
by Dif on Tuesday April 14th 2015, 15:54
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).
by diego on Thursday April 16th 2015, 10:39
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
by ceric35 on Tuesday April 21st 2015, 13:41
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.
by ceric35 on Tuesday April 28th 2015, 14:08
I now got no freeze since a while with:
WINEARCH=win32 wine .wine/drive_c/Program\ Files/World\ of\ Warcraft/Wow.exe -opengl
by William on Tuesday May 26th 2015, 2:54
by Chris Rankin on Tuesday May 5th 2015, 15:40
This bug has been infuriating me ever since Fedora "upgraded" to Wine 1.7.41.
by Kristian Wedmark on Monday March 2nd 2015, 10:10
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:
by Chris Rankin on Sunday March 1st 2015, 15:57
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.
by diego on Saturday February 28th 2015, 3:35
if we have a hope that Linux will become the first choice of people gaming is a key part of this hope ....
by Kristian Wedmark on Sunday March 1st 2015, 11:32
by Chris Rankin on Sunday March 1st 2015, 15:35
by diego on Monday March 2nd 2015, 5:48
sorry my english is bad.
by Kristian Wedmark on Monday March 2nd 2015, 10:06
by Chris on Sunday February 1st 2015, 17:49
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.
by Knusper on Monday February 2nd 2015, 8:22
Dont use SET processAffinityMask "1"
by Knusper on Monday February 2nd 2015, 8:25
The cvar should do nothing anymore ...for years
by hirschhornsalz on Monday February 2nd 2015, 8:42
I use a value of 3, which confines WoW to the first 2 cores, to get slightly higher and more stable fps.
by Chris on Monday February 2nd 2015, 22:00
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.
by Knusper on Monday February 2nd 2015, 22:06
by Mute on Wednesday January 28th 2015, 15:05
by Chris on Sunday February 1st 2015, 17:56
by turgut kalfaoglu on Thursday January 15th 2015, 11:18
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.
by Knusper on Thursday January 15th 2015, 13:49
by turgut kalfaoglu on Thursday January 15th 2015, 15:41
by Knusper on Thursday January 15th 2015, 15:47
by Angus on Sunday January 11th 2015, 15:04
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
by Knusper on Monday January 12th 2015, 7:09
Affter that everything should work
by Guy Fleming on Wednesday December 31st 2014, 12:15
by cg on Monday December 29th 2014, 4:36
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
by Chris on Sunday February 1st 2015, 18:04
by Genericxx on Tuesday December 23rd 2014, 2:29
by Knusper on Tuesday December 23rd 2014, 10:34
by Genericxx on Tuesday December 23rd 2014, 11:05
by Knusper on Tuesday December 23rd 2014, 12:27
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
by Jens on Tuesday December 23rd 2014, 12:55
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
by Knusper on Tuesday December 23rd 2014, 18:18
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
by Genericxx on Saturday December 27th 2014, 2:47
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.
by Vladimir Olegshenko on Saturday December 20th 2014, 6:14
by Knusper on Saturday December 20th 2014, 11:02
by Vladimir Olegshenko on Sunday December 21st 2014, 1:02
by Vladimir Olegshenko on Saturday December 20th 2014, 4:59
by hirschhornsalz on Saturday December 20th 2014, 5:58
Do you have the latest wine?
Or try the latest battle.net app from us.battle.net/en/app/
by Vladimir Olegshenko on Friday December 19th 2014, 2:53
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.
by Xpander on Friday December 19th 2014, 7:42
by Björn Bidar on Friday December 12th 2014, 8:17
Do you have any logs about the memory leak and may report them to stefan?
by Xpander on Friday December 19th 2014, 7:41
by Björn Bidar on Friday December 12th 2014, 1:12
For me csmt is faster the nvidia extension.
by Xpander on Friday December 12th 2014, 5:39
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
by Björn Bidar on Wednesday December 10th 2014, 12:15
Using wine 1.7.31-csmt with multimedia patch applied.
by Xpander on Thursday December 11th 2014, 6:53
by Steven Wilson on Thursday December 11th 2014, 19:13
by Xpander on Friday December 12th 2014, 5:42
export __GL_THREADED_OPTIMIZATIONS=1
thats what i have before i launch my wow.
my entire script: pastebin.com/i2MjWnFJ
by Björn Bidar on Friday December 12th 2014, 8:19
by Steven Wilson on Saturday December 13th 2014, 0:06
by Steven Wilson on Thursday December 11th 2014, 13:39
by Dif on Tuesday March 31st 2015, 10:26
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.
by Dif on Tuesday March 31st 2015, 10:26
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.
by Barsoianu Radu on Saturday November 29th 2014, 5:18
by Clif on Saturday November 29th 2014, 12:13
by gutigen on Thursday December 11th 2014, 6:16
by Knusper on Sunday November 30th 2014, 15:14
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
by Barsoianu Radu on Tuesday December 2nd 2014, 8:22
by Simon on Tuesday December 2nd 2014, 18:44
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.
by Barsoianu Radu on Wednesday December 3rd 2014, 0:09
by hirschhornsalz on Wednesday December 3rd 2014, 3:12
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.
by Barsoianu Radu on Wednesday December 3rd 2014, 4:01
by Simon on Wednesday December 3rd 2014, 20:19
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.
by Barsoianu Radu on Thursday December 4th 2014, 2:40
by gutigen on Thursday December 11th 2014, 6:15
www.reddit.com/r/pcmasterrace/wiki/guide
by Barsoianu Radu on Tuesday November 25th 2014, 4:17
by Knusper on Sunday November 30th 2014, 15:15
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
by Gregor Kališnik on Wednesday November 12th 2014, 14:16
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.
by Corazin on Thursday November 13th 2014, 21:06
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.
by hirschhornsalz on Friday November 14th 2014, 3:19
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.
by Corazin on Saturday November 15th 2014, 2:53
by hirschhornsalz on Saturday November 15th 2014, 5:52
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.
by gutigen on Thursday December 11th 2014, 11:38
Try running WoW with `vblank_mode=0`.
by Brollie on Sunday November 9th 2014, 12:28
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?
by Brollie on Sunday November 9th 2014, 12:29
by hirschhornsalz on Wednesday November 12th 2014, 6:53
But if the stutter is very regular, an addon could be the cause. Also try to switch off yxour compositing manager.
by Brollie on Wednesday November 12th 2014, 7:46
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)
by Brollie on Wednesday November 12th 2014, 7:46
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)
by Alex on Friday November 7th 2014, 8:25
by Jens on Friday November 7th 2014, 8:42
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.
by Nevin on Monday November 3rd 2014, 14:27
by Crocky on Monday November 3rd 2014, 2:01
Anyone knows what is going on? I use the Catalyst drivers from AMD (got good perf) and Wine 1.7 under Ubuntu 14.04
by Josh Raymond on Monday November 3rd 2014, 7:48
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?
by Crocky on Monday November 3rd 2014, 8:26
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?
by Josh Raymond on Tuesday November 4th 2014, 9:36
by Crocky on Wednesday November 5th 2014, 1:29
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.
by SirMoo on Monday November 17th 2014, 22:52
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.
by Xpander on Thursday December 11th 2014, 7:16
its probably like its loosing focus for sec and keyboard is not grabbed anymore.
by Tigs on Saturday November 1st 2014, 8:37
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?
by Owen Jiang on Wednesday November 5th 2014, 6:46
by Jens on Wednesday November 5th 2014, 7:17
by Josh Raymond on Wednesday October 29th 2014, 22:04
Not sure why, anyone else have this issue? The bnet app launcher repaid thing detected no problems.
by Jens on Thursday October 30th 2014, 2:12
by Josh Raymond on Thursday October 30th 2014, 6:46
by Fred on Friday October 31st 2014, 6:01
Quite the contrary actually. The OpenGL pipeline seems to run at least 10 FPS faster than previously. Not sure what changed.
by Josh Raymond on Monday November 3rd 2014, 7:43
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.
by Puggan on Tuesday October 28th 2014, 4:49
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.
by hirschhornsalz on Tuesday October 28th 2014, 5:01
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.
by Brian McCarthy on Monday October 27th 2014, 9:17
by pete on Saturday November 1st 2014, 10:18
by Brian McCarthy on Monday November 3rd 2014, 21:43
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
by gotsanity on Tuesday November 18th 2014, 21:01
by Paula Breton on Wednesday October 22nd 2014, 2:44
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.
by gutigen on Tuesday October 28th 2014, 8:29
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).
by bas70 on Sunday October 19th 2014, 8:56
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
by bas70 on Sunday October 19th 2014, 7:26
by Elckerlijc on Sunday October 19th 2014, 12:01
by bas70 on Sunday October 19th 2014, 13:06
Thanks for the advice.
by bas70 on Monday October 20th 2014, 14:04
Thanks again.
by Josh Raymond on Friday October 17th 2014, 13:29
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)
by Jens on Friday October 17th 2014, 13:32
export LD_PRELOAD="libpthread.so.0 libGL.so.1"
export __GL_THREADED_OPTIMIZATIONS=1
by Josh Raymond on Friday October 17th 2014, 13:58
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" &
by Josh Raymond on Friday October 17th 2014, 14:34
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.. >.>
by Jens on Friday October 31st 2014, 7:45
Maybe that's related to your issue.
by Jens on Friday October 17th 2014, 13:35
Call
lsmod |grep nou
or
lsmod |grep nvidi
to know which is loaded.
Only the official nvidia driver gives real performance.
by Josh Raymond on Friday October 17th 2014, 13:43
But thanks for you're first post, I'll give it a try and see what happens
by Jens on Friday July 18th 2014, 13:21
by Matan Drory on Friday November 28th 2014, 12:00
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)
by Jens on Saturday November 29th 2014, 2:42
by Jens on Tuesday July 8th 2014, 11:32
Everythings running fine now using opengl!
by Charles Towns on Thursday October 23rd 2014, 23:37
-Thanks
by Jens on Thursday October 23rd 2014, 23:39
WoWB was only because of the Beta.
by zerohed on Monday July 7th 2014, 7:58
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
by Jens on Monday July 7th 2014, 8:51
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.