Test the Forward Renderer in your PC VR projects with the 4.14 Preview

[anonymous_user_23212407]

@HEGI;664174

‘Normal to Roughness’ can reduce the flickering on surfaces. This is a simple material option(Forward rendering category on the left). Otherwise it is a good idea to add something like 0.25-0.5 to the overall roughness of all surfaces in VR with MSAA.

Where do I find this material option please?

[HEGI]

@Vherenow;675327

Where do I find this material option please?

Here you go.

[anonymous_user_23212407]

@HEGI;675371

Here you go.

Thank you very much, however I have looked at all my menus and still cannot find this option? I apologize for my noob ignorance in advance ;-)…

[anonymous_user_23212407]

Ok I found it… Nevermind

[kAzAAkAs]

Decided to try out forward rendering in 4.15 about two weeks ago. I found the difference in sharpness that MSAA made to be quite small compared to upping the screen size a little bit.

Furthermore, I’ve found that performance actually worsened when using forward rendering. I had to lower my screen size in order to still guarantee 90FPS, even without using MSAA! As you may guess from my previous statement above, my experience was that in total it worsened performance quite a bit. MSAA is supposed to make the picture clearer than TAA, but in order to still guarantee 90FPS under these settings I had to lower the screen size by about 40%, so obviously the total picture quality got worse. I’ve also found that MSAA made all of the tree branches with leaves look very thin, much, much fuller leaf growth on my trees with TAA.

Overall, I’m slightly disappointed and decided to stay with deferred shading. I hope that nVidia will finally release the VRWorks fork for 4.15, hopefully ending my crispness vs FPS problems for good.

[IslandPlaya]

@kAzAAkAs;689591

Decided to try out forward rendering in 4.15 about two weeks ago. I found the difference in sharpness that MSAA made to be quite small compared to upping the screen size a little bit.

Furthermore, I’ve found that performance actually worsened when using forward rendering. I had to lower my screen size in order to still guarantee 90FPS, even without using MSAA! As you may guess from my previous statement above, my experience was that in total it worsened performance quite a bit. MSAA is supposed to make the picture clearer than TAA, but in order to still guarantee 90FPS under these settings I had to lower the screen size by about 40%, so obviously the total picture quality got worse. I’ve also found that MSAA made all of the tree branches with leaves look very thin, much, much fuller leaf growth on my trees with TAA.

Overall, I’m slightly disappointed and decided to stay with deferred shading. I hope that nVidia will finally release the VRWorks fork for 4.15, hopefully ending my crispness vs FPS problems for good.

This is good info that will probably me save lots of time repeating the testing that you did. Thanks for sharing.

[kAzAAkAs]

@IslandPlaya;689618

This is good info that will probably me save lots of time repeating the testing that you did. Thanks for sharing.

I don’t recommend that you do not try it out at all though. I think it’s performance may depend on the project. I’ts not that much work to test it either. Just enable the option, set AA to MSAA, restart the engine and wait a minute to let the shaders recompile. Then just hit “stat fps” and try some screen sizes and compare.

[IslandPlaya]

@kAzAAkAs;689657

I don’t recommend that you do not try it out at all though. I think it’s performance may depend on the project. I’ts not that much work to test it either. Just enable the option, set AA to MSAA, restart the engine and wait a minute to let the shaders recompile. Then just hit “stat fps” and try some screen sizes and compare.

Agreed. What I’ve taken from your post is that I can drop the priority of trying out the forward renderer. Performance measurement is easy but image quality is subjective and I’d spend ages trying to find an elusive sweet spot I imagine.

I’d already done the briefest of tests and I wasn’t much impressed.

It’s the lowering of my expectations for IQ/FPS using FR that will help me out ultimately. I’d much rather have VRWorks for 4.16 integrated and maintained by Epic going forward. If such a thing is possible.