Oculus Rift with DCS World Discussion

[DerekSpeare]

I'd fear a malfunction like this:

 

[hansangb]

MMOne video

 

 

OMG. I'm thinking $6,000 minimum.

[Torso]

OMG. I'm thinking $6,000 minimum.

Add at least another 0 to that if not needing to up it to a six figure digit. That is designed for theme park/arcade use, not home. That is the companies target market. Just that more high use industrial engineering will make it a large ticket item.

[John Hargreaves]

This should be the latest product from DSD, c'mon Derek, you know you want to..

[hansangb]

This should be the latest product from DSD, c'mon Derek, you know you want to..

 

 

:D:joystick::pilotfly::thumbup:

[DerekSpeare]

This should be the latest product from DSD, c'mon Derek, you know you want to..

 

:pilotfly::joystick: :lol:

[John Hargreaves]

On the topic of DSD, button boxes work surprisingly well with the rift, as you have a kind of muscle memory as to where things are, and a tactile button is much better than trying to identify a key on a keyboard when you are fumbling around unsighted. It might be worth doing one aimed at VR users where the buttons all feel a little different, sizes, shapes & such, so they can be easily used without looking.

All the little hats and switches on the Warthog are like that, based on real pilots being able to find things in the dark or a smoke filled cockpit I guess. It's great being able to feel for certain switches whilst in the rift.

[dburne]

All the little hats and switches on the Warthog are like that, based on real pilots being able to find things in the dark or a smoke filled cockpit I guess. It's great being able to feel for certain switches whilst in the rift.

 

A big +1 to that, new Rift user here have had it a little over a week, all those buttons/hats on my Warthog setup I have been using for so long, are a life saver now that I am using the Rift.

[metzger]

On the topic of DSD, button boxes work surprisingly well with the rift, as you have a kind of muscle memory as to where things are, and a tactile button is much better than trying to identify a key on a keyboard when you are fumbling around unsighted. It might be worth doing one aimed at VR users where the buttons all feel a little different, sizes, shapes & such, so they can be easily used without looking.

All the little hats and switches on the Warthog are like that, based on real pilots being able to find things in the dark or a smoke filled cockpit I guess. It's great being able to feel for certain switches whilst in the rift.

This is my approach also and it works very well. +1

 

Sent from my Redmi 4 using Tapatalk

[DerekSpeare]

On the topic of DSD, button boxes work surprisingly well with the rift, as you have a kind of muscle memory as to where things are, and a tactile button is much better than trying to identify a key on a keyboard when you are fumbling around unsighted. It might be worth doing one aimed at VR users where the buttons all feel a little different, sizes, shapes & such, so they can be easily used without looking.

All the little hats and switches on the Warthog are like that, based on real pilots being able to find things in the dark or a smoke filled cockpit I guess. It's great being able to feel for certain switches whilst in the rift.

 

The entire premise of a good button controller is that the user does not need to be looking at them to use them. Any good button controller has design features which are robust and have varied tactile responses which offer the operator ease of use, and allow the right control elements to be used at the instant they are needed. Ultimately the goal is to prevent unnecessary distractions while simultaneously enhancing gameplay. The analogue design demands have been used in aircraft and auto design for decades...well, anything designed for human-machine interaction, actually...

 

I'm a big DCS-VR fan (as some may know), and have been using our own DSD button devices with DCS and VR since the 0400 runtimes :) Surely the need for positive tactile experience is essential in our components, and that's been one of the overarching demands all along. Enough about me, though...

 

Speaking of DCS and VR, what does ED have planned for DX12 support?

Edited January 23, 2017 by DerekSpeare

[John Hargreaves]

I use one of the little P2 boxes and it works great in VR, like you say, very analogue and tactile.

[hansangb]

The entire premise of a good button controller is that the user does not need to be looking at them to use them. Any good button controller has design features which are robust and have varied tactile responses which offer the operator ease of use, and allow the right control elements to be used at the instant they are needed. Ultimately the goal is to prevent unnecessary distractions while simultaneously enhancing gameplay. The analogue design demands have been used in aircraft and auto design for decades...well, anything designed for human-machine interaction, actually...

 

I'm a big DCS-VR fan (as some may know), and have been using our own DSD button devices with DCS and VR since the 0400 runtimes :) Surely the need for positive tactile experience is essential in our components, and that's been one of the overarching demands all along. Enough about me, though...

 

