Oculus Rift and DCS World Discussion

[Frusheen]

Hi Gents,

 

Don’t mean to change the subject too much, but just picked up the Rift DK2 and wondering if you can guide me to any tutorials for setting up with DCS this weekend. Running a GTX 980TI.

 

-Rick

 

Rick,

- Install the 0.7 oculus runtime and setup your IPD via the configuration utility.

- launch DCS and select auto detect oculus rift then exit.

- Right click on DCS icon go to properties and set it to launch in vista compatibility mode.

- launch DCS and put on your rift.

- press right ctrl and pause keys to show FPS. Adjust graphics options to get 150FPS and enjoy.

 

Colour saturation is currently off. The bug was reported and a fix is coming. EDIT: fixed! :-)

Edited October 9, 2015 by Frusheen

[AH_Sid]

Hotfix 2 just released, I no longer need the vista compatibility mode workaround and the colour saturation is fixed, looks great! :thumbup:

[hannibal]

That's why I'm upgrading to Skylake and then waiting for pascal. I'll stick with my Geforce 970 until pascal is released now. But I did think Nvidia spoke about having two cards running a screen each . Anymore news on that?

 

I've just realized, I'm going to be spending hugh amounts of money in the next year :helpsmilie:

 

im in the same boat.. may not need skylake (2600K & 980x owner here) but definitely i need pascal and its 3d stack mem tech!!

[rjetster1]

Rick,

- Install the 0.7 oculus runtime and setup your IPD via the configuration utility.

- launch DCS and select auto detect oculus rift then exit.

- Right click on DCS icon go to properties and set it to launch in vista compatibility mode.

- launch DCS and put on your rift.

- press right ctrl and pause keys to show FPS. Adjust graphics options to get 150FPS and enjoy.

 

Colour saturation is currently off. The bug was reported and a fix is coming. EDIT: fixed! :-)

 

Thank you so kindly!

[joebloggs]

Hotfix 2 just released, I no longer need the vista compatibility mode workaround and the colour saturation is fixed, looks great! :thumbup:

 

As far as I can tell this statement is wrong. There is no mention in the patch notes about a crash fix for Dk2 and I'm still crashing even running vista compatibility mode now. The color issue is fixed, but certainly not the crashes.

[frank7006]

DCS 1.5 Oculus Rift DK2 performance

 

I have an i7-3770 3.4ghz quad core and a Nvidia GTX 980ti superclocked. Here is my experience with performance in the DK2 in the DCS 1.5 Beta:

 

Mig-21 performance is atrocious. It's by far the worst and is absolutely unplayable even on my 980 ti superclocked - the fastest card you could possibly buy. If I turn every single graphics setting to its absolute lowest level I get on average 30 fps in the 'takeoff' instant action scenario. The other scenarios are similar in fps.

 

The other aircraft modules don't work very well either and even keeping a steady 75 fps on medium graphics settings is not possible when flying low near cities. Some of the modules like the Mig-15 and F-86 run pretty well on medium settings some of the time though.

 

Shadows - even the lowest setting - are a huge performance loss and have to be turned off completely.

 

 

If ED implements asynchronous time warp we should see a roughly 80-90% increase in performance. When I played the FlyInside FSX demo, asynchronous time warp would maintain a steady 75 fps even though my actual performance would dip down to 40 fps. Below 40 fps it could not hold 75 fps.

 

If anyone has any tips or tweaks please post them here. I'm always looking for anything that will boost my fps in the DK2.

Edited October 10, 2015 by JaySmizzle

[vicx]

Yo JaySmizz.

I think DCS 1.5 Beta might already be using are using Async timewarp. The way that DCS measures frames you need to be getting 150fps for perfectly smooth VR. When you drop below 150fps I think Timewarp is being used.

 

Check the last few pages of this thread for details. TLDR ... Press RCTRL-PAUSEBREAK to see DCS fps displayed.

 

VR is very demanding and shadows are VERY heavy especially in a pit like the Mig-21 which has the most polygons of any DCS pit.

Edited October 10, 2015 by vicx

[joebloggs]

Yo JaySmizz.

I think DCS 1.5 Beta might already be using are using Async timewarp. The way that DCS measures frames you need to be getting 150fps for perfectly smooth VR. When you drop below 150fps I think Timewarp is being used.

 

