4.18 + forward rendering + HTC vive - blurry antialiasing

anonymous_user_7ea5c0e9 · October 31, 2017, 10:47am

Hi Everybody,

We are actually testing the new version of UE 4.18.

We converted one of our existing VR project and noticed the antialiasing in our HTC Vive changed a lot.

In 4.17, when using forward rendering + MSAA, we have a nice, crisp antialiasing.

In 4.18, with the same scene and same settings the aliasing looks blurry and incorrect.

As an example, it looks the same as when you use defered rendering + Temporal AA with an HTC Vive.

Did someone else has the same problem ? Maybe we missed something …

Of course we tried to reverse to deferred then reactivate forward rendering among other tests in order to be sure we identify the problem.

Best regards

liquidpza · October 31, 2017, 7:01pm

I’m having the same issues, I’ll let you know if I find a solution.

anonymous_user_7ea5c0e9 · October 31, 2017, 7:39pm

At least I’m not alone ^^
Let’s investigate

anonymous_user_1b767992 · November 8, 2017, 10:09am

I´m having similar problems. It seems to me that the supersampling in SteamVR has no effect on 4.18. When I run the same project on 4.17 the supersampling is applied. Sadly I don’t have any solution for this yet.

anonymous_user_7ea5c0e9 · November 8, 2017, 10:32am

Very interesting.
For short, do you think it has to be corrected by Epic or Steam ?
I’m pretty confident if the problem comes from UE, it will be solved in the next update …

anonymous_user_1b767992 · November 8, 2017, 10:47am

I don´t know who should fix it. Hopefully it gets done somehow

I did try around with the r.screenpercentage command and achieved the same kind of effect. What I don´t know if this has a bigger or smaller performance impact. It seems like it is more costly but maybe I’m imagining.

darinsmyth · January 8, 2018, 6:47pm

Anybody any update on this? I seem to be getting blurryness with Vive and 4.18.2

liquidpza · January 8, 2018, 11:51pm

I’ve been using an Execute Console Command in the level blueprint and running an r.screenpercentage 200 command. Of course you can adjust the 200 and find a percentage that works well for you. This seems to be a solid work-around until it’s fixed in an update. I hope this works for everyone, good luck in there!

anonymous_user_942e8e52 · January 12, 2018, 8:20pm

“+1” for this workaround. Sounds like things will be cleared up in 4.19.