Speaking of DCS and VR, what does ED have planned for DX12 support?

 

 

DSD controllers are solid as well. Kudos to you Derek.

 

But I can't **WAIT** to have DX12 support in DCS. I guess it won't have for three years (judging by how long it took took) but maybe now that 2.5 can unify the branches and we ditched the old engine, it'll be faster.

 

I surely hope so.

[SkateZilla]

1.5 and 2.0 both use the same engine.

[hansangb]

1.5 and 2.0 both use the same engine.

 

Huh, I must have missed that. I always thought the 1.x was on the older engine. Regardless, afters seeing the DX 11 vs 12 video you once posted, I hope to hell ED adds DX12 support sooner rather than later!

[NineLine]

Huh, I must have missed that. I always thought the 1.x was on the older engine. Regardless, afters seeing the DX 11 vs 12 video you once posted, I hope to hell ED adds DX12 support sooner rather than later!

 

There is no info about any plans on going to DX12 currently.

[JABO2009]

guys, pls help me out regarding my system and OC in DCS.

With my system below, Im running the Causcasus map very smooth in SP and MP. I recently upgraded RAM to 16GiG.

I estimate it could also handle DCS 2.0 Nevada (which Im not owning yet) , but Im afraid the party will be over (on both maps) once I get the Rift for DCS, which is planned on the long run.

 

So, Is the above said correct ? Or shall I give the Rift a try with my "upgraded but aged system" ?

 

Pls - help ! :noexpression:

 

 

...............................................

CPU: Intel I5-2400 @ 3,1GHz

RAM: 16GB

GPU: Gigabyte Geforce GTX 960 Windforce 2X OC 4GB GDDR5

Win 7 64 bit

Mad Catz V1 Joystick / Track IR5

 

currently running DCS 1.5.X

Edited January 26, 2017 by JABO2009

[Cibit]

guys, pls help me out regarding my system and OC in DCS.

With my system below, Im running the Causcasus map very smooth in SP and MP. I recently upgraded RAM to 16GiG.

I estimate it could also handle DCS 2.0 Nevada (which Im not owning yet) , but Im afraid the party will be over (on both maps) once I get the Rift for DCS, which is planned on the long run.

 

So, Is the above said correct ? Or shall I give the Rift a try with my "upgraded but aged system" ?

 

Pls - help ! :noexpression:

 

 

...............................................

CPU: Intel I5-2400 @ 3,1GHz

RAM: 16GB

GPU: Gigabyte Geforce GTX 960 Windforce 2X OC 4GB GDDR5

Win 64 bit

Mad Catz V1 Joystick / Track IR5

 

currently running DCS 1.5.X

 

I run the rift with mine with quite high settings without difficulties and I believe your CPU is newer than mine you have more ram and same VRAM as 970. Get one ordered Pffft;)

 

PS NTTR runs better at the moment than Caucasus

[agathorn]

I am experiencing a very odd and vexing issue and wondering if anyone else has run into this.

 

I can play sometimes 30 minutes to an hour on average, but sometimes much less (as little as 10 minutes) until suddenly essentially the Rift just dies in DCS. I know it is about to happen because the view starts juddering really bad then skipping frames or freezing the view. Then about 30 seconds later the view in the Rift goes completely blank and the mirror view on the desktop freezes.

 

It **looks** like DCS has frozen but in fact it hasn't. I can continue to hear proper audio, and the flight controls still function. I just have no visuals.

 

The only way to fix it is to force kill DCS and restart.

 

My system is as follows taken from DXDiag, and Rift is CV1 with latest updates as far as I know:

Operating System: Windows 10 Pro 64-bit (10.0, Build 10586) (10586.th2_release_sec.161024-1825)

Processor: Intel® Core i7-4770K CPU @ 3.50GHz (8 CPUs)

Memory: 16384MB RAM

Card name: NVIDIA GeForce GTX 980 Ti

Display Memory: 14263 MB

[simo1000rr]

I am experiencing a very odd and vexing issue and wondering if anyone else has run into this.

 

I can play sometimes 30 minutes to an hour on average, but sometimes much less (as little as 10 minutes) until suddenly essentially the Rift just dies in DCS. I know it is about to happen because the view starts juddering really bad then skipping frames or freezing the view. Then about 30 seconds later the view in the Rift goes completely blank and the mirror view on the desktop freezes.

 

