4.27 template poor performance on Quest 1

[maxbrown]

@Brickan

BTW, when I talk about the 4.27 template giving poor performance, I mean around 14-15 FPS. If I go into the smaller room, it jumps up to 22-23 FPS

I created a new vrTemplate project (4.27.0) and checked again with OVRmetrics and you’re right; the default VRtemplate in 4.27.0 runs that bad as you reported on Quest1. I hadn’t checked with OVR metrics before, barely tested the level and was mainly focused on solving why my migrated levels gave such bad performance. Sorry for the confusion.

If you do create a blank new project and enable openXR, Vulkan etc and build for Quest1 (so without the vrTemplate stuff in it) and use your own meshes, blueprints/controllers etc as before, it should run nicely. I tested a small project (200k triangles, 300 drawcalls) and it runs 72fps. So there’s something in the template project that doesn’t play nice with Quest 1.

@VictorLerp Is it a known issue the vrTemplate project runs like this on Quest1? I tried looking for a reason using Renderdoc (v1.15, plugin v1.0 Buildin in Editor) but for some reason it gets stuck at the three dots on the Quest. Renderdoc also reports some errors when connecting (error reading from socket, didn’t get proper handshake).