VR in normandy

[nachomaga]

Same low performance here, 4790k at 4.7ghz and 980ti. Was good in 2.0. Struggling with settings, like the old days with FSX, hehe. Ill try the Scooternutz settings.

[awjudge]

You are right but reading the pre-release folks VR accounts, this was the cats ass for VR. What happened?

 

 

 

Good question... NTTR had these problems when it was released. I'm sure they'll figure it out.

 

 

Sent from my iPhone using Tapatalk

[dburne]

Well I got it maintaining 45 fps in take off instant action mission for the Spitfire in Normandy.

 

Had to lower textures to medium, lower visibility range and trees/clutter a lot.

Shadows - Flat Only.

 

But still this is with no other planes in the air close by.

[Wolf8312]

It's a shame but as a VIVE user you wouldnt believe how far my performance has come in a year!

 

I'm gonna forget about Normandy and pretend it doesent exist for a while but I am confident it will come good in the end.

 

Whether it can compete VR wise with the WW2 VR competition though I am not sure, as its some pretty silky smoothe competition dogfighting wise!

[funkyfranky]

I've made a relatively detailed performance comparison between DCS 2.0.5 and 2.1.0. You can find it here.

Performance in DCS 2.1 does not look too bad FPS wise. But deferred shading and MSAA don't mix well at the moment.

[SpeedStick]

I've made a relatively detailed performance comparison between DCS 2.0.5 and 2.1.0. You can find it here.

 

This. +Rep

[dburne]

Well have now turned shadows completely off and lowered details even more. At least can maintain ASW of 45 fps, not much hope of hitting 90 fps for non ASW ( unless over just water).

 

What do you guys think of the new deferred shading or whatever it is called. I turned it on and while it did not seem to hurt much performance wise for me, man it sure makes things pretty bright and some objects blurred seems like. Not sure I am going to like it, at least in it's current incarnation.

 

Also in VR of course the aircraft icons are way too big, hopefully at some point down the road they can scale those down somewhat. Hard to see the runway when there are several planes parked around it with all their icons hovering above...

[=DECOY=]

This is very interesting! Can you make a video of that... havent seen any VR Normandy expierience with good framerate. Not a single one with proof of stable fps :noexpression:

 

 

Not the best quality but you can see the fps counter, used a f5,2000c and huey ( sorry for the flying hahaha)

 

 

 

[PreussLee]

Gotta say i was a bit confused reading all the comments about bad performance. For me it runs pretty well, mostly like Nevada over Vegas in 2.0. Did fly mainly the Huey in Normandy yet and i actually feared it would be a lot worse! Though i did turn my settings down a little...PD from 1.6 to 1.4, shadows low and i dont use the deferred shader. And had to turn the terrain shadows from flat to off because they seem broken to me...

But besides from those few little tweakings im pretty happy with the performance yet! Still hoping that its gettin better with the next few updates of course :P

[Verde]

Yeah but VR need 90fps and 45 is like walking with one leg already, asw needs to be a brief performance saver not judder. But grasp for 45 as a start point is a bad idea thing simply isnt as enjoyable. Fingers crossed that devs will sort the fps.

[dburne]

Well I have leaned my graphics settings out about as far as I can get, low settings - no shadows. No matter what I do, I can not achieved 90 fps whilst flying over Normandy. Over the water sure, but over the land no way.

 

So for now guess I will have to be satisfied flying with ASW on at the 45 fps rate. Have spent most of the morning tweaking settings and testing. No matter how lean I get it, I just cannot achieve 90 fps flying over land. Going to go back in and start increasing my settings a little at a time, testing in between, until I see it start to dip below the ASW rate of 45 fps. Then will back it off a little from there, and be happy with what I have for now.

 

I will be hoping for future optimizations to occur to maybe help, or if not maybe the next gen of video card might get me back up there.

I sure am enjoying flying my Spit over Normandy though!

[Knock-Knock]

All said though, regarding performance. Visually it sure does have it moments. Yes its a little too hazy, and horizon gets all bloomed out etc, but thats tweaks. The potential is very much there.

 

Now these two shots, from my flying around Nevada, hunting suitable settings for me, doesnt tell the entire story in VR, as we know.

The one with the sun in back, nothing special, I just noticed that the grid in the radar cast shadows, and it gave it all a nice depth - sadly the radar elements were on top of it all, so it killed the depth a little.

Glare, sun glare, Im a sucker for a sunglare, and 2.1 does that really good already. Small glares from the small lakes, and all kind of bits and bops of the plane and cockpit.

[Los]

My friend and I both vr users (he Oculus me vive) are bore both dealing with chunkage. Its a step back. Starting in non vr mode, Normandy is much smoother. We'll sit out Normandy until it get sorted out.

[Tj1376]

All said though, regarding performance. Visually it sure does have it moments. Yes its a little too hazy, and horizon gets all bloomed out etc, but thats tweaks. The potential is very much there.

 

Now these two shots, from my flying around Nevada, hunting suitable settings for me, doesnt tell the entire story in VR, as we know.

The one with the sun in back, nothing special, I just noticed that the grid in the radar cast shadows, and it gave it all a nice depth - sadly the radar elements were on top of it all, so it killed the depth a little.

Glare, sun glare, Im a sucker for a sunglare, and 2.1 does that really good already. Small glares from the small lakes, and all kind of bits and bops of the plane and cockpit.

 

 

 

You have to admit, 2.1 is astonishingly beautiful.

 

