We're gearing up for our first public Quest store release and now...

@iBrews
Alex Coulombe@iBrews
10 views May 13, 2024 ~3 min read
Advertisement
1
We're gearing up for our first public Quest store release and now properly jumping through all of Meta's VRCs. Here's a thread on some of the headaches we're encountering. I hope this will be useful to other #UE5 developers going down this path in the future. Enjoy! 😪😓😮‍💨
2
Let's start with VRC.Quest.Performance.1:
Interactive applications must use a refresh of 72 Hz, 80 Hz, 90 Hz, or 120 Hz.

We're using the Meta Quest Developer Hub which conveniently throws up fps drop flags while in the experience, so we identified a few pain points
Media image
3
On Friday, @RobertJALA kindly went thru various stat commands (stat scenerendering, stat rhi, stat unit, stat tickables etc) to identify elements in our scene causing the biggest bottlenecks. In our case, biggest one we hadn't addressed was materials too many individual textures.
4
@RobertJALA it also seemed time to try making a build from Meta's fork of Unreal Engine 5.3, which allows for such features as ASW (best in class reprojection), eye tracked foveation (disable OpenXR foveation!), and more, unavailable when just using the MetaXR plugin.
Media image
Media image
5
@RobertJALA There's quite a few plugins that ship with Unreal that are excluded from Meta's fork, so we had to take those along with our custom plugins into the project Plugins folder & rebuild them in C++. For some reason I also had to specify 'project only' to not rebuild the entire engine
Media image
6
thanks again to Alex from Out of the Box Plugins for helping me figure this out-- note you can also just delete the entire line about engine version from your .uplugin files
x.com/iBrews/status/…
7
now things got bizarre.

we assumed that with Application SpaceWarp (ASW) enabled, we'd see a significant performance improvement.

In headset, we were seeing that. However in MQDH every few seconds we get flagged as the CPU useage spiked and the framerate dropped from 72 to 36😵‍💫
Media image
8
And those spikes would even happen in a blank map! Compare that to ASW off where, at least in this blank test map, we could hit any framerate we desire with no spikes... even 120 fps (note UE5 Meta builds will always default to 72 fps target unless you tell it otherwise)
Media image
Media image
9
And here's a funny thing—the flags only get raised when you're under 60 fps... so if I set the target framerate to 120 fps and have ASW on, those CPU spikes only drop down to 60 fps and so it doesn't raise a flag. HOWEVER, the VRC says you need to maintain your target framerate🤔
Media image
10
anyway, that's where we are at the moment. hopefully we can get an answer from Meta on if the flags ASW is throwing in MQDH are actually going to keep us from passing VRC (in which case we just won't use their fork) but if so, I'd love to know more about what's going on there.
11
( oh and we're also dealing with some totally baffling things like stuff that looks different in the left and right eyes but only in the Meta fork so who knows what's going on there we'd really like to keep instanced stereo on lol )
12
Really grateful for Neel reaching out and hopping into this over the weekend to help us with a sanity check— we’re not using ASW wrong, yay
13
@threadreaderapp unroll
Actions
What You Can Do
  • Export as PDF or Markdown
  • Batch Export to Notion
  • Bookmark & Highlight
  • Screenshot Tweet
Create Free Account

Includes 7-day Premium trial

Advertisement