- This topic has 4 replies, 2 voices, and was last updated Aug 17, 2014 8:23pm by
.
-
Posts
-
I mean with the amount of questions that seem to be persistent about Vorpx and DK2 and compatibility, think it would be beneficial to Ralf if an FAQ was created to help answer people’s common questions?
The most relevant things are answered in the DK2 first aid sticky:
If you feel anything important is missing, please post it here and I’ll add it to the first post of the sticky.
Well one thing I’m pretty sure is gonna be asked a lot once the update comes is “How do I update.”
Also, here’s something I’ve been wondering, because I honestly do not understand how “Direct to Rift” works since I’m a total noob when it comes to working with the windows infrastructure, is will the update actually have some ways to put games directly to the rift without the need to screw around with extended mode.
Sorry if that sounds impossible from your end. I didn’t know if that was something hard coded into the games themselves or if there was actually some sort of DLL library that could be accessed by even third party programs. I figured since it was becoming uniform to include “direct to rift” options that it would actually be DLLs or an option in the SDK itself to compile a separate .exe
Updates are installed automatically, similar to Steam updates. When you start vorpX Control, vorpX checks for available updates.
The first DK2 ready version of vorpX will probably require Extended Mode. Direct to Rift works for a few games already, but in general it’s a lot more difficult to implement in a driver like vorpX compared to native apps since the Oculus driver hooks games similar to vorpX, which creates a conflict between both programs.
You can force many games to the Rift through the vorpX config app though, which makes working in Extended Mode a lot easier.
- You must be logged in to reply to this topic.