Multisample Techniques broken after new patch

[Potiontrue-area-52]

Since the new patch, every time I boot up WoW, multisampling techniques is no longer working despite nothing in the setting having been changed (it’s turned on in the settings, it just doesn’t work).

If I then turn it off, then back on again, it starts to work like normal. But I have to do this every time I boot WoW since the patch. It was working fine before.

There is a thread on reddit with a handful of people reporting the same exact issue, but I couldn’t find anything in the forums so I’m making this thread.

[Zenjy-nesingwary]

You’d want to edit your post and move it to the tech support forum. That’d be the better place for this. You can use the pencil icon and move it there.

[Dezaller-barthilas]

Have noticed the exact same issue since weekly reset

[Pawgwalker-dalaran]

I can also now confirm this is an issue. I know what I’m looking at and for and you have to switch to a different version to trigger it to apply (the game will hitch for a second when you hit apply) in order to get it to work again.

1. I normally use 4x MSAA
2. I launched my client
3. I found a high-contrast diagonal edge
4. I turned MSAA off
5. No change in the stair-stepping aliasing on the edge
6. I switched back to 4x MSAA
7. No change in the stair-stepping aliasing on the edge
8. I switched to 2x MSAA and hit apply
9. The client hitched from the graphics restarting
10. The AA was now working
11. Switched to different levels like 4x and 8x and they now work correctly

So it sounds like something in the rendering thread isn’t checking variables correctly on the first go or maybe it’s some issue with variables not feeding the right values to things downstream.

I can also confirm that it doesn’t survive a relaunch. I’m sure they’ll fix it at some point, but to be honest, MSAA doesn’t really belong in a deferred rendering pipeline anyways(this is why almost all deferred rendering based games use temporal solutions for AA, that and they’re dirt cheap). One last edit: I can confirm that the image based AA(FXAA/CMAA) methods do survive a relaunch.

Yet another edit: CMAA2 is borked, but CMAA is fine. Get on a flying mount and look down at grass and it’s a noisy flashing static checkboard pattern.

https://imgur.com/gQpLUrk

[Pawgwalker-dalaran]

Made a post in the bug reports about these issues since this actually belongs there:

Anti-aliasing options are not working correctly

MSAA isn’t remembering it’s settings between launches and you have to set it to none, then back to what you want, before it will stick. Not sure if it survives a /console gxrestart (didn’t check, but I just thought about it) CMAA2(not CMAA) is broken and creates a terrible dithered checker pattern on alpha masked things like grass: https://imgur.com/gQpLUrk Some notes and things I’ve tested: Checked to make sure that config.wtf isn’t read-only Tested on slider 1 through 10 VRS off for all t…

[Valklock-dalaran]

Having the same issue. Hope this is fixed soon.

[Shalemara-moon-guard]

Thanks so much, I felt like I was going crazy.

[Abendel-moon-guard]

I noticed this same issue, I thought my GPU was stasrting to fail because I never had this problem before, I just don’t understand why the Quality assurance team is so lackluster these days.