Absolutely not! We will only require you to have support for Oculus hardware if you opt-in to this specific feature. Our intention with this update is to provide publishers an additional distribution mechanism to reach Oculus hardware owners – we have zero intention of making Oculus support a hard requirement to publish VIVE content on the platform.
Articles in this section
- How will consumers know which titles are compatible with Oculus?
- Will all titles on Viveport work for Oculus Rift users?
- Does the end customer need to take any special steps to launch Oculus Rift content via VIVEPORT?
- What about the “OpenVR-Input Emulator”? Can I use this to quickly remap existing Vive inputs onto a Touch controller scheme?
- Where can I find documentation about Oculus Rift and VIVE controller input mapping?
- How do I opt-in or opt-out of the VIVEPORT Oculus Rift program?
- I have additional questions about publishing an Oculus Rift compatible title to VIVEPORT; where can I ask them?
- Which VIVEPORT revenue models will be available for content that indicates support for Oculus Rift hardware?
- Do I need a specific version of VIVEPORT to take advantage of this Oculus Rift feature? Can I test using the developer consoles “beta” feature?
- Since the Oculus Rift approach is OpenVR based, does that mean that Windows Mixed Reality HMDs will also be supported in the future? Can I upload a WMR build to VIVEPORT?