World of Warcraft

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.


Reply to Thread Back to Threads

Game crashes shortly after logging in?
Paul Sainsbury
Posted 2014-11-16 15:18
Hi,

I have Ubuntu 14.04.1 64 bit, Intel i5 cpu and Radeon R9 280X running the open source drivers.  I'm evaluating CrossOver as a tool to help me move over from Windows to Linux with WoW being the only real sticking point for me.

The game quite literally just closes, without giving any errors, and then the Battle.Net launcher shows that I need to "update", and after initialising for a while it doesn't actually apply any updates at all but lets me "play" again.

Any ideas what could be wrong?

From
 Paul
Alexander Tornow
Alexander Tornow Omniscient Mystical Exalted Nigh-invincible Supreme Raging Atomic Dragon Turbo Chief Senior Advocate, Rank 2
Posted 2014-11-18 16:09
Hi there,

usually we'd be using the Open Source Radeon drivers that Ubuntu provides at default, but this time around we were forced to use the proprietary default AMD Catalyst drivers provided by Ubuntu. Performance with the Open Source drivers is good and much more stable, system integration with Unity is superior and smoother too, but there is a bug with them in Ubuntu 14.04.1 64-bit. The bug is caused by a buggy LLVM and Mesa driver combination, which has yet to be fixed on this release of Ubuntu. This issue causes a lot of games to crash when using a specific combination of graphic-settings in games powered by Wine/Crossover and it also happens in games played natively - including WoW. This issue has been adressed + fixed in Ubuntu 14.10 64-bit, which ships with a new graphics stack + Mesa drivers, but performance took a major hit. I'll provide more details on this later.

Anyway, you have two options:

1. Download and install the newest Open drivers for your system via a PPA like the one from Oibaf or...

2. Activate the proprietary AMD Catalyst drivers provided by Ubuntu.

That should fix the issue.

Cheers,
Alex
Alexander Tornow
Alexander Tornow Omniscient Mystical Exalted Nigh-invincible Supreme Raging Atomic Dragon Turbo Chief Senior Advocate, Rank 2
Posted 2014-11-20 02:52
Hey Paul,

did it work? Are you able to fly around in the world of Azeroth?

For everyone else having the issue: You can analyse the situation and verify what I wrote above by using Crossover's built-in diagnostic tool when running WoW.

This is the error/bug that's currently affecting Ubuntu 14.04.1 users when using the Open Source drivers provided by Ubuntu at default:

** Fri Nov 14 12:12:39 2014
Starting '/opt/cxoffice/bin/wineloader' 'winewrapper.exe' '--new-console' '--workdir' '/home/nicole/.cxoffice/World_of_Warcraft/dosdevices/c:/Program Files/World of Warcraft' '--start' '--'
'/home/nicole/.cxoffice/World_of_Warcraft/dosdevices/../drive_c/Program Files/World of Warcraft/Wow.exe'

fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:heap:HeapSetInformation 0x1590000 0 0x33fdc8 4
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: /usr/lib/i386-linux-gnu/pkcs11/gnome-keyring-pkcs11.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden
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, 0x179e974, 0x179e970): stub
fixme:d3d11:D3D11CreateDevice stub: adapter (nil), driver_type D3D_DRIVER_TYPE_HARDWARE, swrast (nil), flags 0x1, feature_levels 0x179fac0, levels 0x3, sdk_version 7, device (nil), feature_level 0x179facc, context (nil)
fixme:win:EnumDisplayDevicesW ((null),0,0x179ecf8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ec08,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179f1f8,0x00000000), stub!
fixme:dxgi:dxgi_adapter_CheckInterfaceSupport iface 0x1475d0, guid {9b7e4c0f-342c-4106-a19f-4f2704f689f0}, umd_version (nil) stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179f0e8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179efe8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179eee8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179f5b8,0x00000000), stub!
fixme:d3d9:D3DPERF_SetOptions (0x1) : stub
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:win:EnumDisplayDevicesW ((null),0,0x179e6f8,0x00000000), stub!
fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x179fa30,0,(nil),0x68322f8,0x179fa28,0x179fa8c) stub!
fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x179fa30,0,(nil),0x68322f8,0x179fa28,0x179fa8c) stub!
ALSA lib conf.c:3314:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM default
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x6e0e998): stub
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:win:EnumDisplayDevicesW ((null),0,0x179ed38,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ec48,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ed28,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ec28,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ed28,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ec28,0x00000000), stub!
fixme:winhttp:get_system_proxy_autoconfig_url no support on this platform
fixme:win:EnumDisplayDevicesW ((null),0,0x179ef78,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ee78,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ef68,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ee68,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ef68,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x179ee68,0x00000000), stub!
fixme:imm:ImmReleaseContext (0x6004c, 0x68329c8): stub
fixme:advapi:CreateRestrictedToken (0x23dc, 0x0, 2, 0x20cbbb08, 19, 0x1238923c, 5, 0x179a4d0, 0x179a5d0): stub
fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x179a0fc,0,(nil),0x12062140,0x179a124,0x179a130) stub!
LLVM ERROR: ran out of registers during register allocation