Check the last few pages of this thread for details. TLDR ... Press RCTRL-PAUSE to see DCS fps displayed.

 

VR is very demanding and shadows are VERY heavy especially in a pit like the Mig-21 which has the most polygons of any DCS pit.

 

What pause key do you mean? Which key are you referring to on the keyboard?

 

 

If anyone has any tips or tweaks please post them here. I'm always looking for anything that will boost my fps in the DK2.

 

You could try this.

 

[Frusheen]

[Frusheen]

Yo JaySmizz.

I think DCS 1.5 Beta might already be using are using Async timewarp. The way that DCS measures frames you need to be getting 150fps for perfectly smooth VR. When you drop below 150fps I think Timewarp is being used.

 

Check the last few pages of this thread for details. TLDR ... Press RCTRL-PAUSEBREAK to see DCS fps displayed.

 

VR is very demanding and shadows are VERY heavy especially in a pit like the Mig-21 which has the most polygons of any DCS pit.

 

I don't think it is using timewarp vicx. The judder would not be so bad below 150 frames if it was. I kinda suspect it may be using super sampling though. The image clarity has improved so much since 1.2 it looks higher resolution.

[LuSi_6]

for me all problems are fixed:

 

uninstall OC runtime

uninstall NVIDIA drivers

clean up System (CCleaner)

 

make sure dcs OB is clean

 

install OC runtime

before reinstall NVIDIA drivers: Stop OC Service, kill all OC stuff in task manager

 

set NVIDIA controlpanel to global-> Performance

 

run dcs still in vista sp2 mode and vsync off

 

game all day long :)

[=DECOY=]

quick question for rift users what resolution are you using ?

 

thanks in advance I'm intrigued

[LuSi_6]

you can't choose. It's always the rift resolution, no matter what you set

[=DECOY=]

New Gamma has made a massive difference on the rift. Great job:thumbup:

Edited October 10, 2015 by =DECOY=

[joebloggs]

for me all problems are fixed:

 

uninstall OC runtime

uninstall NVIDIA drivers

clean up System (CCleaner)

 

make sure dcs OB is clean

 

install OC runtime

before reinstall NVIDIA drivers: Stop OC Service, kill all OC stuff in task manager

 

set NVIDIA controlpanel to global-> Performance

 

run dcs still in vista sp2 mode and vsync off

 

game all day long :)

 

I wouldn't say the problem is fixed if you have to resort to doing all what you have done. I also don't see how "stopping the OC Service and killing all OC stuff in task manager" would make a difference to the Rift working or not. Also, what do you mean when you say make sure the OB is clean? Do you mean Oculus Beta?

 

Edit: I just tried what you did and at times I still get crashes when mission is loading. So for me this still isn't fixed. I think ED need to at-least recognize there is a problem by confirming this in the Crash Bug section of 1.5.

Edited October 10, 2015 by joebloggs

[hansangb]

I wouldn't say the problem is fixed if you have to resort to doing all what you have done. I also don't see how "stopping the OC Service and killing all OC stuff in task manager" would make a difference to the Rift working or not. Also, what do you mean when you say make sure the OB is clean? Do you mean Oculus Beta?

 

Edit: I just tried what you did and at times I still get crashes when mission is loading. So for me this still isn't fixed. I think ED need to at-least recognize there is a problem by confirming this in the Crash Bug section of 1.5.

 

 

That's the point of the beta. Hope you reported it on the beta thread (or added to the existing crash reports)

[joebloggs]

That's the point of the beta. Hope you reported it on the beta thread (or added to the existing crash reports)

 

What do you mean by that's the point of the beta? I did report it, but have no idea what you mean when you say: "That's the point of a beta." I know what the point of a beta is, it's to test bugs and report them which is what I have done. Unfortunately, though, ED haven't yet stated it's a bug like they have done with others, so everyone's left wondering if it's something to do with their settings. That's why people are trying all sorts of different stuff like reinstalling this that and the other. I've tried hitting my machine with a hammer, but that didn't work either.

 

The point is you can't fix something if this has something to do with Eagle Dynamics code, but with no word who knows?

[Smoky]

