Quick Summary of the technical checklist for everyone participating in a Multiplayer Session
1. Use headphones with your VR device (or PC)
2. Charge your device and controllers before the session
3. Verify your Browser is up to date
4. Connect your Device to the best internet wifi and test that WebRTC is working on this same internet network using your PC
Please validate that both Relay connectivity and Host connectivity are checked
Find below a more detailed WebRTC audit
To ensure a Multiplayer Session is as comfortable as possible, Wonda recommends:
To fully charge your devices before starting the session. In general, performance on VR Headsets decreases when the battery is low and Multiplayer Sessions can be very demanding performance-wise when there are multiple participants.
To have headphones plugged into your headsets or mute users when they are not speaking to avoid echoes.
Wonda Multiplayer Sessions rely on two different services in order to work properly
A webRTC stack which handles audio communications and avatar synchronization
A content synchronization server that allows all participants to view the same content at the same time
Bandwidth use: Wonda VR recommends having a bandwidth of at least 300kbps per user to support a good audio quality and correct avatar synchronisation. Note this bandwidth is only for webRTC communications, it does not include the bandwidth cost of media streaming.
You can use this tool https://test.webrtc.org/ to verify your device allows webRTC communications in your current network configuration.
For Enterprise Hub
Multiplayer sessions for Enterprise Hub are based on Twilio, our webRTC Premium solution. Check this documentation for more info and troubleshooting: https://www.twilio.com/docs/video/ip-addresses#media-servers
For experience in Imlab Hub
Firewall rules: In order to work correctly, the following connexions must be allowed in the firewall:
By default, webRTC communications will not work on networks that use a symmetric NAT restriction (more info https://developer.mozilla.org/en-US/docs/Web/API/WebRTC_API/Protocols#TURN)
If it is the case, Wonda VR teams can set up a TURN server to handle those use cases.
Content Synchronization Requirements
Communications to Wonda VR synchronization server must be allowed with the following properties:
TCP to room-manager.spaces.wondavr.com port 443