Oculus Rift and DCS World Discussion

[KaspeR32]

Maybe he has an AMD card? lol I really hope AMD cards will work at some point before CV1.

[blksolo]

Just broke down and ordered DK2,September isnt going to come fast enough!!

[Wags]

I read on Reddit that 1.2.9 isn't working with DK2. Perhaps ED had a different SDK version and it is an easy fix.

 

DK2 works fine here with 1.2.9 version as released to public today.

[Wags]

From Oculus's good practices guide:

 

• Your code should run at a frame rate equal to or greater than the Rift display refresh rate, vsynced and unbuffered. Lag and dropped frames produce judder which is discomforting in VR. Ideally, target 20ms or less motion-to-photon latency
  
• Game loop latency is not a single constant and varies over time. The SDK uses some tricks (e.g., predictive tracking, TimeWarp) to shield the user from the effects of latency, but do everything you can to minimize variability in latency across an experience.
  

I think DCS needs deep changes :music_whistling:

 

One of the biggest reasons for the new engine is for improved frame rates. This will help a lot in meeting comfortable performance requirements. We already support predictive tracking and Time Warp.

[LFCChameleon_Silk]

for me the occulus is a no go, I have a young child and the last thing I want is to be blinded or immersed so deeply in the sim that I am unaware of whats going on around me.

 

I'm sure its neat and all but its just not my kinda thing... I mean I'm still not even using headtracking.

[Sceptre]

I've noticed an increase in FPS whilst playing 1.2.9 compared to 1.2.8.... anyone else getting this?

[digitaljjd]

Just broke down and ordered DK2,September isnt going to come fast enough!!

 

Nice!, welcome to the wait club, I ordered mine on 20 Jun, maybe I'll make the 3rd or 4th wave. My fingers are crossed for August.

[Cowboy10uk]

same here... don't back out now :D

 

 

 

Lol, no issues there guys. Sadly UPS were unable to deliver yesterday and don't deliver on the weekend, so now they are currently saying Monday. It's hell knowing it's sat in their depot only 15 miles away from me. :(

 

All going well, first impressions should be put up on Tues. Need Monday to fly. ;)

 

Cowboy10uk

[aeliusg]

Tried calling them to see if you can drive down and pick it up?

[Cowboy10uk]

Sadly depot isn't open either. :( So have to wait until Monday no matter what.

 

Cowboy10uk

[frank7006]

So, Wags says DCS works just fine with DK2 with the new update. Has anyone tried it?

[rosco350]

Mine arrives Tuesday! I have to work but will rush home in time for UPS to try it. I'll post my experience later Tuesday if no one else does before me. I've been using DK1 with DCS for a while so I can give a good description of the differences between the two.

[SkateZilla]

one of my FSX Buddies is trying to code an input mixer

 

he has a $10 webcam mounted to his unit and plugged into the DK2 USB Port.

 

has a early alpha plugin that allows him to mix game output with webcam input with a hot key press. which allows him to see 100% game, 100% webcam or 50/50 mix. Which allows him ot use his FSX Switch boards and stuff :)

[Revelation]

Sadly depot isn't open either. :( So have to wait until Monday no matter what.

 

Cowboy10uk

 

Well at least you are almost there - I'm still pending.

 

 

Last known order switched to processing on Thursday - order date at 2:40pm PDT on the 19th. I placed my order at 2:53pm PDT on the 19th.

 

Yeah good stuff....

[Wags]

Given that some of you are now getting your DK2s, I thought this might be of interest.

 

1- As much as possible, you will want to maximize your frame rate, 75 FPS min if possible. However, given the current res of the DK2, I could not notice too many visible changes after backing off my graphic settings. You’ll want to play around with your settings to find your best balance.

 

2- Cockpits with a lot of dramatic geometry look best. I’m particularly fond of the Su-25T, UH-1H and F-86F.

 

3- Some HUDs seem more readable than others. For instance, I can read much of the HUD indication on the Ka-50 HUD. Others, not as easily. Aircraft like the F-86F, P-51D, Huey and Hip work very well given the lack of a busy HUD.

 

4- While the res is much better than the DK1 spotting targets is still almost impossible. I realize it’s a sin, but you may want to consider labels… I do!

 

5- After spending hours in the DK2, I have yet to feel at all unwell. This is compared to the DK1 that would give me headaches and nausea after just a few minutes.

 

6- The 6 DOF support really shines in DCS. The sense of presence is outstanding.

 

