Forum Discussion
Developer QOL General
I'm trying to find the most comfortable flow to iterate on an app. What type of setups and strategies do you guys use to make it all less painful? I got accustomed to using Virtual Desktop + Unity where you can code and launch without having to remove the headset. Virtual Desktop does not appear to be capable of context switching w/ Android Studios, on top of the fact that Quest Pro 2 is now discontinued means that I am now forced to constantly deal with scalp thrashing from taking the headset off and on again. Should I go with the Bosworth strat and just go bald?
2 Replies
Replies have been turned off for this discussion
With Meta Spatial SDK you currently need to deploy your applications to a real headset to see them running.
A Meta Spatial SDK app is a fully immersive app which means that it will replace Virtual Desktop when running (only one fully immersive app can run at a time).
We do support a feature called Input Forwarding (https://developers.meta.com/horizon/documentation/spatial-sdk/spatial-sdk-tooling-castinputforward) which may ease your flow. If you have two headsets, you can run Virtual Desktop in your main headset and then set up a cast window through MQDH which casts your second headset's view. You can then use Input Forwarding to control your second headset through the cast window. This would allow you to stay in Virtual Desktop the entire time while running and testing your app through the Cast window you're seeing in Virtual Desktop.
We are aware this is still not an optimal workflow and the team is thinking hard about improvements we can make.I use it, and it does the job for me...
My only wish is to have a virtual controller in castinputforward. Gaze is not enough, and I should reconfigure the helmet (remove hand tracking and remove batteries from my controller) whenever I want to use it.
Something like https://github.com/meta-quest/immersive-web-emulator
