ED and the Oculus Rift Developers Kit 2 (DK2) Discussion Thread

TJ, you need to disable the two windows services in task manager to get everything working again in 0.4.0

it dosent take a second.

ill be surprised if beta update later has 0.4.0 working all ready, as far as i understand this was a last minute thing with 0.4.0, we will see.

Oh an if you havnt already look back and down and lean over chair, that is a really cool feeling :)

Granite: all menu text is readable, market text almost but leaning froward a bit helps with that.
 
Last edited:

Sir.Tj

The Moderator who shall not be Blamed....
Volunteer Moderator
Sounds good. Hope you don't mind me asking - I've asked a few times and no one has answered yet:

Can you read all the menu text (and market text) without having to lean forward?

Personally at the moment its a bit fuzzy but that could be due to my poor eyesight, didn't get to use a DK1 so I can't compare tohe two.
 
Why do you say that? Phone screens (phone screens :eek:) are coming with 4K nowadays, so I think it's anything but a "sure thing". If you ask me, it's what they're waiting for.

I really don't think they're waiting for 4K - it would price the Rift out of the market in terms of PCs that were needed to run it. Yes they want the VR experience to be the best it can be, but that is too big a step (IMHO) at this time. Of course, CV1 is not "at this time" so, that may address that part but I can't see this happening even into the middle of next year. 1440p is probably the safe bet.

But OMG. :eek::eek::eek: Worth every penny.

Welcome to the VR revolution - bit good innit! :D
 

Sir.Tj

The Moderator who shall not be Blamed....
Volunteer Moderator
Why? Have you bricked it? :eek:

I don't think so. the demo in the OR CP works fine, it's just that postional tracking and head movment in ED has gone at the moment. it was fine before I updated the FW and now it's sitting in the central position.

I'm guessing it's becaouse of the FW update.

Same thing on a Rollercoaster demo I downloaded.
 
I really don't think they're waiting for 4K - it would price the Rift out of the market in terms of PCs that were needed to run it. Yes they want the VR experience to be the best it can be, but that is too big a step (IMHO) at this time. Of course, CV1 is not "at this time" so, that may address that part but I can't see this happening even into the middle of next year. 1440p is probably the safe bet.

You may be right, but what they have said so far (that I have read) is that they know now what CV1 needs to be. So they have a spec already... not sharing it yet though sadly. :(

The race to high res may not be the most important thing for them... getting it usable for long periods for everybody & building up the SDK to the point where it's easy for devs to simply drop in support for it (remember it is Facebook and we will get Farmville :rolleyes: ) might be more important.

One of the things they might want to do is integrate some graphics processing on the Rift itself, so it can upscale to 4K for people who don't have a PC capable of doing it natively.
 
I don't think so. the demo in the OR CP works fine, it's just that postional tracking and head movment in ED has gone at the moment. it was fine before I updated the FW and now it's sitting in the central position.

I'm guessing it's becaouse of the FW update.

Same thing on a Rollercoaster demo I downloaded.

Oh dear, that doesn't sound good. :(

Or do you mean that positional and head tracking works OK in the OR CP demo & it's just an issue with E: D? I seem to remember David mentioning in the Q&A that was a current issue with the game and DK2 - hopefully fixed today if they've managed to get one to test in time.
 

Sir.Tj

The Moderator who shall not be Blamed....
Volunteer Moderator
Oh dear, that doesn't sound good. :(

Or do you mean that positional and head tracking works OK in the OR CP demo & it's just an issue with E: D? I seem to remember David mentioning in the Q&A that was a current issue with the game and DK2 - hopefully fixed today if they've managed to get one to test in time.

Yep works fine on the OR CP, so I guess it's just a DK1- DK2 compatablility issue with the demos and games with the new headset.

I would like to point out now, it could very well be easily my fault. I'm having fun getting the settings right between the primary and secondary screens in window.

One min I've go teh Icons on one screen and the next it's on the other, but I'm still grinning like a madman. :D

I will be whining like mad on here later on probably. :rolleyes:
 

SlackR

Banned
Thank you for this. I've been messing around with the screw thingies on the side of the rift, no idea what they do or where the best position is for them to be, so I left them both pretty central / neutral position.

My First impressions for people sat on the fence about buying a dk2:-

I was a virgin rift user when I got home from work last night. I expected the res to be fairly decent, but those pixels looked huge to me in both the demo and ED. After a while I could just read the menu's but it was a struggle.

I noticed that if your vision wasn't centered then the image would seem to start to come apart for want of a better word, the image would start to blur /ghost and the colours would come apart unless you were looking pretty much straight at it.

Inspite of this, the sense of presence I felt was incredible. I was inside that sidewinder, which felt surprisingly roomy, everything looked great. the radar, the rest of the hud elements and instruments were something to behold.

Such a difference seeing this in the rift as apposed to track ir. I chose to super cruise towards an unknown signal that was 0.171. ly away, and I was just blissfully looking out my windows gazing at the stars. Space felt like it was just outside that window. after about 10 minutes when I was travelling at 700 and something c and still 0.141 ly from my target I was rudely intercepted.

Had a nice little fight with a sidewinder that went on for about 5 minutes, before I got my ass kicked. (stock sidewinder with single laser) and I have poor piloting skills ;)