This is the important part: LLVM ERROR: ran out of registers during register allocation

^ The game crashes at this point.

This bug currently affects all 3D applications like: Nexuiz, Xonotic, WoW, Source Engine powered games and more.

Take a look at my previous post if you want to know how to work around this issue.

Cheers,
Alex
Paul Sainsbury
Posted 2014-11-21 14:17
Apparently the forum doesn't tell me when there have been replies to my posts, so I only saw your message now. :( I will try it out soon.
Paul Sainsbury
Posted 2014-11-21 15:30
I've tried both sets of proprietary drivers, and even downloaded and installed the version from AMD's site... still no joy.

I get the error you mention though - "LLVM ERROR:  ran out of registers during register allocation"

Any ideas what else to try?

From
 Paul
Alexander Tornow
Alexander Tornow Omniscient Mystical Exalted Nigh-invincible Supreme Raging Atomic Dragon Turbo Chief Senior Advocate, Rank 2
Posted 2014-11-25 08:58
Sup mate,

are you 100% positive that the error occures with the proprietary drivers as well? I haven't heard that one before. Did you reboot your machine after switchting to the proprietary drivers via Ubuntu's built-in tool? That's a mandatory step and even though it sounds kinda weird asking this... I have seen ppl forget it. And that by itself is understandable, because Ubuntu doesn't tell you to reboot after it makes the changes.

In addition: Have you tried playing the game with "performance enhanced graphics" disabled?

A last ditch effort (use at your own risk):

If that doesn't work, you might want to try the newest Open Source drivers via the Oibaf PPA. But first make sure Ubuntu defaults back to the Open Source driver and then type in the following in a terminal:

sudo apt-add-repository ppa:oibaf/graphics-drivers && sudo apt-get update && sudo apt-get dist-upgrade


Confirm via terminal and reboot when done. Verify via Ubuntu's driver tool that the Open driver is in use.

But be careful though: This will download and install the newest (literally - daily updates) Open Source drivers for your GPU, which might be a bit unstable. You will also experience regressions sometimes. This is bleeding edge software. Also, during my testing, using the new Open Source drivers + Crossover + WoW results in an immediate freeze if performance enhanced graphics are activated. I had to disable the feature in order for WoW to run without crashing.

Let me know how it goes!

Cheers,
Alex
Alexander Tornow
Alexander Tornow Omniscient Mystical Exalted Nigh-invincible Supreme Raging Atomic Dragon Turbo Chief Senior Advocate, Rank 2
Posted 2014-11-26 06:30
Sup mate,

btw, I almost forgot; there is yet one thing that comes to mind - if everything else fails, but it would come with a bit of sacrifice from your end.

WoW in OpenGL mode

If you can't get rid of the LLVM error, running WoW in OpenGL mode (instead of D3D9) should fix the issue. BUT it will most likely come at a price:

a) Using an AMD GPU, performance in OpenGL mode is most likely going to be... not so good.

b) You will lose most of the nice graphical features that the D3D9 build can offer.

Check this out: https://www.codeweavers.com/compatibility/browse/name/?app_id=7714;forum=1;msg=169187

Still interested? Kk, open the C: drive where Crossover installed WoW into. You can do this by opening Crossover, managing your WoW bottle and by clicking on the button that offers you to open its C: drive. Once you are in there, navigate to the WoW folder, then open the WTF folder and locate the config.wtf file. Open the config.wtf file in a text editor and change the gxApi entry from D3D9 to OpenGL (i.e. SET gxApi "opengl"). Save and close the editor. Relaunch WoW now. Changing these entries will cause the game to run in OpenGL instead of DirectX mode.

If the game "hangs" at the login screen: Press "ENTER" on your keyboard two times and wait for the automated login to proceed. I don't know why this happens, but this is how I got it to login successfully.

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

Please Wait...
eyJjYXJ0IjowLCJ0enMiOi01LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNTI1ODk4MDg2fQ==