TJ

 

 

Sent from my iPhone using Tapatalk

[Knock-Knock]

You have to admit, 2.1 is astonishingly beautiful.

 

TJ

 

 

Sent from my iPhone using Tapatalk

 

 

The light in the 'right' time of day, in a more Deferred polished module, yes, its wonderful.

The noise though, ouf, need that MSAA bad. Deferred is a noisy rendere, and running that without AA in VR, oh man :). But I still prefer running the noisy Deferred over the old rendere / shading. Hope they will move quick on giving us some performance back, allow us to use MSAA without dropping half the frames, and get them modules polished quick.

[Cibit]

I am sorry for all these posts about unplayability. Granted I have not done much but fly around in different aircraft and tried different wind and TOD settings.

I love it, I can not get 90fps but as I could not before in NTTR with the settings I chose its all good.

I have had to make some adjustments to suit, removing AF and MSAA in game and replacing them with nvidia CP settings- AFx8, FXAA On, Antialiasing x8

I have flat cockpit shadows now instead of high and flat terrain shadows using the defered shaders and the cockpit illumination settings too. PD in the rift is 1.5 oh and high water for screenies

 

Overall and knowing that optimisation will occur I am more than happy at the moment:)

Edited May 28, 2017 by Cibit

[Knock-Knock]

with nvidia CP settings- AFx8, FXAA On, Antialiasing x8

 

Oh, gotta try that. Only tried with x2, and saw no difference. Gotta bring out the AA sledgehammer it seems :)

[VampireNZ]

I am sorry for all these posts about unplayability. Granted I have not done much but fly around in different aircraft and tried different wind and TOD settings.

I love it, I can not get 90fps but as I could not before in NTTR with the settings I chose its all good.

I have had to make some adjustments to suit, removing AF and MSAA in game and replacing them with nvidia CP settings- AFx8, FXAA On, Antialiasing x8

I have flat cockpit shadows now instead of high and flat terrain shadows using the defered shaders and the cockpit illumination settings too. PD in the rift is 1.5 oh and high water for screenies

 

Overall and knowing that optimisation will occur I am more than happy at the moment:)

 

So just to confirm - your settings in the nVidia CP are having an effect in-game in VR?

[Cibit]

I managed to get rid of the horrible shimmering on objects in NTTR and the buildings looked better. It certainly made a difference but as all settings where applied together it is possible some are not working. Certainly room for more testing:)

[Wakkaman]

It is important to choose vr as preset in you're graphics options and tweak... my fps is not to bad.

But the lighting in the normandy map is really to bright in VR, it's a bit dissapointing. I also think the map doesn't look that impressive, especially from a high altitude it looks way to repetitive.

[Knock-Knock]

Mmnope, not working for me, AA from the driver makes no difference. Tried a few trough nVidia Inspector too.

[VampireNZ]

Mmnope, not working for me, AA from the driver makes no difference. Tried a few trough nVidia Inspector too.

 

Same here - I did a little investigating and it looks lilke this is by design, a headset display will not get it's info from the nVidia CP/driver. The headset is actually purposefully hidden as a display device from the OS etc.

 

Interesting some pple are saying it does.....:huh:

[Cibit]

Same here - I did a little investigating and it looks lilke this is by design, a headset display will not get it's info from the nVidia CP/driver. The headset is actually purposefully hidden as a display device from the OS etc.

 

Interesting some pple are saying it does.....:huh:

 

It was me and perhaps it was wishful thinking, I am nevertheless convinced it looks better so everyone is happy:thumbup:

[Blackrat_UK]

Same here using NVCP, but Supersampling does work in NVCP, Antialiasing-transparency with VR.

[Torso]

It was me and perhaps it was wishful thinking, I am nevertheless convinced it looks better so everyone is happy:thumbup:

 

Same here - I did a little investigating and it looks lilke this is by design, a headset display will not get it's info from the nVidia CP/driver. The headset is actually purposefully hidden as a display device from the OS etc.

 

Interesting some pple are saying it does.....:huh:

 

You can use the Nvidia control panel to adjust the picture in VR but you have to do it a special way.

 

What you do is, since the HDMI port the VR set is plugged into is hidden you unplug your VR headset, and plug a monitor into the SAME hdmi port. Do not turn off or restart your pc for this. Just do a hot swap. If you have a Vive you can just unplug the hdmi cable from the headset to the hub and plug the monitor into the hdmi port on the hub as it is just a pass thru. If you got a Rift, then just unplug from gpu hdmi port and plug monitor into SAME hdmi port.

 

Now, you can go into the NV cp and go to Display-Adjust desktop color settings

 

Select the monitor you plugged into the VR hdmi port and select the Use NVIDIA settings option.

 

Now, you just have to make some tweaks that you hope will achieve your goals. Add some contrast, brightness, gamma or remove whatever..I like to bump Digital Vibrance up by 5-10 from default 50 as well. So you make your adjustments. The only bad thing, is you cannot check how they are until you are back in VR but you will see your changes reflected on the temp monitor you plugged in so you have that to go by of course.

 

So now that you made the adjustments you save them and close the control panel.

 

Now unplug the monitor from the hdmi port. Plug back in your VR headset.

 

Boom done, now the changes made are retained from Nvidia for that HDMI port, even through restarts even though it is hidden once VR is plugged into it. It still applies the setting you made to the port.

 

Anyways, that is how you do it. Hope it helps some of you.

Edited May 29, 2017 by Torso