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?

檢視更多

Does the end customer need to take any special steps to launch Oculus Rift content via VIVEPORT?

Leigh

2020年01月17日 11:08
已更新

Yes, they will need to enable support of 3^rd party applications from within the Oculus desktop software. Under the “general” tab, they must enable “Allow Unknown Sources” for the content to successfully launch.

評論

0 條評論

請登入寫評論。