The site has a new content architecture. We've added the ability to select your development device to show device-specific content. Please read our blog post Oculus Developer Center Update: Device-centric Documentation Architecture for more information.
All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.
This guide provides actionable guidance for tracking down and solving VR performance issues.
In order to create the best VR experience for your users, it is important to optimize your applications for peak performance on Oculus recommended spec hardware. Otherwise, you may find that your applications exhibit judder, flickering black areas on the peripheries, or other performance-related problems.
In general, performance issues arise because it can be difficult for applications and game engines to keep up with Rift’s refresh rate of 90 Hz. By carefully and systematically tracking down the issues that are causing performance problems and then implementing the necessary optimizations, you can create a significantly better overall user experience.
This guide targets both application developers and engine developers.
This guide addresses a range of tools and methods. We start by covering high-level approaches that help you to narrow down the basic causes for the performance issues that your application may be exhibiting. Then we delve deeper into lower-level tools and analytical approaches, including Event Tracing for Windows (ETW), Windows Performance Analyzer (WPA), and GPUView. These lower-level approaches can be very helpful for solving complex and subtle VR performance issues, especially for game engine developers.
At the end of this guide, we provide a step-by-step tutorial that utilizes all of the tools discussed in this guide, and includes code samples and screenshots.