Got that CV1 finally.

The setup went smoother than ever but after that I couldn't get anything other than Oculus stuff to show on the display. So ED didn't appear on the display and neither did the SteamVR tutorial thing.
:/

hmm, that could actually be more promising that it sounds. If SteamVr isnt running on it either then it could just mean that the current release of steamvr doesn't work with the latest CV1 runtime?

given that the latest beta steamvr release today includes fixes/updates for the rift then they do seem committed to supporting it so we may just need to be patient for the future update that has 1.x support.
 
I wonder if anyone at valve has a CV1 and 1.1+SDK?.

one would hope so given the size of the organisation and their importance in pc gaming.
 
Probably just a stab in the dark, but have you tried the tracker in a different USB3 slot?
Of course

Uninstalling SteamVR (deleting the SteamVR user folders/files) and re-installing and re-configuring
No, I fail to see how that would help.

is Windows 10 fully updated?
Almost, last installed updates were January.

hmm, that could actually be more promising that it sounds
None of the changes in the SteamVR changelog point to why it could be broken for me now, so I don't think we can infer such things

I wonder if anyone at valve has a CV1 and 1.1+SDK?
Oculus are giving out a lot of dev samples of the HMD now so I'd guess so. It's the touch controllers they're really secretive about.
 
Last edited:
None of the changes in the SteamVR changelog point to why it could be broken for me now, so I don't think we can infer such things
my point was that its the other way around.

(im basing this on my understanding of your most recent previous posts, clearly i dont know everything you've tried, so i apologise if ive missunderstood and thank you for taking the time to report your experiences!)

my understanding was you tried it with the firmware that came with sample CV1 and run time 1.0 and after some fiddling, Steamvr and ED sort of worked but not very well?
you then patched the firmware and thus had to upgrade to runtime 1.1 and now neither of them work at all?

im not suggesting that the recent change to steamvr have broken it im just saying that it sounded like steamvr wasn't 100% compatible with the original cv1 firmware/runtime you had and is not compatible at all with the updated cv1 firmware/runtime? if this is the case then would that explain why ED is not working? (ie we're in a similar backwards compatibility situation to when they went from runtime 0.5/0.6/0.7?, except this time its new firmware and a new runtime?)

i brought up the recent update just to mention that as we see in the latest release of steamvr updates for improving rift support, they are clearly still working on updates specifically aimed at the rift so it would seem likely that we will see at some point in the future an update to steamvr to include the cv1 release firmware/runtime compatibility? (which i would guess would then leave us in the same place we are with DK2/0.8 at the moment?)
 
Last edited:
i brought up the recent update just to mention that as we see in the latest release of steamvr updates for improving rift support, they are clearly still working on updates specifically aimed at the rift so it would seem likely that we will see at some point in the future an update to steamvr to include the cv1 release firmware/runtime compatibility? (which i would guess would then leave us in the same place we are with DK2/0.8 at the moment?)

indeed... I too think these steamVR updates with changes specifically for DK2 can only be a promising sign. IF Valve were not interested in supporting the oculus rift they would not waste time and effort on getting it working in 0.8 on the DK2 imo... the fact that they are surely must mean that are at least some what committed to the oculus consumer version, all barring some huge blocker that oculus do with their updated SDK (again!) (*surely that wont happen again? *)
 
Very promising indeed, I am really hoping that is the case for everyone who ordered the new device. I did not myself going to use mom's advice and kind of see how things pan out but would very pleased to see a nice interface for all the others while they wait for the real deal runtime.
 
my understanding was you tried it with the firmware that came with sample CV1 and run time 1.0 and after some fiddling, Steamvr and ED sort of worked but not very well?
you then patched the firmware and thus had to upgrade to runtime 1.1 and now neither of them work at all?

Not quite. I never managed to get ED running with 1.x runtime :(
Default Rift firmware + 0.8 runtime + older SteamVR = working with some glitches.
Updated Rift firmware + any 1.x runtime + any SteamVR = not working.
And yes - now nothing works with SteamVR.

Actually I hadn't seen all the changelog in SteamVR .. I see now what you mean..
lets really hope something happens there.

I got sick and tired of AMDs horrible Crossfire support and ordered a 980Ti . Maybe I'll have better luck with the 'green camp'.
 
Hi
Out of curiosity when it worked could you also choose 1080p 75hz on the cv1 so that lower end hardwarecan run well?

Or is it locked to cv1 RES and 90hz
 
Hi ghcannon,

I play Elite with my DK2 but even with a green hud and some other tweaks I find the overall text/UI readability to be really bad. I know you said that it's much better with CV1, but how much better? If you could rate text readability using the DK2 from 1-10 and text readability using CV1 from 1-10 what would it be?
 
Having a hard time objectively measuring an abstract thing such as readability.

Still, here's a number that's not totally prooma.
if DK2 was 5/10, then the CV1 would be around a 7/10 in terms of readability of text at medium distance.
 
Yeah text wont be really great until we get better resolution. But better screens, optics and layered rendertargets will help alot until were there.
 
Last edited:
Cool, thanks man. I understand it's kind of hard to rate something like that but at least I have somewhat of an idea now :p

Also, what about text readability on the UI? You know like the Navigation panel..etc? Also, since you tried the CV1, was there a physical IDP adjuster on it? You know, where you can adjust the distance between the lenses? I feel like if I could physically adjust the lenses distance on the DK2 it would help a tone because I can't get the "sweet" spot on both lenses at the same time (I have a small IDP)
 
Last edited:
Also, since you tried the CV1, was there a physical IDP adjuster on it? You know, where you can adjust the distance between the lenses? I feel like if I could physically adjust the lenses distance on the DK2 it would help a tone because I can't get the "sweet" spot on both lenses at the same time (I have a small IDP)

Physical IPD adjustment has been known for quite some time and will do everything you asked. However there is no official word on how wide/narrow these IPD adjustment extremes are.
http://www.roadtovr.com/oculus-says-consumer-rift-has-ipd-adjustment-and-better-design-for-glasses/
 
Last edited:
Yes, as phoenix said, there's a physical IPD adjustment. It's very nice and easy to use.

Other than that - 980Ti in da house !! (... well, in da post office to precise but I'll pick it up after work)

I'll give it a shot soon and post if something has changed for the better (since I see no way it can become worse at this point)
 
Last edited:
Well the same thing happens with the 980Ti ... no image is being output to the Rift.

However, I stopped getting hardware failiures on the sensor ... really weird ...
 
Yes, as phoenix said, there's a physical IPD adjustment. It's very nice and easy to use.

Other than that - 980Ti in da house !! (... well, in da post office to precise but I'll pick it up after work)

I'll give it a shot soon and post if something has changed for the better (since I see no way it can become worse at this point)


That's nice, I knew there was an IPD adjuster but wasn't sure how well it worked. For my DK2, for now now I'm using this, https://www.shapeways.com/product/W...culus-rift-d?li=marketplace&optionId=42885500 it works alright, better then nothing I guess.

Also, did you try running older sdk with it? Did it worked or you absolutely need 0.8? Also, sorry another question...how's the space for people with glasses?
 
Last edited:
Back
Top Bottom