Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
Vrally's avatar
Vrally
Protege
11 years ago

How to get custom IPD settings from configuration utillity?

Hi,

I have troubles getting the custom IPD settings entered into the Oculus Configuation Utility. No matter what IPD settings I enter into the Utility the ovrHmd_getRenderDesc() allways returns a HmdToEyeViewOffset struct with 32 mm translation (i.e. half of the default IPD value of 64mm).

Am I doing something wrong here? Do I need to do some special initialization to select my custom user profile?

4 Replies

  • Vrally's avatar
    Vrally
    Protege
    11 years ago
    "brantlew" wrote:
    What version of SDK? Which dev kit are you using?


    Another user reported this for my OpenSceneGraph integration with the Oculus SDK 0.5.0.1. I managed to reproduce the result in both my integration as well as in the OculusRoomTiny example for the 0.5.0.1 SDK.

    But then I tried the OculusRoomTiny example in 0.6.0.0 SDK, and for this version the ovrHmd_getRenderDesc() function returns HmdToEyeViewOffset structs which match the custom setting. So for the latest version it seems fixed (regretfully we have not been able to get the 0.6.0.0 SDK fully integrated with with OpenSceneGraph yet).

    Was this a known problem with the 0.5.0.1 version of the SDK, that got fixed with the 0.6.0.0 release?
  • brantlew's avatar
    brantlew
    Adventurer
    11 years ago
    I'm not aware of a bug like that in 0.5, but it's certainly possible. Glad to hear it's working in 0.6, but I'll try to get better QA checks for this sort of thing moving forward.
  • Vrally's avatar
    Vrally
    Protege
    11 years ago
    "brantlew" wrote:
    I'm not aware of a bug like that in 0.5, but it's certainly possible. Glad to hear it's working in 0.6, but I'll try to get better QA checks for this sort of thing moving forward.


    Well, I am running the 0.5.0.1 OculusRoomTiny example with the 0.6.0.0 runtime, so maybe that could be the cause... Otherwise custom IPD settings have been broken for all users of the 0.5.0.1 SDK, and it seems strange that no one caught that bug already.

    Can it be that the profile generated by the 0.6.0.0 runtime is NOT backwards compatible with the 0.5.0.1 SDK???