@Liquidgands thanks for reporting!
So I’ve been doing some tests yesterday with 3 persons (2 Vive with Trackers, and Oculus) via Steam with the Packaged_2_3 found on the drive.
So considering that, and using now 4.16, Here’s my todo list for the next versions:
2.4 Multiplayer:
[1] 4.16 cannot open multiplayer map - FIXED (see answerhub With 4.16 BP OpenLevel fails when packaged (Windows) - Platform & Builds - Unreal Engine Forums to adress the problem)
[2] 4.16 Monitor output - FIXED
[3] Launch session doesn’t work after having selecting a session and pushed refresh - FIXED (the last function called in the refresh function was redondant)
[4] Vive Trackers -If the listen-server has Vive Trackers, the Trackers are duplicated within local space for each client rather than worldspace
[5] Vive Trackers - If a client has Vive Trackers, his Trackers (client-side) have some lag due to server replicating position
[6] Vive Trackers - the mesh has bad geometry and too many polys, can cause crashes - FIXED with a simplified mesh
[7] [HTC Vive] The position of the player within its playground is offseted
[8] Chaperone / Guardian boundaries don’t always appear - it seems related to network speed (ok in fast connections)
[9] Left/Right grab sockets
[10] Cannot search friends on Steam and Oculus Network
[11] Oculus - No VOIP
[12] Oculus - Cannot search friends sessions
[13] Oculus - Avatars, local and replicated, compatible with Avatar_Master (e.g. teleporting, collision and grabbing)
[14] 4.16 - Network Optimizations
1.3 Single Player
Points [2], [6], [7] and [9] plus
[15] Integration of the VR Essential Kit for interactions with the new grabbing function
I should also create some 3rd person pawn just to test some features off line via simulated network.
I’ve mostly worked in the last few days on doing the Oculus_Avatar pawn, meaning it will use the Oculus Avatar or revert to the Avatar_Master pawn if Oculus Avatar cannot be found on Oculus network, or the option of using Avatar is turned off.