It **looks** like DCS has frozen but in fact it hasn't. I can continue to hear proper audio, and the flight controls still function. I just have no visuals.

 

The only way to fix it is to force kill DCS and restart.

 

My system is as follows taken from DXDiag, and Rift is CV1 with latest updates as far as I know:

Operating System: Windows 10 Pro 64-bit (10.0, Build 10586) (10586.th2_release_sec.161024-1825)

Processor: Intel® Core i7-4770K CPU @ 3.50GHz (8 CPUs)

Memory: 16384MB RAM

Card name: NVIDIA GeForce GTX 980 Ti

Display Memory: 14263 MB

 

it seems that your issue is related to the HDMI connector either in the VGA card or the CV1 cables. i had a semilar issue like yours but mine wouldnt even start . i would get the blanks screen the minute i start the Oculus home . My CV1 would give me black screen with the amber light on instead of white while i could hear the sound in the background. i did every thing possible from switching USB to unplugging the cable from CV1 and connecting them back , I even did a fresh install of windows 4 times. nothing worked. till suddenly i thought of switching VGA card ( i had another gtx 970 lying around ) . the minute i switched the card the CV1 went on with no problem. to make sure then i put back the old card the CV1 wouldnt work.

 

I then figured out that it was a bad HDMI connector from the VGA card. ( the bad card was ASUS sitrix 970 ).

 

to rule out your issue : start first by making sure your CV1 cables are firmly connected to the headset by removing the foamy protection. and pressing the cables in there. also run a repair for your Oculus software just in case its a driver issue. ( you do so by running the install again it will give you the option to repair)

 

if your VGA has another HDMI outlet try that and see if it solves your issue if it doesn't have ( mine didn't ) see if you can get a DVI to HDMI converter , alot of people with similar issue reported on Oculus forum that they solved it by getting this converter.

 

another thing i remembered, is your VGA overclocked , if so make sure that its not a temperature issue or overclocking issue .

[jef32]

Hi

 

On christmas day, when i've unpacked, plugged and installed my Oculus, i had the same problem. Then i've discovered than some USB additional cards, even in USB 3.0, don't support entirely the Oculus. I've plugged the USB of my oculus and captor , on native USB 3.0 outlets on my motherboard and since that, no problems at all .

Edited January 30, 2017 by jef32

[Enduro14]

One question to fellow VR's if i select in vr settings not to use mouse so only my head moves the pointer it never dissapears in the pit?... this the same for you guys aswell?

If so any way to fix that? Currently i have use mouse selected but issue i have with that is i have a buttkicker and it bounces the cursor everywhere if i center it LOL.

 

So end state want to use head pointer only but have ability of cursor to dissapear like it does when using the mouse. "feature request"?

Edited January 30, 2017 by Enduro14

[Haukka81]

Oculus Rift with DCS World Discussion

 

I Recomend to rip of Oculus default face foam, i only left that slim top foam in use -> fov is better and image is sharper too. And nose cap is gone :)

 

Just Google and you find instructios from net.

 

 

Sent from my iPhone using Tapatalk

[Enduro14]

I Recomend to rip of Oculus default face foam, i only left that slim top foam in use -> fov is better and image is sharper too. And nose cap is gone :)

 

Just Google and you find instructios from net.

 

 

Sent from my iPhone using Tapatalk

 

i just did that and what do you know i got a good improvement on my fov and things for me are slightly more clear to read in the pit. With that extra bit of fov checking 6 is alittle easier.

 

Thanks for the tip!

[eurofor]

My Rift CV1 arrived just in time for the Viggen release. Haven't had much time for DCS lately but now I'm gonna have to make time because it's so damn good. I tested the DK2 a year ago so the experience wasn't a surprise but it's still mindblowing every time and I really can't imagine flying without it now. :joystick:

[metzger]

I Recomend to rip of Oculus default face foam, i only left that slim top foam in use -> fov is better and image is sharper too. And nose cap is gone :)

 

Just Google and you find instructios from net.

 

 

Sent from my iPhone using Tapatalk

Are you removing only the foam and leave the plastic thing... Lets call it frame? Is it comfortable enough without foam?

 

Sent from my Redmi 4 using Tapatalk