Lets make a SDK 0.4 Linux nagging thread!

"lokieliot" wrote:
After Installing 4.1 and updating firmware to 2.11 i get an error message 'Incompatible resolution. Please configure the Rift screen to the native resolution.' everything seems correct, what am i not doing?

UPDATE: So the Oculus uses an extended screen, but for some reason rotates the display -90 degrees. Shame the SDK can't work that one out itself.

UPDATE2: I still have frustrating display issues wight the SDK. The Tuscany Demo does not seem to know where it wants to display. I'll wait and see what others say.

I had the sames troubles :

Here are the steps i've done in order to make it work on OSX :

1 - Install the oculus runtime, plug the DK2 in
2 - Open the display setting (Preferences/Display) with cmd+alt+clic to enable display rotation, go to Arrangement, disable Mirror Displays if it's enabled
3 - Clic on "gather windows" button, a new window open, rotate the screen by 90°, select the default/native resolution
4 - Back to the display setting, enable mirror displays, if it works, you'll probably see your main screen's color become weird.
5- Then you'll be able to launch the tuscany demo

Thanks a lot Gregoired, you made my day! Worked instantly on my hackintosh.

Thanks for the OSX release, how long until we've got Linux?

I've updated the topic, as I'm using Linux I'd like to know why isn't the Mac and Linux SDKs developed in conjunction with each other? They are both unix based OSes after all. :(
I know, I know there are discrepancies in X, Cocoa and such....

"creepytennis" wrote:
Also, if the drivers stay closed source, my DK2 is going right back. I'm not developing for something that'll become a brick without proprietary drivers.

The Rift hardware is great. The software continues to be a big disappointment. We badly need an open source driver stack.

In practical terms GPUs become a brick without proprietary drivers, as FOSS Nvidia Drivers are practically non existent and FOSS AMD drivers are so buggy/slow that nobody uses them if they are at all interested in performance. Sure I agree it would be a bummer if it comes to that. But I'm pragmatic in that regard, I'd prefer open source but I can live with proprietary stuff as long as it works without hassles on any OS. (The Nvidia drivers for instance do)


Again I would hate it if they don't release the sources of the runtime part, but that won't be a show stopper for me if I don't have to deal with it. In principle it is understandable that they don't want the give the competition something they can copy easily. But that is a fairly short term view.
In the long run we need something akin to OpenGL for VR that works manufacturer agnostic and that has to be rigorously documented and openly implemented. Proprietary runtimes are a step away from that and overall bad for the future of VR in the coming years.

let's continue the discussion here!

"ElectricMucus" wrote:
FOSS AMD drivers are so buggy/slow that nobody uses them if they are at all interested in performance

The open source AMD drivers at the moment are way more reliable than the proprietary ones, in my experience.

"kaetemi" wrote:

"ElectricMucus" wrote:
FOSS AMD drivers are so buggy/slow that nobody uses them if they are at all interested in performance

The open source AMD drivers at the moment are way more reliable than the proprietary ones, in my experience.

If you are doing anything that involves 3D rendering beyond a opengl 2.1 level they aren't. GLSL is particularly awful.
For things like 2D desktop use and video playback you're right.

"ElectricMucus" wrote:
Thanks for the OSX release, how long until we've got Linux?

I've updated the topic, as I'm using Linux I'd like to know why isn't the Mac and Linux SDKs developed in conjunction with each other? They are both unix based OSes after all. :(
I know, I know there are discrepancies in X, Cocoa and such....

Given that they were willing to release the OSX SDK without DirectHMD support, I wouldn't be surprised to see the Linux platform follow soon after. In fact I'm almost surprised they didn't release it concurrently since the code for interacting with most subsystems is almost identical between the two platforms, and they already have per-platform code for interacting with the HID devices used by the IMU.

I would suspect the delay involves either getting the camera functionality working on Linux (although since the camera is recognized by the V4L system, this doesn't seem like it would be that hard, unless they're actually using a customized mechanism to get data faster than something like V4L would provide) or difficulty getting the runtime integrated as a service.

"ElectricMucus" wrote:
If you are doing anything that involves 3D rendering beyond a opengl 2.1 level they aren't. GLSL is particularly awful.
For things like 2D desktop use and video playback you're right.

OpenGL 1.5 :lol:

YAY Linux thread !!!!!

I need this to work in Linux no friend of windows. :(

I don't think its really Mac OS support in 4.1, its feels more like an accident.