No – you are not required to integrate the VIVEPORT SDK into your project in order to publish it to the store but we strongly encourage you to integrate it to make use of the SDK-based DRM utilized by Viveport, and to gain access to additional SDK features such as DLC. If you chose to not integrate the Viveport SDK, you’ll have the option of using a less-secure wrapper-based DRM solution via the developer console.
- 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?
- Is VIVEPORT support for Oculus Rift related to the ReVive Compatibility Layer?