Can position tracking be turned off with SDK 1.3?

As far as I can tell (in 0.8.0.0), even in the OculusWorldDemo (Tuscany), when you open the HUD menu (spacebar or tab), there is an option to turn off positional tracking, but it doesn't actually work (?)

Also, I would advise that if you are interested in working at the SDK level, 0.5.0.0 is probably the easiest because it is the last SDK before introducing the compositor architecture, which adds another layer of complexity, and the src code is also provided.  

Thanks for the reply.  I was using 0.8 before, and was able to switch positional tracking off in software (or rather, not enable it in the first place).  And before that I was indeed working with 0.5.0.0 (and still am, on OS X...).  The only problem is that you can't run both 0.5 (or 0.8) runtimes as well as the post-v1.0 consumer-version stuff.

Right, so you have to go through the rather inconvenient task of installing / un-installing runtimes constantly. I've resolved to work with the 0.5 SDK since it has all the openness that Oculus originally envisioned in addition to the tech specs that later SDKs benefit from, albeit with simpler software architecture. So are you a game developer, researcher, or what?

What is difficult in not adding the position information in your matrices, just ignore the position value, it is not a big deal to get it from the sensor and not using it.

Do not listen to fools about sdk <1.0. It is true then need to add a few levers to the current black box, but there is no concrete argument to justify to work on 0.7-0.8 nor below (no, extended mode is not a valid argument to me)

galopin said:

What is difficult in not adding the position information in your matrices, just ignore the position value, it is not a big deal to get it from the sensor and not using it.



Do not listen to fools about sdk

Honestly, @galopin your answer would have been just as helpful without that last bit. 

Yeah, the fools part was kind of uncalled for.

hum, because my message was truncated... Still may be harsh, but argumented...

I was saying to put you in the state of mind that everything prior to 1.0 did not exist. The extended mode is not viable and no way easier than the direct mode, in fact direct mode is easier than dealing with the windows desktop manager.

Second, i was saying that right now, everything is not pink, 1.3 is too much of a black box, limiting innovation and adding frustration, Oculus cannot pretend to have a perfect knowledge on VR, as it is a domain where a lot remains to be invented and experimented. They definitely need to open the black box to help everyone to experiment and do not fight against the applications that are not main stream ( games ), it will come in time with enough request and less stress from the messy release :)

Thanks for the replies.  Yes, I was hoping to try to "keep up" with the latest runtimes, and to benefit from things like direct mode and even asynchronous timewarp.  @galopin Yes, I'd thought about removing the head position from the matrices, but figured that would mess with the ATW.  Thinking about it further, I guess not, since the time-warp Oculus has implemented is rotation-only.  So, yes, I'll give that a try.

So are you a game developer, researcher, or what?

Definitely "or what."   ;)   Freelance programmer/artist/creative coder... or something like that.

Thanks again,
Glen.

In Unity, you can just disable position tracking by setting OVRPlugin.position to false. This ultimately is calling the following code that directly calls the functions in the dll (taken from OVRPlugin.cs):

cap = 5; (The enumeration for Position is 5).


ovrp_SetCaps(caps)

Would this work for your purposes?

the set caps function is not part of the ovr api anymore, so it will change nothing :)