Hey guys!I put together this simple tutorial, showing the bare minimum code needed to work with the Oculus SDK.https://developer.oculus.com/wiki/index.php?title=Minimal_Oculus_ApplicationIt's basically just a console application that prints out some values from the headset. This could be a good place to start if you are confused about what is part of the SDK and what is just part of the demos. It also shows how simple it is to work with the SDK. Of course, it won't show how to handle stereo 3D, or distortion, or all the complex stuff. But it's a start.Hope that helps,- AndresUpdated tutorial for 0.3.x SDK: https://developer.oculus.com/wiki/Minimal_Oculus_Application_0.3.x

Thanks for this! One of my pieces of feedback was that I found working off the sample source much easier than the documentation, so I was going to suggest that you guys do one of these source-and-explanation tutorials. The documentation is great for understanding the "why," but I think the "how" is best communicated through something like this.Should be helpful for others trying to get up to speed! I spent a bit of time going through the docs trying to figure out what the K-values were for the headset before realizing you could read them from the device config by looking at the sample source :)

That's a great tutorial. It really does make it easier to identify core elements.Beginners will have some challenge wrapping their heads around the pseudo-managed pointers.Overall it's a helpful time saver. Thanks.

Very useful guide, tyvm. I Now If you could do the same for setting up the warp and SBS rendering that would help me out quite a bit! :P

Here is an enhanced version of the Minimal App that adds acceleration data:https://developer.oculus.com/wiki/Add ... ation_Data

"geekmaster" wrote:Here is an enhanced version of the Minimal App that adds acceleration data:https://developer.oculus.com/wiki/Add ... ation_DataTechnically that's a mixture of acceleration and the up vector. It will report an acceleration upwards even when the Rift isn't accelerating (and will report zero when the Rift is accelerating at 9.8m/s/s downwards). I was hoping Oculus had already separated out accelerations for us, but they are just giving us the calibrated accelerometer data.Contrary to what that page says, it is giving you the UP vector, not the DOWN vector. The reason is, accelerometers can't detect the force of gravity or acceleration due to gravity, but can detect the equal and opposite force of you holding it up against gravity. Accelerometers work by having a weight on a spring (usually a microscopic one). It's like when you stand up on a bus, you get pushed back when the bus accelerates, and flung forwards when the bus decelerates suddenly. Most forces (like you moving your head) are applied to the outside of the Rift, while the weight has inertia and lags behind. But that doesn't happen with gravity, which pulls on the inside weight at the same time it pulls on the outside.If you can find out which way is UP some other way (by remembering from when there was no true acceleration, and applying the change from the gyros), then you can subtract it to get a rough idea of the true acceleration, but that's not usually accurate enough for much.

Minimal Oculus Application Tutorial | Meta Community Forums

33 Replies

cybereality
Grand Champion
11 years ago
I need to update the wiki to the latest SDK. Please give me a moment.
cybereality
Grand Champion
11 years ago
OK, here you go:

https://developer.oculus.com/wiki/Minimal_Oculus_Application_0.3.x

provezano

Honored Guest

11 years ago

I've tested your application and I some constants aren't recognized.

In this line:

ovrHmd_StartSensor(hmd, ovrHmdCap_Orientation | ovrHmdCap_YawCorrection | ovrHmdCap_Position | ovrHmdCap_LowPersistence, ovrHmdCap_Orientation);

I found those constants in the OVR_CAPI file, as follows:

typedef enum
{
    ovrSensorCap_Orientation    = 0x0010,   //  Supports orientation tracking (IMU).
    ovrSensorCap_YawCorrection  = 0x0020,   //  Supports yaw correction through magnetometer or other means.
    ovrSensorCap_Position       = 0x0040,   //  Supports positional tracking.
} ovrSensorCaps;

So, if I change the line above to

ovrHmd_StartSensor(hmd, ovrSensorCap_Orientation | ovrSensorCap_YawCorrection | ovrSensorCap_Position | ovrHmdCap_LowPersistence, ovrSensorCap_Orientation);

it works.

--
Is it possible to capture those values while I am trying an example at the same time :?:

cybereality
Grand Champion
11 years ago
Ah yes, there were some changes in 0.3.2 that broke this example.

Thanks for bringing this to my attention.
jherico
Adventurer
11 years ago
"provezano" wrote:

ovrHmd_StartSensor(hmd, ovrSensorCap_Orientation | ovrSensorCap_YawCorrection | ovrSensorCap_Position | ovrHmdCap_LowPersistence, ovrSensorCap_Orientation);

Don't pass in anything that isn't an "ovrSensorCap_" capabilities into StartSensor. In particular, ovrHmdCap_LowPersistence isn't part of the sensor capabilities. Since these are bitfields, injecting a bitfield from the wrong type can erroneously turn on or off some feature you didn't expect.

Also, you don't need to duplicate anything in required that is already in supported, unless you explicitly want the function to return false and not start the sensors if it's not supported.

cybereality

Grand Champion

11 years ago

OK, I updated the tutorial. The line should look like this:

ovrHmd_StartSensor(hmd, ovrSensorCap_Orientation| ovrSensorCap_YawCorrection | ovrSensorCap_Position, ovrSensorCap_Orientation);

provezano
Honored Guest
11 years ago
How about my question?
Is it possible to capture those values while I am trying an example at the same time :?:

I mean... I can use and capture the coordinates from my mouse at the same time, is it possible to do the same with Oculus? Because I tried that example and the Oculus becomes unavailable for another application.
cybereality
Grand Champion
11 years ago
Currently only one application can interface with the Rift at a time.
geekmaster
Protege
11 years ago
"cybereality" wrote:
Currently only one application can interface with the Rift at a time.

Unless that application is a USB multiplexer, such as is commonly used to feed a USB webcam video stream to multiple apps. This method could work for the Rift as well. It is not that hard to find a way to get beyond artificial limitations like your "only one application" constraint.
fire2k
Honored Guest
11 years ago
A little question about the tutorial:

To get this to work I also have to explicitly link to "shell32.lib" and "gdi32.lib", even though they are totally in the inherited values. If I don't link those two specifically I get Linker failures.

I've noticed that the OculusTinyRoom also explicitly links everything inherited in again. Is there a reason for this?

Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨

Minimal Oculus Application Tutorial

33 Replies

Quick Links

Other Meta Support

Related Content

Application image

Missing Tutorial Project File

Quest 2 Stuck Loading Into the Desktop Application

This application requires the Windows App Runtime

Create A World Tutorial Step five