Shouldn't we all (Oculus DK2 owners) be waiting for 1.3?

Sanderson · Mar 26, 2016

I've seen several threads and a lot of posts about the new update fromFD.

Shouldn't we all be waiting for 1.3 to drop before we start crying over DK2 performance? I mean, I want to play on my DK2 as much as anyone but, posting "results" without the new runtime 1.3 seems a bit like judging ammunition made for a new gun by using an old one you have laying around.

How about we wait for all the pieces before posting a bunch to do about nothing?

Tepescovir · Mar 26, 2016

er, because it was nice an smooth with 0.5 or 0.6 and is now a stuutering double image rubbish now?

777Driver · Mar 26, 2016

Sanderson said:
I've seen several threads and a lot of posts about the new update fromFD.

Shouldn't we all be waiting for 1.3 to drop before we start crying over DK2 performance? I mean, I want to play on my DK2 as much as anyone but, posting "results" without the new runtime 1.3 seems a bit like judging ammunition made for a new gun by using an old one you have laying around.

How about we wait for all the pieces before posting a bunch to do about nothing?

Performance is good with 0.8, you can tell that it's steamVR causing issues. I expect good performance with 1.3 by Monday.

RiftFlyer · Mar 26, 2016

Tepescovir said:
er, because it was nice an smooth with 0.5 or 0.6 and is now a stuutering double image rubbish now?

It's designed to work with a runtime you don't have yet! Surely people can wait two days.

Imagine the outcry if rift owners got their cv1 on Monday morning - open oculus home and download elite dangerous for the first time only to discover it doesn't work. That's exactly what would have happened if frontier had not updated on Thursday. Both Friday and Monday are holidays in a lot of countries including the uk. The update had to be posted before staff finished for the long weekend.

Is the complaint that your DEVELOPER kit should work on an outdated DEVELOPER runtime rather than support a consumer device on its first day of launch?

Hell Razor5543 · Mar 26, 2016

I don't have an issue waiting for SDK 1.3, as I only have been using a Rift DK2 for about a month. Only question I have is how to UNINSTALL Steam VR once I have SDK 1.3 installed and running.

777Driver · Mar 26, 2016

Hell Razor5543 said:
I don't have an issue waiting for SDK 1.3, as I only have been using a Rift DK2 for about a month. Only question I have is how to UNINSTALL Steam VR once I have SDK 1.3 installed and running.

Same way you uninstall any other software, either through the built in uninstaller or through the windows uninstaller.

Hell Razor5543 · Mar 26, 2016

777Driver said:
Same way you uninstall any other software, either through the built in uninstaller or through the windows uninstaller.

Slight problem with that. I am running Windows 8.1 (64 bit), and there is no uninstaller, and no sign of SteamVR in the Windows Control Panel uninstall program function. Looks like I might have to uninstall Steam.

RiftFlyer · Mar 26, 2016

You should be able to uninstall steamVR from within steam.

Mazhurg · Mar 26, 2016

Right click steamVR in the Steam tool library, select delete local files.

You're done.

gamer101 · Mar 26, 2016

Lack of SS has been reported by both 0.8 and 1.3 users.

As for those people who already have 1.3, their findings are the ones which carry the weight for the next 24 hours. Those that have 1.3 AND a CV1 will have GOD status for the next few weeks ;-)

Those that have 1.3, a CV1 AND a Vive are just too lucky ;-)

Hell Razor5543 · Mar 27, 2016

Mazhurg said:
Right click steamVR in the Steam tool library, select delete local files.

You're done.

Thanks for that. I will do it when I have downloaded the latest SDK software, once I get back for holiday. Repped.

Frank · Mar 27, 2016

Sanderson said:
I've seen several threads and a lot of posts about the new update fromFD.

Shouldn't we all be waiting for 1.3 to drop before we start crying over DK2 performance? I mean, I want to play on my DK2 as much as anyone but, posting "results" without the new runtime 1.3 seems a bit like judging ammunition made for a new gun by using an old one you have laying around.

How about we wait for all the pieces before posting a bunch to do about nothing?

There's a simple answer to that. It would've meant a whole couple of days without Elite in VR!

I was certainly doing a bit of moping and crying and looking for answers on the forums, but I wasn't crying to Frontier Developments. I've always complimented them on the support they've provided for a development kit.

spameroo · Mar 27, 2016

Frank said:
There's a simple answer to that. It would've meant a whole couple of days without Elite in VR!

I was certainly doing a bit of moping and crying and looking for answers on the forums, but I wasn't crying to Frontier Developments. I've always complimented them on the support they've provided for a development kit.

Exactly. I haven't seen much, if any, QQ directed at the devs about any of these issues or questions since the patch.

If some people choose to wait until 1.3 runtime is available that's fine, they're likely saving themselves a weekend of needless tinkering, but I don't see the point of trying to stop those of us who choose to tinker. Worst case scenario, we are wasting our own (and no one else's) time trying to fix problems that will be totally resolved with the official OVR runtime tomorrow. I think we're all aware of this risk, such as it is. On the other hand, if any of the issues we're discussing do persist under the official runtime (and there's already some evidence to suggest that this is the case), the causes or solutions we identify using 0.8 could help FD (or ourselves) to discover a more permanent fix.

The only people who are actually wasting time (their own or anyone else's) are the ones making threads like this....

xondk · Mar 27, 2016

RiftFlyer said:
It's designed to work with a runtime you don't have yet! Surely people can wait two days.

Considering there were posts almost instantly after the patch, I think the answer is "no"

Sanderson · Mar 27, 2016

spameroo said:
Exactly. I haven't seen much, if any, QQ directed at the devs about any of these issues or questions since the patch.

If some people choose to wait until 1.3 runtime is available that's fine, they're likely saving themselves a weekend of needless tinkering, but I don't see the point of trying to stop those of us who choose to tinker. Worst case scenario, we are wasting our own (and no one else's) time trying to fix problems that will be totally resolved with the official OVR runtime tomorrow. I think we're all aware of this risk, such as it is. On the other hand, if any of the issues we're discussing do persist under the official runtime (and there's already some evidence to suggest that this is the case), the causes or solutions we identify using 0.8 could help FD (or ourselves) to discover a more permanent fix.

The only people who are actually wasting time (their own or anyone else's) are the ones making threads like this....

No one is trying to stop anyone or anything. Obviously I can't reach through the internet and turn your computer off. That's just ridiculous. Having said that, expecting stellar results from an incomplete patch is a bit ridiculous also.