Hi guys. Just a quick recap. I’m presently working on a new version of the template. This one should be faster than precedent version, simply because I’ll replicate things via a small bit of C++ code, thus eliminating the main bottleneck of the template (was replicating on tick in bp). Because I’m a developer and a university professor, I like to explain things. So the little bits of code will be thoroughly explained.
I’m working now on the 4.20.3-Oculus branch, as per suggestion of Mike Howard, the Oculus Avatar product Manager at Oculus. Major problems right now with version 4.21 and Avatars. My next template will be targeted for Oculus Rift, Go & Quest. While we have here all kind of VR stuff (Magic Leap, all versions Valve knuckles, etc), I feel best served by Oculus, and all our projects right now are whether Go, Quest, or Magic Leap oriented.
So I put aside a little bit the Steam and Magic Leap templates, and concentrate on Oculus-oriented products.
The next template will incorporate (in part) the now-integrated Oculus-Avatar plugin; anyway honestly it does not bring much to the already available Oculus-Avatars SDK (latest v1.31).
Avatars on Android in Unreal: As per Mike, “not ready for prime time”; it works kinda, but needs more polishing.
So next template, everything multiplayer, very much faster and simpler, will integrate Oculus Avatars (for Rift) and maybe, maybe for Android (Go, Quest).
As I consider myself an my team, pioneers in VR, we like to bring an easy-to-use and understand template, even for the newbies.
As Bon Jovi said, keep the faith!