New PC SDK - 0.6.0.0 Beta

Reinstalled the Firmware checking that.

Edit: It looks good but still getting double image any ideas? :S
 
Last edited:
Just wanted to try it out but the game only runs in direct mode for me. when starting in extended it switches between my monitor and the rift forever and I can't set up the rift as a primary display on windows anymore.
Edit: I hope the powerplay update will be compiled with the 0.6 SDK for better compatibility

From what I remember of the talks at GDC earlier, as as the release notes seem to indicate, is that OR is essentially making the HW invisible to the OS hence the removal (or merge?) of the extended mode.

As they progress the drivers, making the rift accessible to the drivers API only will permit them to ensure stability (and code uniformity). Unfortunately, it appears that as I suspected in my op that it breaks the current extended SDK mode that FD is using - as FD is probably doing client based rendering currently.

It would be nice if someone from the team could enlighten us on that.
 
Older unity programs still work in extended mode (though with horrible framerate, direct mode is fine). I guess the problem is this:
• Removal of client-based rendering
 
Last edited:
so how is ED performance in direct?

yes this one may be the one to eliminate or start breaching that gap between direct/extended
 
Can Raptoid or another "tester":) confirm that there is no longer a direct / extended mode setting in the rift config tool?
 
so how is ED performance in direct?

yes this one may be the one to eliminate or start breaching that gap between direct/extended

I still get only 37.5 fps in the station (edit: in direct mode). in space it is better but still worse then in extended mode with 0.5.X SDK
Edit: The extended setting is still there but the access to the screen seems limited. for me it shows a black screen except if I start a unity based program or the demo scene.
 
Last edited:
From what I remember of the talks at GDC earlier, as as the release notes seem to indicate, is that OR is essentially making the HW invisible to the OS hence the removal (or merge?) of the extended mode.

As they progress the drivers, making the rift accessible to the drivers API only will permit them to ensure stability (and code uniformity). Unfortunately, it appears that as I suspected in my op that it breaks the current extended SDK mode that FD is using - as FD is probably doing client based rendering currently.


Be nice if they at least conversed before they do this. Lots of good hindered by no communication.

It would be nice if someone from the team could enlighten us on that

- - - Updated - - -

Can Raptoid or another "tester":) confirm that there is no longer a direct / extended mode setting in the rift config tool?

Not sure if confirmed but yes I cannot seem to go one way or the other. Tried Direct thinking ahh WTH and that was not it. Double image although I will say I really like the black startup screen and the image even though doubled looks pretty good
 
From what I remember of the talks at GDC earlier, as as the release notes seem to indicate, is that OR is essentially making the HW invisible to the OS hence the removal (or merge?) of the extended mode.

As they progress the drivers, making the rift accessible to the drivers API only will permit them to ensure stability (and code uniformity). Unfortunately, it appears that as I suspected in my op that it breaks the current extended SDK mode that FD is using - as FD is probably doing client based rendering currently.


Be nice if they at least conversed before they do this. Lots of good hindered by no communication.

It would be nice if someone from the team could enlighten us on that

- - - Updated - - -



Not sure if confirmed but yes I cannot seem to go one way or the other. Tried Direct thinking ahh WTH and that was not it. Double image although I will say I really like the black startup screen and the image even though doubled looks pretty good

I am going to say YES blows that up maybe somebody more aquainted can respond

- - - Updated - - -

As it stands Stay away from this driver for now unless you are brave :cool:
 
Although the download has been "un-pulled", I don't fancy this particular beta much. I'll be watching the skies while others have the misery- I have a night off, and I'd just like to play some ED, which I haven't had much time for lately :)
 
Pain in the A but YES will have to. Set a whole new profile to see the improvements just a little disapointed in the lack of communication between these two entities.

Half the afternoon is gone and the Boss comes home soon. Quick reset everything and down the hatch a couple, whew!
 
Last edited:
Epic flickering when used in direct mode, plus shadowed frames. I did have dual monitors enabled as well so may have caused issues. Really would recommend eveyone stick with .5 for the moment!
 
Glad I didn't update but thanks to those that had the nuts to test.

I'd be keen to know if FD intend to roll this in to Powerplay.
 
Glad I didn't update but thanks to those that had the nuts to test.

I'd be keen to know if FD intend to roll this in to Powerplay.
A recompile for Powerplay could come, but I wouldn't count on a rework to actually use the new stuff. It would be amazing to have the text and other 2D elements render at 2x since that's one of the biggest areas of improvement when using super sampling. They can roll an update to 0.6 SDK in a minor update since it only affects a relatively small portion of users.
 
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.
 
Back
Top Bottom