04-11-2019 08:57 AM
04-12-2019 06:47 AM
04-16-2019 11:31 AM
motorsep said:
What's the consensus about UE 4.22 performance on Go / Quest ?
When I tried one of the later previews, performance was horrible with ES2 and ES3.1. Since there is no 4.22 release with current Oculus integrations on Oculus github, I assume the reason for it is not that Oculus is busy prepping for Rift S / Quest launch, but because 4.22 performs worse than 4.21.x.
Please enlighten me 🙂
04-16-2019 04:25 PM
aussieburgerVR said:As I posted already 4.22 has terrible performance on the Go. I'm guessing the same for Quest? I'm really hoping Oculus can fix this (or push Epic to fix it via a hotfix if their side) as there are lots of nice new 4.22 features I was hoping to use 🙂
I've only briefly tested on the Rift and it seemed ok there but my project is more mobile performance so probably wouldn't notice a drop in performance anyway.
04-23-2019 11:19 AM
motorsep said:
aussieburgerVR said:As I posted already 4.22 has terrible performance on the Go. I'm guessing the same for Quest? I'm really hoping Oculus can fix this (or push Epic to fix it via a hotfix if their side) as there are lots of nice new 4.22 features I was hoping to use 🙂
I've only briefly tested on the Rift and it seemed ok there but my project is more mobile performance so probably wouldn't notice a drop in performance anyway.
https://developer.oculus.com/blog/understanding-gameplay-latency-for-oculus-quest-oculus-go-and-gear... check the "UE4 and RHIThread" part as it relates to 4.22
You can skip new rendering pipeline. Quoting from the discord:
r.rhicmdbypassrequires: r.rhithread.enable
I haven't tried it though.
04-23-2019 12:43 PM
04-24-2019 10:34 AM
motorsep said:
@aussieburgerVR Did you by chance report your findings to Oculus (using their bug tracker) ?
04-24-2019 11:03 AM