Love how manipulative Blizzard is in marking a solution in my old topic that i never marked, and is nothing but a lie, i marked an post that proofs i am not alone with issue, and they provide to apply censorship and completely ignore issue for 510+ days now.
Im all for doing an class action lawsuit to get everyone refunded at this point, since they will not listen.
You are literally rambling at this point with demands of compensation and threats of lawsuit. Everybody and their moms know
nothing like this will happen and it is not helping in general.
If been having issues for 510+ days, they arenāt gonna fix this, they will ignore it just like they ignored me, i am not having another issue its all related.
I have the right to speak up when AMD and Blizzard ignore me, if they do not like it they can go fix the issue, i will complain complain and keep on complaining, until its fixed or until i give up which is what i decide when to do.
510+ days is way to long to address issue which gives me the right to ask for compensation, anyone affected by this issue has that right as well, they had enough chances to fix this.
They did not listen when i complained, they did not listen when some one else complained, and now this is still ongoing.
Seriously what the hell AMD and Blizzard stop pointing your users back and forward and fix the issue.
Let him cook!
Hello I followed your guide on this link https://github.com/taylorsay13/WoW-AMD-Fix/wiki, but the game crashes all the time saying its out of memory, is it normal ?
Works fine on my PC. Try to do a file system check(DISM / SFC) and/or a scan and repair on the game.
Does anyone have access to TWW alpha? If so, can you try DX12 and see if the issue is fixed?
ok so i did a scan and repair my windows and i repaired the game as well and i still got the same crash saying āAccess violation, the memory could not be readā iāve seen a lot of people having this issue using dxvk on wine but i dont know how to fix it on windows (i have no problems with dxvk on any other game)
Only thing I can suggest is try reinstalling GPU drivers. It is not an error I have ever had and of course DXVK on windows WoW players are quite a niche subset of people so there is not much online about it.
I have already done it, unfortunately thatās not working. Some people on wine forums are saying that addons could be the problem, so I have to try a fresh install of my game and test it without addons.
Vulkan uses more vram, their been reports of Intel having issues as well on those system you get out of vram errors as well reported by NVIDIA users, i think one of the big YouTubers talked about it worth a look.
Also worth it is to raise your voice on the r/AMD driver thread for 24.4.1 they still havenāt acknowledged the World of Warcraft issues, as well as many other issues reported by users, not very cool of AMD.
AMD deserves all the criticism, everyone should call them out for their issues after this long, or they will never improve.
Eh, fk it. Managed to sell my 7900 xt for a good price and bought 4070 ti super.
Donāt feel like waiting for a maaaaaybeeeeee fix in an unspecified future.
Anyone tried the new driver ?
edit : just to know, what CPUs are you using ?
ryzen 5 7600. can someone who has sever crash incidents try to play the game without discord running?
If tested without discord couple of times in the past, the issue is with the game or drivers, AMD or Blizzard does not care about World of Warcraft, the only solutions is criticism and plenty of it, preferably the kind of criticism that progressively louder the more ignorant they become.
@Taylors: I installed the Vulkan thingy on my machine and I get WoW crashes with it. They happen just like with DX12 in dungeons and in raids, but they completely crash WoW for me. :\
Do you happen to run MSAA + different renderscale cos that has been broken in past causing pinkscreen, the pinkscreen bug i cannot reproduce anymore but i know renderscale + MSAA has incompatibility, either use MSAA or just renderscale, do not combine AA techniques either together just pick one, i think MSAA in World of Warcraft is just broken it still says alpha test after all these years, it should not even be an option.
Yep the exact same thing is happening for me and i didnt find any way to fix it so back to dx11
Anti-Aliasing is set to āNoneā and Render Scale to 98%. Iāll just set it to 100% for the moment and see if anything changes.
Hello,
If this can help, here are some information regarding the issue with AMD CG and DX12, where the whole system hangs up for 10-15s , and wow sound remains, but discord an wow crashs.
CG: Sapphire Radeon RX 7800 XT,
CPU: AMD Ryzen 7 7800X3D
MB: ASUS TUF GAMING B650M-PLUS WIFI
I play under ubuntu linux (DXVK v2.3, wine-ge-26), and have the same issue as reported here under Windows. So itās not only Windows related. The logs shows a CGU timeout as under windows:
kernel: [24326.244734] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
In my case this issue is 100% reproducible when going up just after first boss at Brackenhide Hollow dungeon. There are also a couple of other areas with the same reproducible issue.
For this dungeon I have to switch to DX11, resulting in dropping from 160 FPS with DX12 to 50-60 FPS with DX11, which is kinda sadā¦
Cleaning and reconstruct shader cache changed nothing.
A thread on AMD regarding this issue
Guess i was lucky when i played on Linux i was still on the 6900 XT, i am sure everyone else can probably relate that their are games that you can play for hours without issue, while crashing in World of Warcraft which is frustrating because World of Warcraft is the game you want to play, but its the game that has most issues right now.
After i upgraded from 6900 XT to 7900 XTX the frequency i got issues went down but never fully went away, and it was the same kind of freezes i experienced on 6900 XT also reported by other users.
Still think AMD has messed something up at driver level with the way particle effects are rendered for example, cos its always the areas with these kind of effects where i froze the most.
Gogrond was the worst pre expansion cos i levelād every single character thru wod and thru gorgrond, in Dragonflight it was the azure span if had multiple freezes / crashes in snowy areaās especially azure archives.
If already seen proof of AMD messing with particle effects in Dying light 2 and having issues with particle effects in Ratchet & clank rift apart, on top of that both experience flashing images with particle effects probably.
If only seen 3 types of visual bugs in World of warcraft with RT shadows being glitchy when they interact with Radeon overlay which was fixed.
Pink screen with MSAA + renderscale set above or below 100% in revendreth video i posted in one of previous post.
Poison effect glitching on screen when flying around Caldera of the menders coordinates 39.07 ,34,24 on forbidden reach
Technically all these glitches are caused by the type of issue, just never experienced these flashes however in World of Warcraft.
But it does proof that AMD has probably been messing with it at driver level, and probably messed something up.
Might sound crazy but i would really encourage Blizzard to reach out to AMD or their no point in ever re subbing again, not like i will anyway after spending 200 euros on a game i lost motivation to play due issues with the game.
And if went thru multiple hardware swaps as well and testing different things, stress testing the hell out of my system with not even a slight hint of system instability, so good luck AMD and Blizzard i know its your fault, canāt keep shoveling this under a rug forever.
I am literally going thru insanity right now just because of this stupid issue that is being ignored, but also many other user reported issues.
Oh and if you gonna disable any anti aliasing or just run 1 anti aliasing setting only and run at 100% render scale do not forgot to switch resample from FidelityFX Super Resolution 1.0
