# 4.18 + forward rendering + HTC vive - blurry antialiasing

**URL:** <https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390>\
**Category:** Rendering\
**Tags:** UE4-18, msaa, Forward-Rendering, unreal-engine, question\
**Created:** [October 31, 2017, 10:47am UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390 "2017-10-31T10:47:24Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous\_user\_7ea5c0e9](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_7ea5c0e9](https://forums.unrealengine.com/u/anonymous_user_7ea5c0e9)\
**Post date:** [October 31, 2017, 10:47am UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/1 "2017-10-31T10:47:24Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![liquidpza](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@liquidpza](https://forums.unrealengine.com/u/liquidpza)\
**Post date:** [October 31, 2017, 7:01pm UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/2 "2017-10-31T19:01:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_7ea5c0e9](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_7ea5c0e9](https://forums.unrealengine.com/u/anonymous_user_7ea5c0e9)\
**Post date:** [October 31, 2017, 7:39pm UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/3 "2017-10-31T19:39:23Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_1b767992](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_1b767992](https://forums.unrealengine.com/u/anonymous_user_1b767992)\
**Post date:** [November 8, 2017, 10:09am UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/4 "2017-11-08T10:09:26Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_7ea5c0e9](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_7ea5c0e9](https://forums.unrealengine.com/u/anonymous_user_7ea5c0e9)\
**Post date:** [November 8, 2017, 10:32am UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/5 "2017-11-08T10:32:35Z")

</div>

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 …

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_1b767992](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_1b767992](https://forums.unrealengine.com/u/anonymous_user_1b767992)\
**Post date:** [November 8, 2017, 10:47am UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/6 "2017-11-08T10:47:36Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![darinsmyth](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@darinsmyth](https://forums.unrealengine.com/u/darinsmyth)\
**Post date:** [January 8, 2018, 6:47pm UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/7 "2018-01-08T18:47:27Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![liquidpza](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@liquidpza](https://forums.unrealengine.com/u/liquidpza)\
**Post date:** [January 8, 2018, 11:51pm UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/8 "2018-01-08T23:51:06Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![anonymous\_user\_942e8e52](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_942e8e52](https://forums.unrealengine.com/u/anonymous_user_942e8e52)\
**Post date:** [January 12, 2018, 8:20pm UTC](https://forums.unrealengine.com/t/4-18-forward-rendering-htc-vive-blurry-antialiasing/408390/9 "2018-01-12T20:20:19Z")

</div>

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

> **[Significant Changes Coming To VR Resolution Settings in 4.19](https://www.unrealengine.com/en-US/blog/significant-changes-coming-to-vr-resolution-settings-in-4-19)**
>
> We’re adding a new cvar in 4.19 to control panel resolution for Unreal Engine 4 (UE4) Virtuality Reality (VR) projects and moving away from referencing Screen Percentage. Here’s what you need to know.
