# What is the optimal work flow for building and debugging Oculus Quest

**URL:** <https://forums.unrealengine.com/t/what-is-the-optimal-work-flow-for-building-and-debugging-oculus-quest/456411>\
**Category:** Debugging, Optimization, & Profiling\
**Tags:** Debugging, workflow, unreal-engine, oculus-vr, question\
**Created:** [October 4, 2019, 11:04am UTC](https://forums.unrealengine.com/t/what-is-the-optimal-work-flow-for-building-and-debugging-oculus-quest/456411 "2019-10-04T11:04:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattwallace](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@mattwallace](https://forums.unrealengine.com/u/mattwallace)\
**Post date:** [October 4, 2019, 11:04am UTC](https://forums.unrealengine.com/t/what-is-the-optimal-work-flow-for-building-and-debugging-oculus-quest/456411/1 "2019-10-04T11:04:33Z")

</div>

I have gotten my oculus quest setup for packaging and running the VR Template. The workflow for running my level is a pretty slow process IMO. Using the project launcher works fine but the lack of debugging within the engine is annoying.

I’d like the ability to use breakpoints in my blueprints and c++ code.

Also, is there a way I can mirror what I’m seeing in the headset inside of the unreal editor while I’m working on my app?

I’m hoping someone has a “better” workflow or at least a recommendation that I’m missing.

---

<div class="post-metadata">

**Author:** ![Brainversation](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Brainversation](https://forums.unrealengine.com/u/Brainversation)\
**Post date:** [November 30, 2022, 6:09pm UTC](https://forums.unrealengine.com/t/what-is-the-optimal-work-flow-for-building-and-debugging-oculus-quest/456411/2 "2022-11-30T18:09:50Z")

</div>

@mattwallace Did you ever find or come up with a optimal workflow?
