Frusheen

Ok I'm two days in with DK2. DCS specific issues I'm seeing. Cons: - direct HMD access not available. - I still can't get my mouse click to work. I have the yellow crosshair cursor but no labels appear on switches, no green mouse over icons and no way to click on anything once in the rift display and menu. - Also no multiplayer access. - occasional juddering cockpit Pros - tracking, warp and scale all very well implemented resulting in fantastic immersion. Let's hope an update comes at some stage. As far as rift goes. Higher FOV and much higher resolution are needed. I don't think 1440p will be sufficient for non vr designed games. In contrast games designed with vr in mind are probably ok at 1440p. Elite Dangerous for example looks incredible.

No it doesn't help. Thanks for the tip though

Its really weird. The cursor is rendered properly. Even when I hit ESC I cannot click on any of the menu items in the rift screen. To launch a mission I have to hit Pause/Break key to start a flight as I can't click on the 'ok' button. I can see the cursor fine its just not recognising the mouse click. I am using extended mode (Rift is also non primary). I thought it was something simple but I'm really stumped. I've to right click the DCS taskbar icon on my main monitor to exit a flight. When back on the main DCS screen on my monitor the mouse works fine again. DCS is working great in the DK2 besides this issue. I slowed the P51 and opened the canopy at a few thousand feet. Leaning and looking out the side of the cockpit is fantastic. I bailed out for fun and that was a real rush as you climb out of the seat and jump! Little touches like sitting up in your seat and seeing your helmet appear in the rear view mirror or leaning to look around the window pillar in the Huey... Fantastic.

Had a blast with the Huey and p-51. The tracking is fantastic. Resolution is much better but not nearly high enough yet. FOV also needs to be higher (not an easy issue to solve). Colour and contrast are much better. I had a major issue. Usb cable was not making proper contact. The rift kept turning off. I solved it with a bit of hot glue. As I'm using extended mode I have another problem. My mouse cursor is working but mouse clicks aren't being recognised. It has to be something simple. I've only had it a couple of hours so I'll probably figure it out. I tried the A-10. Looks beautiful but not usable for anything other than pleasure flights.

The flip side is they also hope to increase FOV which will further reduce pixel density and make the perceived resolution worse. As a matter of interest what does a typical set of NVGs end up at on the Snellen scale?

I'm the same. I only fly helicopters in dcs so HUD issues don't bother me. I'd imagine the p51 and Dora will also be flyable. I'm looking forward to my delivery tomorrow.

Have you rotated your rift display in nvidia control panel?

Thanks Wags. Hopefully it is as simple as recompiling and doesn't require any code adjustment. It does look like Oculus are also working on a fix.

That does seem to be the major issue people are seeing. It might not be so bad in dcs but games like elite dangerous must really suffer.

I'm not sure if the DK2 problems being reported are AMD related. I'll know soon enough as I'm running Nvidia. If Wags could install the runtime 0.4, SDK and firmware update it will tell for sure.

This is the official Oculus message relating to UE4. I suspect DCS has the same issue. On top of that the headset also had a firmware upgrade released. I'm not sure if that would need to be avoided. I just hope Wags has a hotline to Oculus HQ and it will have all been fixed by Tuesday so I can avoid the above hack. I did ask about this in the thread earlier in the week. I found it odd that oculus delayed release by a week to finish the SDK yet official DCS support was ready!

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.

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

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.

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.

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.

Thanks for checking.

I don't expect massive improvements over DK1. The resolution is not high enough yet. Maybe by consumer release but not in the dev kits. Just my opinion. Due to the pixel arrangement of OLED in dk2 it has lower perceived resolution than the HD prototype (Crystal Cove). I'm not expecting to be completely blown away. The Oculus philosophy that games need to be designed for VR may mean a few iterations before the likes of DCS or other monitor based games will be entirely usable. I'm thinking MFDs radios etc.. I'll know next week.

For DK2 positional tracking? Ok that's news to me. Great!

Mine is on the way also. I hope we won't be playing the waiting game for 1.2.9 to have support for it in dcs? I can't take much more waiting! Haha

I'm fairly sure they already have them. They've stated they were testing DK2 integration in 1.2.9. I posted the link a few days ago.

That's not what I meant. If you update DCS to DK2 compatability (1.2.9) then the DK1 may not work in game anymore as DCS will be using the newer SDK. I wasn't t referring to existing DK1 games and demos. I researched it further and it seems DK1 will still work with software compiled for DK2 (just without DK2 exclusive features). The reason I flagged it as a possible issue is that 1.2.9 will likely be available before many of us have our DK2. Anyway it seems to be a non issue so disregard.

https://m.facebook.com/story.php?story_fbid=10154430712040341&id=441639040340 EDIT: in the comments On a side note DK1 owners may want to avoid the 1.2.9 update. If it is using a DK2 SDK then DK1 support may no longer work.

Good news - 1.2.9 should introduce DK2 support and it is nearing release. Hopefully that means not much waiting around for those who are in the first batch of shipments. I hope I'm one of them!

You sure?