Overall my experience was extremely positive. The consumer version is going to be great. Don't rush out and buy one though if its a choice of dk2 now and cv1 later.

Your rift definitely isn't calibrated correctly...
 
So I got the DK2 today and as a DK1 user, I can say the DK2 is a definite improvement. The higher resolution is very much needed as text is more readable. The positional tracking is only ok though as the single camera setup isn't ideal but works most of the time for most use cases. The screen door effect is still there but seems to be less noticeable, at least in the stuff I've tried. Latency is still an issue as there's still some amount of aberration and juddering even when locked at 75ps.

Only played with a few things, like the built-in scene in the config tool, the Oculus World Demo, ED (of course), and Technolust (VERY cool).

My first-hour impressions: flying around in ED is a much more enjoyable experience over DK1. Text is more readable but it's still not quite there yet. We really need 1920 per eye minimum, so 1440p just isn't going to be good enough imho.

DK2 is still a far cry from the mythical CV1. There's still simply so much more to fix, improve, and get right. We've got a very long way to go still.

DK3 in 2015? :)
 

SlackR

Banned
Anyone else having issues after extending HMD to desktop? For some reason I cant keep the setting in my NVidia Control panel for the DK2 monitor changed so that it stays set to flat/landscape, as when I check my screen resolution settings afterwards its back to portrait. Nor can I find elite, and only elite, in the 3D settings when I try to set up a profile as recommended.

Also this means that nothing works now as I dont see the main monitor through the DK2, just the extended desktop. Im using DVI connections if that makes a difference.

One thing I did notice is that if I run the world demos with the option set to Direct HMD access it works perfectly! Very very smooth with no horizontal stutter at all, which I get slightly when its extended.

Did you follow my list? The stutter is because you probably don't have v sync switched on and aren't at 75 hz.
 

SlackR

Banned
Hi
ok sorry I cant belive I am about to sound like complete noob, however if it has me confused maybe somoene else will be too at some point.

I am preparing for my rift arrival...

in the quick start guid it asks to install the SDK before hooking up the rift.

that seems simple enough, however, I have downloaded it, but i cant find any install exe. am i being really daft? if it just needs to be downloaded and not installed does it matter where it goes?

thanks

So long as the the runtime config file opens you will be set...
 
Your rift definitely isn't calibrated correctly...

Because I was messing with the screw thingies ?

Are you saying this because the pixels shouldn't seem huge, or because the image shouldn't start to come apart at the periphery ?

Ideally should I adjust the screws so that the screen is closer to the eyes or further away ? I haven't noticed a lot of difference.
 
You have to install the driver runtime - this is different from the SDK even though it has "sdk" in the name :rolleyes:.

In the downloads section on http://developer.oculusvr.com (you'll need to register to gain access if you haven't already) under Windows there should be three downloads - the driver, the SDK, and a Unity integration package.

The first download is the one you need to get it up and running.


So long as the the runtime config file opens you will be set...


ahh ok thanks guys.... I have done that. so do i noot need to worry about the other one then?

Mike
 

SlackR

Banned
Because I was messing with the screw thingies ?

Are you saying this because the pixels shouldn't seem huge, or because the image shouldn't start to come apart at the periphery ?

Ideally should I adjust the screws so that the screen is closer to the eyes or further away ? I haven't noticed a lot of difference.

The pixels should definitely not feel huge and image should tear apart like you are describing. I would suggest messing further with the IPD test...remember the screws should be all the way out when performing the test. Not sure about your eyesight but I wear glasses and use the A cups, but you could also try switching lenses.
 
I don't think so. the demo in the OR CP works fine, it's just that postional tracking and head movment in ED has gone at the moment. it was fine before I updated the FW and now it's sitting in the central position.

I'm guessing it's becaouse of the FW update.

Same thing on a Rollercoaster demo I downloaded.

so are you guys saying best NOT to update the firmware just yet?

if so does that mean i should take off the 0.4 drivers and stick in the beta ones and more stuff will work for now? i was hoping on trying the helix roller coaster

thanks
 
ahh ok thanks guys.... I have done that. so do i not need to worry about the other one then?

Not if you don't plan on developing for it, no.

so are you guys saying best NOT to update the firmware just yet?

if so does that mean i should take off the 0.4 drivers and stick in the beta ones and more stuff will work for now? i was hoping on trying the helix roller coaster

Your call, but if it were me, I would still update. It sounds like a software problem with the rollercoaster & E: D (and the latter might be fixed today). Might be worth waiting though to see how TJ and others get on once beta 1 hits.
 
Last edited:
Not if you don't plan on developing for it, no.

that is my next plan..... but not there yet. possibly losing my job at end of year so need to brush up on coding skills to make me more employable.

not sure python is a good VR language however.... but that is for another thread.

thanks again :)
 

SlackR

Banned
so are you guys saying best NOT to update the firmware just yet?

if so does that mean i should take off the 0.4 drivers and stick in the beta ones and more stuff will work for now? i was hoping on trying the helix roller coaster

thanks

If you follow the instructions then Helix works perfectly :)
 
Back
Top Bottom