With the latest DCS updates, can you now read the gauges using DK2? The Hud? Is the zoom fixed? (Biggest issue with DK2 in DCS was the lack of zoom....head tracking works but you can't get close enough to read the HUD).

 

Also, what DK2 runtime version is everyone using with DCS? is it safe to continue using the .5 beta drivers on DK2 with DCS? Or did everyone have to upgrade to .6 or .7? Elite:Dangerous doesn't work with .7 and they say they don't plan to fix it! Trying to find a version that's lowest common denominator for all my games is getting to be a challenge.

[joebloggs]

With the latest DCS updates, can you now read the gauges using DK2? The Hud? Is the zoom fixed? (Biggest issue with DK2 in DCS was the lack of zoom....head tracking works but you can't get close enough to read the HUD).

 

Also, what DK2 runtime version is everyone using with DCS? is it safe to continue using the .5 beta drivers on DK2 with DCS? Or did everyone have to upgrade to .6 or .7? Elite:Dangerous doesn't work with .7 and they say they don't plan to fix it! Trying to find a version that's lowest common denominator for all my games is getting to be a challenge.

 

Head tracking in the Rift = Zoom. You cant get close to the digital readings in the HUD even outside of the Rift. There is a mod you can use to make readings in the HUD bigger, but this is a beta and it's not advised to use mods in 1.5. This makes crashing and trying to find bugs more difficult.

[gtrdrt]

for me all problems are fixed:

 

uninstall OC runtime

uninstall NVIDIA drivers

clean up System (CCleaner)

 

make sure dcs OB is clean

 

install OC runtime

before reinstall NVIDIA drivers: Stop OC Service, kill all OC stuff in task manager

 

set NVIDIA controlpanel to global-> Performance

 

run dcs still in vista sp2 mode and vsync off

 

game all day long :)

OC runtime=Oculus Runtime?

[Frusheen]

With the latest DCS updates, can you now read the gauges using DK2? The Hud? Is the zoom fixed? (Biggest issue with DK2 in DCS was the lack of zoom....head tracking works but you can't get close enough to read the HUD).

 

Also, what DK2 runtime version is everyone using with DCS? is it safe to continue using the .5 beta drivers on DK2 with DCS? Or did everyone have to upgrade to .6 or .7? Elite:Dangerous doesn't work with .7 and they say they don't plan to fix it! Trying to find a version that's lowest common denominator for all my games is getting to be a challenge.

 

All gauges are more readable than before. The hud is legible if you lean in a bit or can be made to show larger characters with a mod if needed. As for zoom being "fixed" - No and in my view it shouldn't be. What's the point of going to all the trouble of direct mode and higher FPS to reduce latency and sim sickness only to ruin it and make everybody nauseous with a zoom button!

 

1.5 uses .7 and Frontier Have said they are 100% committed to supporting the rift in elite dangerous.

Edited October 11, 2015 by Frusheen

[Crunchy]

1.5 uses .7 and Frontier Have said they are 100% committed to supporting the rift in elite dangerous.

 

Are you saying 0.7 works with Elite Dangerous? Because as far as I know it doesn't. Lets hope they are committed to supporting Rift still because I won't be buying Horizons until they implement 0.7 or the latest runtime. I'm getting fed up of buying game that claim to support Oculus and then as soon as a new Runtime arrives they abandon it until next year and CV1.

[gtrdrt]

...I still get crashes when mission is loading...

 

I don't remember who posted it or where it was posted, but it has been suggested that you disable your internet connection before running DCS. That's been working pretty well for me as a way to avoid the crashes. Plus, I just discovered that once you've got the program running, you can then re-enable your internet connection and log in, and then you're back in business. I hope it works well for you and others too.

[gtrdrt]

New Gamma has made a massive difference on the rift. Great job:thumbup:

Is the New Gamma adjustable? If so, where? Other than there being a massive visual difference, which I don't seem to be able to see, is there any other indicator that tells you whether or not the New Gamma is on?

[Kayos]

Are you saying 0.7 works with Elite Dangerous? Because as far as I know it doesn't. Lets hope they are committed to supporting Rift still because I won't be buying Horizons until they implement 0.7 or the latest runtime. I'm getting fed up of buying game that claim to support Oculus and then as soon as a new Runtime arrives they abandon it until next year and CV1.

 

I think Elite Dangerous is for a different thread.