New PC SDK - 0.6.0.0 Beta

Raptoyd · May 17, 2015

Howl_UK said:
If you get the black flickery screen when launching in Extended just power off and on the HMD. It occasionally happens to me since updating but it's a fast workaround. I've not seen any other problems.

Tried that yesterday was still getting double image. Saw where someone said on the Oculus forum that this load automatically makes your HMD the main monitor even though it does not say it did in display properties and that he played with that and got it working. I don't feel like playing around with it put it back to what works until?

[VR] Mad Mike · May 17, 2015

and the 1st official victim of the new direction the rift SDK is announced.

ETS2 is probably removing its VR support. Devs are going to look into it but its likely VR support may be dropped until DX11 or vulkan support - which is a long time away.

fingers crossed the devs pull summat out of a hat, but even if they do, they warned that performance will take a hit.

Caspar · May 17, 2015

I'd be surprised if FD don't support this. According to David Braben, it took them less time to implement Rift support than it would have taken them to build a business case to do the work had they not developed independently.

seanwasere · May 17, 2015

I've managed to get 0.6.0.0 working now.
if I get the flickering upon starting ED, then I switch the Oculus off then on a again a few times until it stabilises,
this solution has worked on two separate occasions for me now.

rich_hard1 · May 17, 2015

Why so many people having issues with the latest SDK. Mine is ok. Works beautifully.

[VR] Mad Mike · May 18, 2015

Caspar said:
I'd be surprised if FD don't support this. According to David Braben, it took them less time to implement Rift support than it would have taken them to build a business case to do the work had they not developed independently.

I am not worried about Elite, am sure it will be fine. AFAIK the issues are because oculus are pulling the plug on DX9 support. Elite is not DX9 so even if there are issues with the current new rift drivers I am confident FD will be able to fix them.

any apps which ARE DX9 however could be in for a hard time VR wise.

I get why they are doing it. DX9 is antiquated and it makes it easier to streamline going forward, but some sort of base "compatibility mode" would have been nice, even if i warned that it was suboptimal before enabling.

seanwasere said:
I've managed to get 0.6.0.0 working now.
if I get the flickering upon starting ED, then I switch the Oculus off then on a again a few times until it stabilises,
this solution has worked on two separate occasions for me now.

out of curiosity once it IS working are their any upsides over the older SDK? I know all of us rifters are meant to be beta testers, but stuff that. I test beta software for my real job. What little gaming time I get I am sticking with what works

seanwasere · May 18, 2015

when 0.6.0.0 actually works for me, i see no better performance than with the 0.5 version of the oculus drivers unfortunately.
0.5 is the way to go for now.

Ancipital · May 18, 2015

seanwasere said:
when 0.6.0.0 actually works for me, i see no better performance than with the 0.5 version of the oculus drivers unfortunately.
0.5 is the way to go for now.

Mad Mike said:
out of curiosity once it IS working are their any upsides over the older SDK? I know all of us rifters are meant to be beta testers, but stuff that. I test beta software for my real job. What little gaming time I get I am sticking with what works

It won't produce much speedup, unless the client apps are rewritten to actually use the new features. Quite a lot has changed under the hood. Here's a slightly easier to chew summary of what has changed and why:

http://www.roadtovr.com/oculus-sdk-v0-6-0-0-now-paves-way-rift-cv1/

It's a shame that it seems to break backwards compatibility somewhat right now, though. I wonder if they will improve that at all before this version of the SDK leaves beta?

Mazhurg · May 18, 2015

Well, at least we know that FD is now aware of the issues (see sticky). Hopefully while it may not improve performance much, fixing the issues will also allow FD to start using the new layering capabilities of the driver - which should improve readability in the HUD by a fair amount.

AndreyATGB · May 20, 2015

I tried 0.6 and it works in extended like before as far as I can tell, but I need to turn it off after the game starts, turn it back on then alt-tab twice to get it to work properly. Direct mirrors to main monitor and seems to give less FPS, so I'm just going to stick to 0.5 as ED is pretty much the only thing I play with the DK2.