A look at ACC in VR on a mid range PC

I decided to do a video to demonstrate how ACC currently runs in VR (oculus) in the early release 0.5 state. This video is a full grid and day to night cycles so its representative of frame rates and graphics quality in the dry. ASW is on the entire time. Typically I HATE ASW but it seems the unreal engine responds very well to it and I did not have as much tearing, jaggies, or blurring that I experience in other titles with ASW on.

the video is at 1080P so feel free to crank it up on youtube

I have a basic PC, Alienware Aurora R7: For VR I think its definitely a "mid range" PC
i8700
GTX 1070
16gb DDR4 2666 mhz ram

you be the judge...its smooth and playable for me. but the quality, as of now, is well behind AC. I am sure some optimization is coming. Wanted to share for the guys like me who do not have high end PCs. All in all, i really enjoy ACC despite the graphics shortcomings. The time cycle, lighting, physics, tire model, and FFB are looking and feeling very good to me at this point.

 

Pretty sure ASW made the game choppy. I remember turing it off as others and was much smoother, unless it's changed.

 

with my PC there is no comparison, the ASW is 100% required for a smooth experience. When I force it off its un playable unless I am on track by myself, which isn't much of a stress test.

 

with my 1080ti, the ASW is very smooth, works very well, and I can push more my graphic settings than in this video so it is better for me visualy

 

Thanks for sharing - To the OP, the quality is pretty good in fact - I run a i7 8750, GTX 1080 and 16GB DDR4 ram - Am running with pixel density set at 1.5 in Oculus Tray tool - Am constantly at 90fps with high / Epic settings in game but it is very hard for me to read the text on the dashboard (it is blurry) - your video shows it is perfectly clear and am now wondering what's wrong with my environment! I haven't tried ASW yet - I just got the Rift a few days ago. I guess am going to try ASW now.

 

yes you should try it, you could manage to up the pixel density and all other graphic settings.

 

Try these settings, they made mine go from 45 fps to ~80fps.

https://docs.unrealengine.com/en-us/Platforms/VR/ContentSetup

 

Interesting, I will try it.
Does it have an impact on visual compared to original ?

 

Probably, I could not see anything.

 

I have also very clear dashboard in Oculus, but I set pixel scaling in game settings, not in Oculus tray tool. Try that.

 

Thanks but I tried I did set it at 200% and it is clear when I look at the right panel with all the buttons but not the digital dashboard behind the wheel (the other digital panels that are closer are fine tho) - I mostly drive the Ferrari - If I come closer with the headset then it becomes clear(er) but not if I don't.

What in-game pixel density are you using if I may ask?

 

I thought anything above 100% is a waste of time. What you need is a beefy CPU, and a beefy GPU.

VR definitely eats performance even if you have the best hardware. Unless you have the best I doubt anything can be done about it.

 

I hear you - However I definitely see the difference in terms of quality rendering (aka visuals) but it definitely taxes the system a lot. If I don't go above 100% I get 90 fps with most settings set to Epic so it is not too bad but the dashboard and panels in cockpit view is a let down for me with a pixel density of 1 (100%). If I set it to 1.5 (150%) I get around 45 fps locked in front view (without cockpit) otherwise it is between 25-45 fps in cockpit view.

 

Thank you for the video. Could you please post your graphics settings screen too (AA, quality levels, Pixel density....)?

I feel I get much worse graphics and framerate in VR (Oculus Rift) although I have stronger hardware except the CPU. Perhaps I should upgrade CPU?

I also experience strange tearing/ghosting (from the TAA I think): when I look outside the left window I see the sidemirror multiple times (semi transparent tearing/ghosting effect). It seems you don’t have this problem...

 

I have done some test, 45fps with original engine.ini and 73fps with this tweaked engine.ini, there is not much loss in graphics rendering, it stays acceptable and will allow to push the graphic setting even more.
As you can see, first pic is with original engine.ini, and there is more dark inside the car and trees, with the tweaked one all is more clean, looks like a light switched on inside the car.

 

Looks brighter because you are missing ambient oclussion:

r.AmbientOcclusionLevels=0

 

Great link, thank you for sharing

The first line of the settings says : vr density 1
I run with 150% which is 1.5, will that setting overwrite my in game setting? Or should I change 1 for 1.5 in the settings?
Where is the : Config\DefaultEngine.INI?

 

yes this is it, so I have tested:
r.AmbientOcclusionLevels=0 --> 73fps
r.AmbientOcclusionLevels=1 --> 69fps and very close to original so worth it
r.AmbientOcclusionLevels line deleted for have the original activated --> 64fps

in conclusion, I will use the r.AmbientOcclusionLevels=1 for better visual and only 4fps loss

I have deleted this line in order to have the ACC parameter but even if you keep it, it will use the ACC one (150%)

 

where exactly are we supposed to paste those settings?

[SystemSettings]
vr.PixelDensity=1
r.SeparateTranslucency=0
r.HZBOcclusion=0
r.MotionBlurQuality=0
r.PostProcessAAQuality=3
r.BloomQuality=1
r.EyeAdaptationQuality=0
r.AmbientOcclusionLevels=0
r.SSR.Quality=1
r.DepthOfFieldQuality=0
r.SceneColorFormat=2
r.TranslucencyVolumeBlur=0
r.TranslucencyLightingVolumeDim=4
r.MaxAnisotropy=8
r.LensFlareQuality=0
r.SceneColorFringeQuality=0
r.FastBlurThreshold=0
r.SSR.MaxRoughness=0.1
r.rhicmdbypass=0
sg.EffectsQuality=2
sg.PostProcessQuality=0

 

@Mike1304 I will post my settings once I prove them out in the rain and will post up another video of a full grid rain race.

I have used @Cote Dazur 's .ini files in previous releases with amazing results. however for the sake of these videos I wanted to see how I could get ACC to perform in with a "stock" engine.ini file.

I would recommend using his changes and will test that out in the near future on the 0.5.1 release.