7- I now have a perpetual sore neck after doing several ACM flights. I’m tempted to attach a couple of grab handles to my monitor that I can grab on to in order to more easily check six! You get a much better sense of the fight geometry with the Rift.

 

8- Landing are a breeze now. You get a much better sense of speed and altitude.

 

9- After centering the view at the start of mission (KP 5), I never had to re-center.

 

10- Using a HOTAS, I very rarely had to press a key. When I did, I was able to easily look through the vents to find the needed key.

 

11- We are using predictive tracking and TimeWarp.

 

Fun times!

[LNR212]

DK2 working in Multiplayer?

[Chazz_BMF]

Somehow I feel time is going backwards. Can't wait to get my dk2. My order is still Processing :cry:

[Frusheen]

Given that some of you are now getting your DK2s, I thought this might be of interest.

 

1- As much as possible, you will want to maximize your frame rate, 75 FPS min if possible. However, given the current res of the DK2, I could not notice too many visible changes after backing off my graphic settings. You’ll want to play around with your settings to find your best balance.

 

2- Cockpits with a lot of dramatic geometry look best. I’m particularly fond of the Su-25T, UH-1H and F-86F.

 

3- Some HUDs seem more readable than others. For instance, I can read much of the HUD indication on the Ka-50 HUD. Others, not as easily. Aircraft like the F-86F, P-51D, Huey and Hip work very well given the lack of a busy HUD.

 

4- While the res is much better than the DK1 spotting targets is still almost impossible. I realize it’s a sin, but you may want to consider labels… I do!

 

5- After spending hours in the DK2, I have yet to feel at all unwell. This is compared to the DK1 that would give me headaches and nausea after just a few minutes.

 

6- The 6 DOF support really shines in DCS. The sense of presence is outstanding.

 

7- I now have a perpetual sore neck after doing several ACM flights. I’m tempted to attach a couple of grab handles to my monitor that I can grab on to in order to more easily check six! You get a much better sense of the fight geometry with the Rift.

 

8- Landing are a breeze now. You get a much better sense of speed and altitude.

 

9- After centering the view at the start of mission (KP 5), I never had to re-center.

 

10- Using a HOTAS, I very rarely had to press a key. When I did, I was able to easily look through the vents to find the needed key.

 

11- We are using predictive tracking and TimeWarp.

 

Fun times!

 

Wags can you confirm that 1.2.9 was compiled with the latest SDK, headset firmware and oculus runtime that was released a few days ago? It made some changes and several people on reddit and oculus forum have reported dcs isn't working for them. I've yet to read of a new dk2 owner getting it to work.

[Wags]

No, not since last month. It's possible these recent changes broke 1.2.9 compatibility.

[tobaschi]

No, not since last month. It's possible these recent changes broke 1.2.9 compatibility.

 

[Frusheen]

No, not since last month. It's possible these recent changes broke 1.2.9 compatibility.

 

UE4 integration along with other early access developer software has the same issue. It seems anything compiled with the 0.3sdk does not work with runtime 0.4 :-(

 

I'm not sure if oculus can fix it or if it requires recompiling 1.2.9 with the 0.4SDK.

[SkateZilla]

UE4 integration along with other early access developer software has the same issue. It seems anything compiled with the 0.3sdk does not work with runtime 0.4 :-(

 

I'm not sure if oculus can fix it or if it requires recompiling 1.2.9 with the 0.4SDK.

 

Can you Roll back to the .3 SDK?

 

I've been chatting with AMD and some people with OR, as it's not limited to DCS.

[Frusheen]

Can you Roll back to the .3 SDK?

 

I've been chatting with AMD and some people with OR, as it's not limited to DCS.

 

I don't think the SDK used by ED was ever public. I may be wrong.

[SkateZilla]

I don't think the SDK used by ED was ever public. I may be wrong.

 

i meant can the end-user/client roll back to use .3 firmware and stuff

[Frusheen]

i meant can the end-user/client roll back to use .3 firmware and stuff

 

They can. Provided the earlier version is available. The version released last week is the only publicly available DK2 version. I think (and could be corrected on this) that ED had an early build which was not publicly released.

 

There may be a possible workaround by installing a camera driver and removing the oculus 0.4 runtime. I won't have my DK2 until Tuesday so I can't check.

 

Perhaps Oculus can resolve the issue. It seems crazy that they give certain software houses early access for development and then break it on them as soon as they release the dev kit to the rest of the dev community.