After much trial and error to solve my Error 132, after updating Windows 10, and my AMD drivers, trying some compatibility mode suggestions.
Anti-Aliasing turned on will instantly cause Error 132. Anti-Aliasing turned off, the game will run as normal.
I canāt even get into the game to turn it off.
You should be able to access menu on the character select and login screens.
I canāt get that far. My game crashes at launch. I uninstalled all my add ons and now am downloading a new video driver.
Iām having the same issue, I canāt get to character select either, crashes before anything loads.
My client crashes immediately if I try to log into a character with MSAA anti-aliasing enabled. CMAA and lower are currently working fine. This wasnāt an issue before the patch released.
I can not even make it to select screen it crashes a soon as the game launches.
Iām also having the same problem after installed the patch
Thank you for your report, everyone! Weāre gathering information and checking this out! Just curious for those who canāt launch at all. Does forcing Dx11 work around the AA crashes?
-d3d11Im already in dx11 mode because of the shader cache bug you guys have not fixed yet for AMD cards.
EDIT and Update: Well actually adding that did work and was able to log in as it looks like it reverted back to dx12 so that means dx12 is completely busted for AMD cards?
I have a nvidia card and having same issue kraceā¦
Caterpepi,
This worked! Note, I had used the Launcher to āReset In-Game Optionsā and had no success. Adding that -d3d11 flag in forced it to work.
The Anti-Aliasing crashes are appearing on AMD cards only from the reported crashes. If youāre on an Intel Integrated card or Nvidia, please start a separate thread.
Thanks for following up! It looks like the ones with D3D11 work around that has worked so far is a different crash than the Anti-Aliasing crash. If the crash is immediate, please try the workaround posted above.
If you are able to access the character select screen, please try disabling Anti-Aliasing or trying CMAA if using MSAA. If this works, please let us know if switching to -d3d11 or Direct X 11 under System > Advanced works with MSAA.
I have an AMD card and Iām experiencing the anti-aliasing crash when using MSAA, even when switching to DX11. On DX12 the crash would be immediate with an error pop-up, on DX11 I can load into the character select screen, but when entering the game it just freezes and I have to manually exit.
CMAA seems to work fine right now, but I do hope something can be fixed as MSAA is my preferred AA setting, and the best looking one.
Going into advanced settings and switching off āMultisample Alpha Testā fixed this issue for me.
However, iām noticing a lot of FPS stuttering recently.
Velaisa that worked for me! I was able to put MSAA x8 back on when I unchecked that box and now it seems to not be crashing! 
Thank you so much, Iām so picky about my graphics settings and the difference is very noticeable to me when I have to use alternate AA settings.
This worked for me. I was using dx12 before and now i can get in. Before it would crash on load in. Thank you for the work around until things can get fixed
I got an AMD card and changing DX 12 to 11 worked for me just fine, although as far as I know Iāve never changed anything on AA since I installed the game ( is market as āNoneā for quite a while)
I am using Vega 64 on 19.3.1 driver. Game crashes when using MSAA, on both DX11 and DX12. Playing without MSAA works on both, so Iāve been using CMAA as a workaround. Looks terrible, Iāve been spoiled. lol