What are your experiences with the SDK 1.0

First, this is a development question so I'll move to the development forum.

In terms of your question, the 1.0 PC SDK is not public right now, and the people that have access to it should not be talking about anything within it on a public channel.

I realize people are interested to know what improvements there are and more information will be coming.

Is there already a time table when the non testers will get acces to the sdk 1.0 and runtime.??

"Marco3key" wrote:
Is there already a time table when the non testers will get acces to the sdk 1.0 and runtime.??

Good question. I have a DK1 and I'm thrilled about my retail kit coming but access to SDK 1.0 asap would be great. I'm assuming the retail kit will be just as open to development as a devkit?

I'm having an issue with the ovr_GetSessionStatus() in the 1.0 SDK if I unplug the HDMI cable and plug it back in. When I unplug the cable, HmdPresent and HmdMounted are still returning true, but IsVisible returns false. But when I plug it back in, IsVisible still returns false.

@hmiller: I sent you a PM with details about the proper channel to discuss private SDKs. Thanks.

Hi,

Could we the unfortunate at least know why is 1.0 so secret if all previous releases where not?

Thanks.

There are lots of pieces in the software stack that work together, not just the SDK all alone, and it didn't make sense to release this before the official consumer launch (which is really not that far away, be patient).

Thanks.
Will it work with the DK2 or CV1 is a must?

I won't comment on DK2 compatibility, but there are a number of features only available with the consumer product.

I do not have the 1.0 but i am confident it will have zero improvements from my wish list. Even without talking about DX12.

* waitable swapchain, reverse where you wait. Instead of a dead locked present, you wait for the monitor (or rift) to be in need for a frame and here you go. It is an order of things that allow a reduced latency, and better control over the queuing.
* uint64 timestamps, double has enough precision but it is inconsistant with cpu and gpu timestamps.
* a way to query all the lens and placement properties to write a custom warp and distortion
* possibly a gpu buffer for deferred update of the hmd orientation for previous point.
* a stat on how good is the position tracking to warn the user before it is too late.
* dx12, cent balles et un mars :)