World Of Warcraft Support UPDATED 2016 Edition

Message

eccerr0r · Post by **eccerr0r** » Tue Jul 23, 2024 5:51 pm

War Within (11.0) prepatch drops today!

Was able to patch, now waiting for 3:00PDT for whether wine will still run it...as well as my old video cards.

Will see if War Within works with my last known working graphics processors:

- Haswell (HD 4400)
- Skylake (HD 520) -- seems to hang in DX12 in dungeons, DX11 seems to work but some things seem drawn/animated wrong.
- ATI R7-250 (GCN1) -- seeing artifacts on some features, only can run DX11
- ATI W2100 (GCN1) -- suspecting similar to R7-250...
- Nvidia GTX660 (though this card is broken... I don't have any good working nvidia cards...)

-----------------

Weird. Before this patch I never had WoW hang (frozen screen) for a long time. However on both the Skylake and R7-250 the screen hangs and I have to close the window and restart WoW. Of course I get kicked from the dungeon. Anyone else seeing this? Because of the two different architectures it probably is a Wine issue.

I'm trying to build Wine 9.13 now, did not have luck running WoW with wine 9.3 to 9.7 ...wonder if this is any better now.

eccerr0r · Post by **eccerr0r** » Thu Aug 15, 2024 7:06 am

Woah WTF.

Anyone run into this: I've had Wow.exe use up 33GiB RAM. My 24GiB and 20GiB machines started swapping!!!

Code: Select all

    PID USER      NI    VIRT    RES   SWAP S nTH  %CPU P vMj   TIME COMMAND     
   3264 user       0   36.0g  21.7g   8.8g S  66  50.2 0  19 175:01 Wow.exe

This is with 11.0.2 after a while of being logged in...

This is reminiscent of when WoW passed the 2GiB barrier and crashed when it ran out of VM. But this is ridiculous using 33GiB RAM. This is new behavior and hopefully it's not a new memory leak.

Note that WoW:The War Within states even recommended memory is 16GiB and minimum of 8GiB. So this very weird. I see this behavior in both wine8 and wine9 (staging)...

BTW my guess as to what happened is that I was at the boss fights for the prerelease patch and well, there are a lot of people there. Each of those armor textures needed to be loaded. I suspect WoW is not freeing textures not seen recently and probably assuming that swap will handle discarding of textures not needed instead of reloading as needed. Once again depending on OS to handle memory!

---

The War Within fully launched, and performance is about the same as the prepatch. Having frame rate drops in the outside world near Hallowfall as well as some highly active scenery, which is not unexpected for the ancient r7-250.

Seems wine-staging-9.13 works on the machine I was having trouble with 9.3 and 9.7. Finally getting off of wine-staging-8.21 ...

eccerr0r · Post by **eccerr0r** » Mon Jan 20, 2025 1:35 am

Looks like Blizzard and their wine-unfriendly battle.net app strikes again. Got BLZBNTAGT00000840 while trying to update.

https://us.forums.blizzard.com/en/blizz ... 0840/53536

eccerr0r · Post by **eccerr0r** » Wed Feb 26, 2025 1:58 am

Hooray 11.1 dropped today and wine-staging 9.19 SIGSEGV's on WoW... sigh...

Aiken · Post by **Aiken** » Wed Feb 26, 2025 3:46 am

This won't help if you want to use a locally compiled wine. After a previous time when blizzard broke wow with wine and wine-staging I used lutirs to download wine-ge-8-26-x86_64 and copied that /opt/lutris/ so any user could access it. Back when WINE_SIMULATE_WRITECOPY=1 was needed to start the game.

I had been checking out a couple of things on the ptr and just now logged into retail with that version from lutirs is still working for me. Trying wine-staging again is on the todo list but it keeps slipping down the list.

eccerr0r · Post by **eccerr0r** » Wed Feb 26, 2025 3:58 am

Upgraded to wine-staging-10.1 ... seems to work now.
Sheesh. Always finding a way to break wine, intentionally or not...

eccerr0r · Post by **eccerr0r** » Sun Mar 16, 2025 7:35 am

Anyone got WoW working on DX12 ?

I have "DX12" 11_1 featureset cards which don't work (drawing errors)... and I just got a 12_0 featureset card which instantly segfault crashes if I enable DX12. Wonder what wine support is like for DX12 at the moment?

eccerr0r · Post by **eccerr0r** » Thu Jan 22, 2026 9:32 am

Well, not sure what's going on but my nvidia-driver machines won't b.net client properly but ATI/Intel boxes work. So patch with the ATI/Intel boxes and rsync to the nvidia box...

And the 12.0 Midnight prepatch dropped Tuesday and it seems it works okay, about the same as before though it seems to use more RAM. Install is now up to 142GB ... well, it dropped to 137GB after a cleanup patch, but regardless probably my 180GB SSDs are now too small for Linux + WoW.

eccerr0r · Post by **eccerr0r** » Tue Feb 03, 2026 9:08 pm

New copy of Battle.net came and...broke again once more:

battle.net client wrote:Battle.net Update Agent went to sleep. Attempting to wake it up...
More help: BLZBNTBNA00000005

So back to no working battle.net clients on any machine... anyone got it working, maybe I have a fluke? Well I do have a Fluke 77 and it's one of my better meters, just doesn't help here...

Aiken · Post by **Aiken** » Tue Feb 03, 2026 9:27 pm

Just updated and it worked but there was a complaint about failing to make a file writable while updating something to do with midnight. 2nd attempt at updating worked. Had a few problems with battlenet + updates + file permissions in recent months. Including one where permission for the directory for wow was set to 000.

Using wine staging 10.19. Stayed at that because 10.20 broke gw2 for me. Have not tried 11.x yet.

My fluke is also a 77.

eccerr0r · Post by **eccerr0r** » Wed Feb 04, 2026 1:16 am

I was able to pick up the patch and it then had the button to restart battle.net, and subsequent that it's never worked again...

Oh, this is with wine-staging-10.20 (and 10.1 but that dropped off portage.)

Aiken · Post by **Aiken** » Wed Feb 04, 2026 2:23 am

I do not remember if I tried 10.20 with battlenet and wow. When gw2 failed to launch immediately went back to 10.19. Just changed to staging 11.1 and both games run. Stayed in wow long enough to see fps looked normal and I could move.

When I find a working wine vanilla and staging I copy them to a local overlay so when a newer version fails, reverting to the last working version is easy.

eccerr0r · Post by **eccerr0r** » Wed Feb 04, 2026 3:10 am

interesting, for the most part all the wine-stagings (and occasionally wine-vanilla), wow has run fine, just battle.net is the issue. Sometimes I can stay at a version of wine and later on (like now) battle.net stops working...

Since battle.net failed me after today's patch, both 10.1 and 10.20 with the same issue, this is very weird...

- Tried wiping $WINEPREFIX/drive_c/ProgramData/*Battle.net* and blizzard stuff... no dice.

Incidentally there is an Agent.exe that's running despite the battle.net gui saying otherwise... hum. It also seems to be the wow agent versus the battle.net agent, perhaps? Or is agent used for updating both?

eccerr0r · Post by **eccerr0r** » Wed Feb 11, 2026 6:38 am

Supposedly the final binary for Midnight came out today (versus the prepatch that came out last week). Battle.net appears to download the patch if I login to b.net versus just continuing without logging in. Was able to get it running on my Intel iGPU (HD 520) and ATI (GCN1) but could not login on my nVidia (Pascal) GPU. Appears to be a missing library function of sorts. Don't have other details other than it crashes when trying to login a character (on the loading screen)... Wine-Staging-10.20 on Intel and nvidia machines, wine-staging-10.7 on ATI.

Another observation... WoW now uses 8GB or so RAM while running - it actually loads that much crap into RAM. So my 8GiB machines are going to swap like crazy. Fortunately most of my machines that I'd consider running WoW on (that have the GPUs) have 16GiB or more so that's okay, alas, the 16GiB machine is DDR4 and we all know what happened to DDR4 prices recently...

It is a bit unfortunate that my 64GiB machine has the nonworking nvidia solution. Looks like error is occuring in wined3d.dll...

Code: Select all

Exception: ACCESS_VIOLATION - The instruction at "0x00007fffff845f48" referenced memory at "0xffffffffffffffff".
ACCESS_VIOLATION - The instruction at "0x00007fffff845f48" referenced memory at "0xffffffffffffffff".
The memory could not be "read".
(DBG-OPTIONS<FunctionsOnly SingleLine> DBG-ADDR<00007fffff83ed1d>("wined3d.dll") <- DBG-ADDR<0000000142cd3a87>("Wow.exe") <- DBG-ADDR<00000001419fe295>("Wow.exe") DBG-OPTIONS<>)
<:Exception.Summary>
<Exception.Assertion:>
DBG-ADDR<00007fffff83ed1d>("wined3d.dll")
DBG-ADDR<0000000142cd3a87>("Wow.exe")
DBG-ADDR<00000001419fe295>("Wow.exe")

eccerr0r · Post by **eccerr0r** » Sun Feb 22, 2026 4:24 pm

Has anyone been able to run Midnight on an nvidia gpu? It was working on TWW but the initial Midnight version, it stopped working.

Tried on my Maxwell laptop with nvidia-drivers and also failed though with different behavior than the Pascal -- kept hanging when logging in or after logging in... Switching to the integrated intel gpu, it works fine.

mega_flow · Post by **mega_flow** » Sun Feb 22, 2026 7:57 pm

eccerr0r wrote:Has anyone been able to run Midnight on an nvidia gpu? It was working on TWW but the initial Midnight version, it stopped working.

Tried on my Maxwell laptop with nvidia-drivers and also failed though with different behavior than the Pascal -- kept hanging when logging in or after logging in... Switching to the integrated intel gpu, it works fine.

Run fine on mij laptop with a RTX 4070
but i run battle.net and wow with steam and proton 10.4 (flatpak and native works ok). only some sound issue and steamwebhelper eating ram
O and on gnome wow final runs back fullscreen when starting the game

eccerr0r · Post by **eccerr0r** » Tue Feb 24, 2026 12:13 am

interesting, okay. I'm using in-portage wine-staging (multiple versions), without USE=wow64 (classic i.e., multilib).

Can't say for my nvidia machines, but no sound issues when running on other boxes afaik. I only run windowed mode but maybe I need to use fullscreen so I don't misclick another window ...

eccerr0r · Post by **eccerr0r** » Sun Mar 01, 2026 8:59 am

Okay... I found that forcing

Code: Select all

wine Wow.exe -d3d11

seems to stop the crashing, using

Code: Select all

wine Wow.exe -d3d12

will crash just after logging in a character into the game... specifically for the nvidia cards (pascal and maxwell). Possible my other cards are automatically using DX11 as well (due to 11_1 featureset) but not sure... thought my intel was 12_0.