Discussing Unreal

VRSS is supported by Robo Recall which is an unreal 4 engine game. So i think there should be hope for ACC

 

From what i've heard VRSS doesn't work with deferred rendering, only with forward rendering. So same issue with MSAA ... doesn't look like ACC is gonna support it, at least not in it's current form.

 

While trying almost every combination of console variable seems to make very little difference to the performance i get in ACC (specifically in VR), one line does produce a huge boost in frame rates.

r.forwardshading=1

I'm not at all familiar with Unreal engine, but assume this enables a forward rendering mode (of sorts) ?
Unfortunately, it also breaks quite a lot of the lighting, and other effects, but the performance difference on my Ryzen 7 1700 / RX480 is huge.

Does this at least give some evidence to support how much improvement could be made in the future, wether in ACC or another title, if the prefered VR branch was used?

 

Or maybe it just shows that the lighting and other effects require reasonable processing power, and by 'breaking' them you leave more overhead for the remainder?

 

Assuming that setting switches from the Deferred Renderer to the Forward Shading Renderer, Epic say:

Switching from the Deferred Renderer to the Forward Renderer may provide you with an increase in performance for your project.

The forward renderer can be faster than the deferred renderer for some content. Most of the performance improvement comes from features that can be disabled per material. By default, only the nearest reflection capture will be applied without parallax correction unless the material opts-in to High Quality Reflections, height fog is computed per-vertex, and planar reflections are only applied to materials that enable it.

Leveraging these options in Epic's new VR game, Robo Recall, the forward renderer is about 22% faster than the deferred renderer on an NVIDIA 970 GTX.


https://docs.unrealengine.com/en-US/Engine/Performance/ForwardRenderer/index.html


Sent from my iPad using Tapatalk

 

r.forwardshading=1

Grade ausprobiert. Performance top, leider Nachts unfahrbar ; (

 

So the performance increase seems to be real. According to what @Typer posted, the settings default to something very low. It would be interesting to have a list of those settings and then increase them, manually until ACC gets usable, again. Seems like a good community job.

 

Very good
I think we should create a new topic in the vr section for more visibility by dev kunos

 

It would be interesting to have a list of those settings [/QUOTE]
You will find every possible variables in the free unreal documentation,
f. e. https://docs.unrealengine.com/en-US/Engine/Performance/ForwardRenderer/index.html

here:
https://docs.unrealengine.com/en-US/Engine/Performance/Scalability/ScalabilityReference/index.html

or here:
https://digilander.libero.it/ZioYuri78/

But what is it good for to have more fps at sunny daytime, but at rain or night it's undriveable in this case?

 

That setting is VR only or also improves fps without VR?

 

It's not VR only. But as said it does break things like lights, hence the performance gain.

Up to Kunos to provide a proper forward render version... but I can't imagine the performance gain will still be there once the lights are adapted. There's already relatively few shadow-casting dynamic lights with the deferred renderer, despite being faster with many dynamic lights.

 

unreal engine is trying to solve the problems of vr de acc?

or he really doesn't care what's happening

 

@houssen to which problems do you refer?

 

the msaa is not implemented
with the valve index I cannot exceed 45 fps with acceptable vision performance

 

You should read the whole thread and find what the devs have said.

Here's what Ari said earlier.

 

I think I'm one of the people who read almost every thread

msaa is not implemented

Real or not ?
when acc can somehow be able to implement it the vr can work perfectly

 

ACC uses deferred renderer in UE4 which doesn't support MSAA, that's why it's not implemented.

 

For Oculus.
Try add this to Engine.ini :

[Oculus.Settings]
PixelDensityMin=0.5
PixelDensityMax=1.0
PixelDensityAdaptive=true

I changes min to 1.5 and max to 2.0
FPS seems to be more stable.

 

But you can add an option to specify how view frustums are applied from camera point of view and just make it happen in bigger distance from the camera especially swithing from she smallest frustum to the second one is too close to the camera/observer and if somebody is using small fov this distance should be also compensated to it. It could be also great option to disable this directional light csm at all.

It could be also good to experiment with Dynamic Shadow Distance for Movable Light in Unreal Editor.