Oculus Rift with DCS World Discussion

Anyone tried night flying with the rift? Looks too light, not dark enough, I think.

Not sure if this was mentioned but the slider for pixel density doesn't seem to be making any quality adjustments that I can see. The setting in the dev kit works great though for clearing up the gauges. I'm assuming that the slider is there but isn't actually doing anything yet?

Jar: same for me, set at 2 and much better than stock view and the same as when using the debugging tool. I hope they hot patch to fix the view issues. I can not seem to hit the sweet spot on my own. Really bad in the F-86, can not use the weapons cause the view is so screwed up. P-51, Dora , Huey and Gazelle not too bad but still not as good as before the patch.

Not sure if this was mentioned but the slider for pixel density doesn't seem to be making any quality adjustments that I can see. The setting in the dev kit works great though for clearing up the gauges. I'm assuming that the slider is there but isn't actually doing anything yet?

Where do I find this pixel density

On the VR tab of the options menu - only available in 1.5.4 Beta until next Friday-ish though.

On the VR tab of the options menu - only available in 1.5.4 Beta until next Friday-ish though.

Thanks I will take a look so no need to use oculus debug tool. Are they removing this option then.

The option isnt being removed.

I think he meant the 1.5.4 is only available on open beta, till friday at the earliest.

The option isnt being removed.

 

I think he meant the 1.5.4 is only available on open beta, till friday at the earliest.

So does this mean I don't have to use the oculus debug tool then. Sorry to ask.

I'm finding that my saved eyepoint positions are not getting saved when I exit out of DCS and start a new session. This was in v2 and in the v1.5 beta. I do not have the issue with the other v1.5 version.

I see we got same speaker set and rudder pedals :) I wonder what's on the platform :)

 

By the way I just got my wife to take photo of me while holding a ruler under my nose, looks like my IPD is 69.8mm (just on the limit of 70 for OR) :music_whistling:

Has it arrived yet Kuky? I am thinking about a 2nd one for dogfighting etc.

So does this mean I don't have to use the oculus debug tool then. Sorry to ask.

Correct, no need to use debug tool.

Well so far I am blown away with the CV1, I am very surprised to find one of my favourite games I have played so far has been Chronos which I scoffed at when I first saw it "third person game in VR... pointless" however it is a lot of fun!

DCS is performing better than I could have hoped with my "below spec" 780, it struggles a bit with pixel density set to 2.0 so I need to play about with the settings however I have flown the P-51, 109, 190 and Gazelle. They have all been fun to fly, especially the Gazelle I can see myself flying that helicopter more and more.

Dogfighting online I still need to check out however I have flown the WWII fighters and have not had an issue with singleplayer dogfighting, spotting will be an issue however the immersion is just so incredible.

VR has almost certainly improved my flying, I think it is the real appreciation of depth that does it.

Mine arrives tomorrow; I'm literally quivering with anticipation!

I've not been able to fly for some time due to work and a house move, so I'm a bit of touch. I have DCS on steam, but also NTTR. Which has the best support for Rift?

I'm finding that my saved eyepoint positions are not getting saved when I exit out of DCS and start a new session. This was in v2 and in the v1.5 beta. I do not have the issue with the other v1.5 version.

Reported

So the pixel density slider in DCS is working? I don't see any difference when using the setting in DCS but with the SDK the change is quite evident. As far as the view problem I just modified the borked .lua files for each aircraft and it fixes that wonky problem. I'll have to try the aero enabled setting to see if that clears up my vegetation ghosting issue that is still remaining. The mesh issue on hills with floating textures has always been there and it would be nice to get that cleared up too. I only see it in 1.5.

Reported

Thank you :D :thumbup:

So the pixel density slider in DCS is working? I don't see any difference when using the setting in DCS but with the SDK the change is quite evident. As far as the view problem I just modified the borked .lua files for each aircraft and it fixes that wonky problem. I'll have to try the aero enabled setting to see if that clears up my vegetation ghosting issue that is still remaining. The mesh issue on hills with floating textures has always been there and it would be nice to get that cleared up too. I only see it in 1.5.

It does work and it does make a difference. I get a HUD that's almost "crisp" to read with 2.0 but the hit on frame rates is too much for me. I run it at 1.5 and live with the balance.

So the pixel density slider in DCS is working? I don't see any difference when using the setting in DCS but with the SDK the change is quite evident. As far as the view problem I just modified the borked .lua files for each aircraft and it fixes that wonky problem. I'll have to try the aero enabled setting to see if that clears up my vegetation ghosting issue that is still remaining. The mesh issue on hills with floating textures has always been there and it would be nice to get that cleared up too. I only see it in 1.5.

you game might not be saving the settings.

Also, regarding Oculus/VR and SLi:

cybereality said (He's Part of The Oculus Team):

So, I asked one of the lead engineers here at Oculus and he assures me that multi-GPU configurations will result in no gains in VR. Both AFR and SFR rendering are not compatible with the way VR rendering is handled. However, the conflicts should be gone. Meaning if you are running multiple graphics cards, you can still run VR games without having to disable the second card. But, you should not receive any performance benefit.

 

That said, there are ways to potentially make multi-GPU to work, provided you're coding your own engine. Both Nvidia and AMD have proprietary APIs to target multiple cards in VR, and in DirectX 12 (and probably Vulkan) developers can code their own custom multi-GPU code allowing for more novel optimizations. But, as far as I know, there aren't any released games that take advantage of these advanced features in VR.

So as far as Oculus' API Goes, SLi/CrossFireX is not supported in AFR or SFR.

This also Rules out VR Works and Liquid VR API's, those API's/Libraries are separate from the Oculus API, and meant for people that are programming their own VR Graphics Engine to be used without Oculus's API.

Whether or not ED can work around it for VR or not, I dunno, but if Oculus' Engineers are saying both API's and Multi-GPU Methods wont work due to how their are rendering in their API, that I doubt there would be a Simple Workaround.

VR has almost certainly improved my flying, I think it is the real appreciation of depth that does it.

Whichever the reason, now I can make landings with a 180 degrees turn before touch down with the Huey that I could only dream of before.

So the pixel density slider in DCS is working? I don't see any difference when using the setting in DCS but with the SDK the change is quite evident. As far as the view problem I just modified the borked .lua files for each aircraft and it fixes that wonky problem. I'll have to try the aero enabled setting to see if that clears up my vegetation ghosting issue that is still remaining. The mesh issue on hills with floating textures has always been there and it would be nice to get that cleared up too. I only see it in 1.5.

I can't get the SDK to work iv transferred the file into c: programmes 86 but no luck

Sent from my iPad using Tapatalk

I can't get the SDK to work iv transferred the file into c: programmes 86 but no luck

 

 

Sent from my iPad using Tapatalk

Run the debug tool, select 'Layer' in the 'Visible HUD' drop down. Put the Rift on to see what pixel density it's running at.

I've found I need to restart Oculus Home to get it to change when using the debug tool. DCS also works fine changing it without the tool.

Ok il give that ok thanks

Run the debug tool, select 'Layer' in the 'Visible HUD' drop down. Put the Rift on to see what pixel density it's running at.

 

 

 

I've found I need to restart Oculus Home to get it to change when using the debug tool. DCS also works fine changing it without the tool.

Great that worked just wondering where is the pixel slider in dcs now.

Options menu, far right is a VR tab

Options menu, far right is a VR tab

Funny I don't have it

Has it arrived yet Kuky? I am thinking about a 2nd one for dogfighting etc.

Not yet... maybe sometime later this week :)

EDIT: YES! IT JUST GOT DELIVERED THIS MORNING !!!! :bounce: