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

[Mark D]

Can I double check :

1) in Direct mode the Oculus config utility does detect your DK2 ie you can press the 'show demo scene' button etc?

2) in Extended mode the HMD light turns blue and in the HMD lenses you see your PC desktop - but the Oculus config utility still does not detect it?

 

[Jonathan E]

Yes and yes.

 

[NoiseCrime]

A timely reminder about the PSU, I unplugged it this morning to plug my laptop in
You were partially right Mark

Still doesn't work though...

View attachment 354

Sorry I had to go out for a few hours, looks like Mark has been helping you though, saying all the right things.

It is strange that the rift itself is not detect in extended mode. Does the rift appear in your display panel (do you have nvidia gpu?) for a long time I couldn't get it to show on my new PC there, where I was trying a direct HDMI connection for the first time. As I said in the end I think unplugging both HDMI and USB to use a different one got it to work.

You mention not having DVI or HDMI on some systems, what are you using to connect it? I feel sure if we could just get the Oculus config to see it in extended mode everything else would work.

Few other things, have you updated the firmware yet? Have you tried, and I hate to say this, un-installing all drivers/config etc, and re-doing the whole install process? I hate saying that since its often said when people have no other valid ideas to try

Some more info would be nice, PC system, gpu model etc, latptop or desktop, connectors.

 

[Adam Lusardi]

That's correct the game runs at 75fps on both.
One displays 75fps at 75hz and the other displays 75fps at 60hz.
You don't need to have a 75hz screen to run 75fps. You just need a 75hz screen to see the benefits of 75fps.

So I set my rift up in direct mode, (rift dvi (display 2), TV Hdmi (display 1)) in the games settings rift mode only allows me to select 60Hz max. (AMD user)
Wonder if I need to force it somehow?

 

[Jonathan E]

Sorry I had to go out for a few hours, looks like Mark has been helping you though, saying all the right things.

It is strange that the rift itself is not detect in extended mode. Does the rift appear in your display panel (do you have nvidia gpu?) for a long time I couldn't get it to show on my new PC there, where I was trying a direct HDMI connection for the first time. As I said in the end I think unplugging both HDMI and USB to use a different one got it to work.

You mention not having DVI or HDMI on some systems, what are you using to connect it? I feel sure if we could just get the Oculus config to see it in extended mode everything else would work.

Few other things, have you updated the firmware yet? Have you tried, and I hate to say this, un-installing all drivers/config etc, and re-doing the whole install process? I hate saying that since its often said when people have no other valid ideas to try

Some more info would be nice, PC system, gpu model etc, latptop or desktop, connectors.

Yes, in extended mode I can see the Rift

In windows screen util

View attachment 358

and Nvidia util...



Yep, uninstalled drivers, rolled Nvidia back 3-4 versions and back one at a time etc.

Desktop system
AMD FX6300
8GB mem
WIn x64 8.1
GTX 780
Tried HMDI and both DVI connectors.

 

[Mark D]

So I set my rift up in direct mode, (rift dvi (display 2), TV Hdmi (display 1)) in the games settings rift mode only allows me to select 60Hz max. (AMD user)
Wonder if I need to force it somehow?

Hi Adam,

Sorry for the stupid question - can I double check if the game is ED? If yes, I had the same problem. To me it appeared in DK2 Direct mode with ED I could only choose resolutions / refresh rates native to my monitor (so personally I could choose 75Hz but only at a lower res).

KING5TON gave me the solution which was an app called CRU (custom resolution utility). As you hinted this allowed me to force ED to the DK2 native resolution / refresh rate.

However at the end of the day I am under the impression ED will not work properly at this time with the DK2 in direct mode. Something very odd means KING5TON and I are only getting 37.5fps (exactly half of what we would expect). If you get better I would be very interested Possibly Beta 3 'might' fix it?

 

[STABB666]

Hi Adam,

Sorry for the stupid question - can I double check if the game is ED? If yes, I had the same problem. To me it appeared in DK2 Direct mode with ED I could only choose resolutions / refresh rates native to my monitor (so personally I could choose 75Hz but only at a lower res).

KING5TON gave me the solution which was an app called CRU (custom resolution utility). As you hinted this allowed me to force ED to the DK2 native resolution / refresh rate.

However at the end of the day I am under the impression ED will not work properly at this time with the DK2 in direct mode. Something very odd means KING5TON and I are only getting 37.5fps (exactly half of what we would expect). If you get better I would be very interest Possibly Beta 3 'might' fix it?

The only time I've seen output matching exactly 50% of a refresh rate is when a progressive scan device is receiving an interlaced signal. Perhaps that app is sending it interlaced to achieve that forced resolution? (though I don't know why...c'mon Oculus, send me one already)

 

[Mark D]

The only time I've seen output matching exactly 50% of a refresh rate is when a progressive scan device is receiving an interlaced signal. Perhaps that app is sending it interlaced to achieve that forced resolution? (though I don't know why...c'mon Oculus, send me one already)

