Lets make a SDK 0.4 Linux nagging thread!

"alexfry" wrote:

"cybereality" wrote:
Yes, other platforms are in the works. It was just important to get the SDK out for the DK2 launch, which is why Windows came out first. However, we have not forgotten about Mac and Linux. Unfortunately I don't have an ETA to when they will be ready.

Well..... If it's not out for Mac and Linux then it isn't really out is it.
A DK2 that only supports Windows is a brick to me.

You should still be able to use 0.3.x on Mac, but without positional tracking. It's not ideal, but neither is it useless for development.

That's a fair point.
For what I'm using it for, the positional tracking isn't that important.

It's makes me sad that OSX does not have exactly the same release timeframe as Windows, but at the key point of the new SDK 2, it's very upsetting, please could you update us as to how far it is behind

"jhibbins" wrote:
It's makes me sad that OSX does not have exactly the same release timeframe as Windows, but at the key point of the new SDK 2, it's very upsetting, please could you update us as to how far it is behind

Yes the "not even an ETA yet" thing sucks.

So I have my SKD 2!!! YAY!!!

I'ts a brick on my OSX, even when I managed to get it running as an external monitor (and worked out how to rotate the screen) the eye lenses don't match the screen at all, I imported the Unity Pro Oculus 0.4 and it won't run, which is probably due to drivers!

I am lucky enough to have a windows 8.1 bootcamp, so I switched (I can't code but hey may as well try a few demos), I ran the tuscany (light with no anime) demo, and NOTHING else will work, I can't even get legacy mode working.

It's sad that with all the wait, I can't even use it on OSX.

"ElectricMucus" wrote:

"jhibbins" wrote:
It's makes me sad that OSX does not have exactly the same release timeframe as Windows, but at the key point of the new SDK 2, it's very upsetting, please could you update us as to how far it is behind

Yes the "not even an ETA yet" thing sucks.

No, what sucks is that they've withheld the source code for the runtime. Even if they'd only released the windows source code for the runtime along with the SDK, I'm sure someone would have hacked something together by now to allow OSX and Linux developers to work.

I haven't thought about it that way, and you are right. I also find the lack of runtime sources unacceptable.
What's the reason for that? If they are bound by some 3rd party agreement that they can't release the sources they shouldn't have done that in the first place.
And if they don't release it because they don't want developers to have that much control any more even worse. :cry:

I get the strange suspicion that we might face a "boiling a frog" thing where more and more functionality is moved into a non-accessible non-modifiable portion of the SDK. Lets hope it doesn't come to that.
Meanwhile OVR is awfully quiet about these issues. :?

"jherico" wrote:
No, what sucks is that they've withheld the source code for the runtime.

I agree with this, I really hope we see the source code for the Oculus service and the drivers released soon. They've effectively made a large part of the SDK closed source now by offloading tasks into the service.

Yeah, maybe open source the drivers, we are a bunch of Developers after all!

OSX is actually fairly close to being ready. Linux may be a little further out. Sorry I can't be more specific.