Modules§
- api
- mock
- utils
- vr_
display - vr_
display_ capabilities - vr_
display_ data - vr_
event - vr_eye
- vr_
eye_ parameters - vr_
field_ view - vr_
frame_ data - vr_
framebuffer - vr_
future_ frame_ data - vr_
gamepad - vr_
layer - vr_
main_ thread_ heartbeat - vr_pose
- vr_
service - vr_
stage_ parameters
Structs§
- MockVR
Init - MockVR
View - VRDisplay
Capabilities - describes the capabilities of a VRDisplay. These are expected to be static per-device/per-user.
- VRDisplay
Data - VREye
Parameters - The VREyeParameters interface represents all the information required to correctly render a scene for a given eye.
- VRField
OfView - The VRFieldOfView interface represents a field of view, as given by 4 degrees describing the view from a center point.
- VRFrame
Data - Represents all the information needed to render a single frame of a VR scene
- VRFramebuffer
- Information about a FBO provided by a VRDisplay.
- VRFramebuffer
Attributes - VRFuture
Frame Data - VRGamepad
Button - VRGamepad
Data - VRGamepad
State - VRLayer
- Data provided to a VRDisplay and presented in the HMD.
- VRPose
- The VRPose struct represents a sensor’s state at a given timestamp.
- VRResolve
Frame Data - VRService
Manager - VRStage
Parameters - The VRStageParameters interface represents the values describing the stage/play area for displays that support room-scale experiences.
- VRViewport
Enums§
Traits§
- VRDisplay
- The VRDisplay traits forms the base of all VR device implementations
- VRGamepad
- VRMain
Thread Heartbeat - Each VR service may have some code which needs to run on the main thread,
for example window creation on MacOS is only supported on the main thread.
Implementations of this trait will usually be neither
SyncnorSend. - VRService
- VRService
Creator