That would make sense. However before installing the app I had ED and my monitor both set to 60Hz with the same result 37.5fps. I have read others who had monitors set to 120Hz and apparently vsync forced their demos to 37.5fps - switching their monitor to 60Hz fixed it for them. Other direct demos (eg Sightline) work fine for me 75fps. So it 'appears' to be DK2 direct mode and ED. That's why I was wandering if anyone else was getting above that figure.

The good news for me is DK2 extended mode and ED works great still so I'm happily using that.

 

[Togg]

i recently made the decision to get a DK2 when my next pay period comes around, (ordering it from OR, not paying a premium for a used buy now ebay) so when it does come in (6-8 weeks is listed on the site) i will be using this thread to troubleshoot any issues i have.

side note... i'm not the best with technology so i may have to pester a few of you more knowledgeable individuals.

 

[STABB666]

That would make sense. However before installing the app I had ED and my monitor both set to 60Hz with the same result 37.5fps. I have read others who had monitors set to 120Hz and apparently vsync forced their demos to 37.5fps - switching their monitor to 60Hz fixed it for them. Other direct demos (eg Sightline) work fine for me 75fps. So it 'appears' to be DK2 direct mode and ED. That's why I was wandering if anyone else was getting above that figure.

The good news for me is DK2 extended mode and ED works great still so I'm happily using that.

Wihout the hardware in hand, it's best guess- but reading someone else's code over here: http://energylab.hpa.edu/public/brain/oculus/OculusSDK/LibOVR/Src/OVR_CAPI.h

With some other poking around here https://developer.oculusvr.com/forums/viewtopic.php?f=37&t=12760 and here https://developer.oculusvr.com/forums/viewtopic.php?t=16150&p=211678 that seems to indicate that ovrDistortionCap_Overdrive is being used to offset smearing on black, which is probably resuting in it being heavily called in ED for the background.

So the vsync link problem then makes a bit of sense- Distortions are passed through ovrHMD to get this fix for true black, and are then being sent to a buffer, which might not be getting swapped in time, which could in turn affect the frame timing and subsequently fps. Maybe at some point we can use FRAPS to capture and export to FRAFS to track the response times from the headset while running ED.

Not clear on why it settles at 37.5 though, but it's clearly somehow linked to vsync and the native res of the OVR.

 

[Adam Lusardi]

Hi Adam,

Sorry for the stupid question - can I double check if the game is ED? If yes, I had the same problem. To me it appeared in DK2 Direct mode with ED I could only choose resolutions / refresh rates native to my monitor (so personally I could choose 75Hz but only at a lower res).

KING5TON gave me the solution which was an app called CRU (custom resolution utility). As you hinted this allowed me to force ED to the DK2 native resolution / refresh rate.

However at the end of the day I am under the impression ED will not work properly at this time with the DK2 in direct mode. Something very odd means KING5TON and I are only getting 37.5fps (exactly half of what we would expect). If you get better I would be very interested Possibly Beta 3 'might' fix it?

Thanks Mark,
I think I will leave it to see what happens later, I did see the link to CRU but as it works in extended for the moment don't want to play around too much. (Yes :smilie: its for ED, don't get any time for other games)

 

[PacalB]

I'm one of the ones that STILL can't get the rift to work in extended desktop mode so I have to use direct to rift... I hope they don't break it in beta 3....

Count yourself lucky, the dk2 I have here won't come out of 'no signal mode' no matter what I try or do. A constant orange light since I got it 2 weeks ago. Mailed Oculus support but haven't heard a word from them. Right now, I have a rather expensive plastic paperweight sitting on the side table.

 

[Jonathan E]

Mail them again, they do respond eventually. If you bought on a credit card, you may need to open a dispute and re-claim the money and let them sort it out.

 

[Adam Lusardi]

Count yourself lucky, the dk2 I have here won't come out of 'no signal mode' no matter what I try or do. A constant orange light since I got it 2 weeks ago. Mailed Oculus support but haven't heard a word from them. Right now, I have a rather expensive plastic paperweight sitting on the side table.

Oh no....have you tried everything? USBs leads etc etc

 

[Dr Wookie]

I'm really teetering on the edge of getting a DK2! Hopefully I'll be able to have a gander at the premiere... I'll be in the UK for 5 weeks , arriving in time for the 22nd so maybe if I go for it it will be waiting for me when I get back . I had a go with DK1 a while back, and with the HD prototype at E3, but I heard that some people think that the DK2 screen is a bit of a step back from the prototype. Them again, the newest iteration is said to be a significant improvement on DK2... Aargh, my brain!

So many people seem to say "oh you should definitely wait, but I could never go back to monitor, wheeee!"

 

[KING5TON]

I'm really teetering on the edge of getting a DK2! Hopefully I'll be able to have a gander at the premiere... I'll be in the UK for 5 weeks , arriving in time for the 22nd so maybe if I go for it it will be waiting for me when I get back . I had a go with DK1 a while back, and with the HD prototype at E3, but I heard that some people think that the DK2 screen is a bit of a step back from the prototype. Them again, the newest iteration is said to be a significant improvement on DK2... Aargh, my brain!

