Skip to main content
Up and Coming
August 15, 2014

Why is DirectToRift always (?) a separate executable?

Due to the lack of Linux support, I'm not yet familiar with the 0.4.x SDK. So stupid question: Does the DirectToRift feature really require to have multiple executables? At least that is how it looks judging from current demos. It's a bit weird to split something that is more or less a binary setting into two executables, where the setting is hard-coded in each. Especially since Unity-based demos in fact have the possibility to adjust settings within the launcher before entering fullscreen mode. Is there a difference how the executables are linked statically? And if so, how is this supposed to work when using the Rift within non-native environments like the JVM?

    11 replies

    Up and Coming
    August 17, 2014
    It would be nice that if the rift camera detects the rift in a 'zone' of being on the users head, it pops up a message asking if the user would like to switch to VR mode (both on the rift and also monitor).