4.2.2.2. Requests from Client to Server

A client may send any of the following one or more times per frame:

• DisplayInfo

• ControllerPoses

• OriginPose

• Inputs

• ResourceRequests

• ResourceAcknowledgements

• NodeUpdates

The Client sends all of its messages in its local units and Axes Standard. For example, if the Client works in metres and has Y vertical, positions and rotations sent to the server will be in this format.

The Server sends all of its commands to the Client in the Client’s local units and standard.

4.2.2.2.1. DisplayInfo

Reference implementation: avs::DisplayInfo

Table 4.7 DisplayInfo

Bytes	Type	Description
4	uint32_t	width
4	uint32_t	height

4.2.2.2.2. ControllerPoses

Reference implementation: avs::ControllerPosesMessage

Table 4.8 ControllerPoses

Bytes	Type	Description
28	Pose	head pose
28	Pose	left controller pose
28	Pose	right controller pose

where Pose is:

Table 4.9 Pose

Bytes	Type	Description
16	4-vector of floats	orientation (quaternion)
12	3-vector of floats	position

4.2.2.2.3. ResourceRequests

Table 4.10 ResourceRequests

Bytes	Type	Description
8	uint64_t	number of resources requested = N
8*N	uid	resource uid’s

4.2.2.2.4. ReceivedResources

Reference implementation: avs::ReceivedResourcesMessage

Table 4.11 ReceivedResources

Bytes	Type	Description
8	uint64_t	number of resources acknowledged = N
8*N	uid	resource uid’s

4.2.2.2.5. NodeUpdates

Reference implementation: avs::NodeStatusMessage

Table 4.12 NodeUpdates

Bytes	Type	Description
8	uint64_t	number of received nodes to report = N
8	uint64_t	number of lost nodes to report = M
8*N	uid	received node uid’s
8*M	uid	lost node uid’s

4.2.2.2.6. Video Keyframe Request

Table 4.13 Video Keyframe Request

Bytes	Type	Description
8	uint64_t	number of received nodes to report = N