So many people seem to say "oh you should definitely wait, but I could never go back to monitor, wheeee!"

Do you own or can you afford a decent GPU?
Can you afford to buy a DK2 now and a consumer version next year?
Could you also afford to buy a new GPU (Maybe SLI if VR SLI works out or AMD bring out something better) next year when the consumer version arrives if it needs it?

If yes to all then go for it.
Nothing holding you back other than spending the money.
If you can't afford it I'd recommend waiting till next year and getting the consumer version. It will be better in every way and if you can just afford a DK2 you will be gutted when they release.
If you don't have a decent machine it's also worth saving up for when consumer version releases, although performance will hopefully improve I think the probable increased specification of consumer version will make current machines weep.

 

[Dr Wookie]

Do you own or can you afford a decent GPU?
Can you afford to buy a DK2 now and a consumer version next year?
Could you also afford to buy a new GPU (Maybe SLI if VR SLI works out or AMD bring out something better) next year when the consumer version arrives if it needs it?

If yes to all then go for it.
Nothing holding you back other than spending the money.
If you can't afford it I'd recommend waiting till next year and getting the consumer version. It will be better in every way and if you can just afford a DK2 you will be gutted when they release.
If you don't have a decent machine it's also worth saving up for when consumer version releases, although performance will hopefully improve I think the probable increased specification of consumer version will make current machines weep.

Hi KING5TON, at the moment I have an i7-4770, a reference but factory-over clocked 970, and 8 GB of RAM. I bought a small form factor PC that constricts the physical size and power of the GPU, and the reference model is required given the airflow in the case. I could see myself getting a DK2 for now, then maybe getting CV1 a year or two down the line, possibly with a newr, more efficient and powerful GPU. However, I wouldn't necessarily jump on the CV1 as soon as it came out, especially if the 970 wouldn't cut it.

 

[NoiseCrime]

Yes, in extended mode I can see the Rift

Hmm, well that is strange and I'm afraid i'm out of ideas. Can't imagine how frustrating this must be for you since outside of Oculus config everything appears correct.

I don't think you stated if you'd updated your firmware on the DK2, that would be interesting to know.
One other thing is do you get the Oculus device information when using direct mode? That is the information about firmware, model, serial num etc?
How many USB devices do you have connected? Have you tried with disconnecting as many as possible?

My thinking here is that the display component of the rift is working (i.e HDMI to your PC) as it shows in display options, where as in the config it is more likely to be based on the USB connection of the rift to your PC, so that my be where the issue lies?
Do you have USB 2 and USB 3 ports? Have you tried the DK" in both?

 

[NoiseCrime]

Hi KING5TON, at the moment I have an i7-4770, a reference but factory-over clocked 970, and 8 GB of RAM. I bought a small form factor PC that constricts the physical size and power of the GPU, and the reference model is required given the airflow in the case. I could see myself getting a DK2 for now, then maybe getting CV1 a year or two down the line, possibly with a newr, more efficient and powerful GPU. However, I wouldn't necessarily jump on the CV1 as soon as it came out, especially if the 970 wouldn't cut it.

I my experience this should be ample for DK2 and ED as long as you disable a few settings such as Ambient Occlusion ( no idea why they offer this, it really wont have much effect outside space stations or cockpit, and even with it enabled I find it hard to see much difference), AA mainly as there are better ways, e.g. SSAA or DSR (nvidia tech) and set shadows to medium or low. It wont maintain 75 fps but it will be close to it or bette for most of the time, but if you find the experience uncomfortable then you'll need to drop down to low settings. However be aware you will never avoid micro stutters or periodic framedrops, its the nature of games when having to load new data or wait for online data. A SLI setup may provide a better overall experience, but frankly until nvidia release its VR Direct tech I don't think its worth it currently, I also feel its probably better to wait until CV1 release before investing ina sli set up since if they increase resolution and/or framerate it will demand even better gpu's than we currently have. Hopefully though by that point ED will be more optimised and perhaps sli GTX970 will be capable for CV1.

 

[Jonathan E]

Hmm, well that is strange and I'm afraid i'm out of ideas. Can't imagine how frustrating this must be for you since outside of Oculus config everything appears correct.

I don't think you stated if you'd updated your firmware on the DK2, that would be interesting to know.
One other thing is do you get the Oculus device information when using direct mode? That is the information about firmware, model, serial num etc?
How many USB devices do you have connected? Have you tried with disconnecting as many as possible?

My thinking here is that the display component of the rift is working (i.e HDMI to your PC) as it shows in display options, where as in the config it is more likely to be based on the USB connection of the rift to your PC, so that my be where the issue lies?
Do you have USB 2 and USB 3 ports? Have you tried the DK" in both?

Yes, the OCU displays the normal info as below, and I have tried re-loading the firmware.



I have removed everything apart from USB keyboard, and tried every combination of USB port usage