HTC Vive support is now included with CRYENGINE. This article will guide you through setting up VR and also includes important information that you should know before getting started.
For help in configuring your device, please use the official HTC Vive application and documentation (available in the link above).
To enable VR in CRYENGINE then follow the steps below:
Once launched, the Engine should be rendering to your head-mounted device.
If you want to make changes to a level i.e. edit your game then you will need to disable VR.
When reverting back to game mode then all of the above steps/any changes made for edit mode must be reverted
Launch the Engine as admin if you encounter error 308.
If so desired you can bind this directly to a key/gamepad button. This can be achieved via Flow Graph using the Debug:InputKey node.
Alternatively, you could modify the <game_folder>\Libs\Config\DefaultProfile.xml
file and assign a button there.
See Setting up Controls & Actionmaps for more information.
We have exposed some controls/functions that are related to the HMD device and the Motion Controllers. This can be accessed through Flow Graph.
Allows quick access to position and rotation information related to the VR device.
Allows you to hook up an input to trigger the RecenterPose command.
Similar to the VR:TransformInfo node. This node will allow you to access position and rotation information of a controller. Additionally, you can provide a scaling value as well as a reference entity.
FlowNodes below are Device/Platform specific, exposed for solely for the purposes of device specific interaction, and not interoperability.
Allows you to retrieve the button states as well as the trigger and touchpad values of the given Controller. (Index should usually be either 0 or 1).
The HTC Vive will play your game at exactly 90 FPS if you can make it run at exactly 90 FPS or above.
If at any point your game runs at a fraction less than 90 FPS, it will temporarily default down to 45 FPS until 90 FPS is restored.
Please keep in mind that anything less than 90 FPS is generally not considered to be a pleasant experience in VR.
Solution:
NOTE: When reverting back to game mode then all of the above steps/any changes made must be reverted
This will try to enable VR in Editor Mode which it will attempt, but can't do.
Solution: Rename the user.cfg to something else such as _user.cfg
This will bypass the file being read on loading of the Sandbox Editor.
The game is active in the background but nothing is visually represented on screen.
Solution: Delete the the user folder in the root of the build. Then relaunch the GameSDK.exe.