

Sithspawn, Bignewy it would be awesome if you could please have quick a chat to Wags and get the lowdown and confirm that something is happening with AA and report back?Ĭheers and thanks to ED again for developing more awesome stuff for us.

This has been a problem since 2.2 came out and I guess all I am wanting to hear is that this is a priority for the team at ED and a solution is being worked on? I haven't seen anything mentioned by Wags for quite a while about s definitely a major problem.īut even if a solution is months off at least we will have a dream to look forward to. Its always good to get a big sample size to iron out bugs.Įvery thread I'm reading thus far about 2.5 (and 2.2 for that matter) around performance discussions has at least 5 or six separate comments about how MSAA is destroying frame rates with deferred shading on, and everyones solution is just to have it a "0" or nvidia control panel work arounds (which unfortunately don't work for VR users) so its basically redundant having it (unless you have a 1080ti and then you can maybe push it to 2x or 4x) Looks like it has been an exciting but mixed start for everyone on the 2.5 beta, but ED have always pushed forward with solutions and I'm sure they will solve a lot of the problems asap.
