Single/Multiplayer, Touch & Vive blueprint only Template

[anonymous_user_3f422bcf]

The problem with Oculus Avatars is that Oculus made their 1.14 template for “testing purpose” only, meaning that Hands inputstate and headpose are sent to a memory buffer through opaque packets; then the “Avatar Remote” register itself in this datastream and retrieve/read the packets back into input state and headpose.

So what is easily done is spawning an avatar for each player and assign it the right OculusID. What I’ve been trying to do is send the inputs and transforms from the locally-controlled player to the right avatar, through replication and RPC. I’ve lost my soul doing it by code though custom class and /or mixing it with blueprints. The f""ing problem I always encounter one way or another is the opaque pointer to avatar packets, the former refusing to works with pointers of all sort. I even tried to do my own custom “packets” and replicate / RPC them but I again encounter the opaque pointers problem. Anyway, I asked to an Oculus engineer a few days ago about that and he said an update is coming soon. I’ll also examine attentively the SDK 2.0 coming tomorrow to see any interesting changes to Avatars replication. Anyway I’ll release what I’ve done tomorrow so PM me about that I would really like to finish that before Christmas.

For the 3rd controller if I’m right Oculus enabled that for mixed reality capture, right? You give me the idea to hack that and use it like a Vive Tracker, why not? I’ll try that!

Hi , I’m almost sure you’ve already seen this post. But, if not, it could help to integrate Oculus avatars