I have built a Windows .exe for my VR project. It’s not optimised enough to be packaged for Android natively on the device at this moment in time.
I currently run it by Wired Quest Link or Air Link to my PC and simply run the app.
I am hoping to send this to a client so I can get their feedback. The client does not have much experience with an Oculus Quest and does not have their own device, so I will be sending mine for them to use.
What’s the best method to tackle this? Presumably I’d need to give them my Oculus account details to sign into the device, and then sign into the Oculus software which they would need to install.
Is there anything that avoids this, simply where they can just plug in my Oculus, double click the exe and off they go? Presumably not, but as little effort on their side as possible would be ideal if anyone has any suggestions on simplifying the process? Possibly create a temporary account that avoids me giving them mine?
Edit: I realise the Oculus forums may be more productive but thought I’d see if anyone here has experience sending builds from UE to clients!
Hi Duubz15 , not advised to be sharing your dev account details with your client.
Some options you could try
doing a video call with your client where you demonstrate the build to them using the oculus mirror tool that will allow you to share your display and have them see what you see in VR on a live call. The mirror tools are available in the Oculus support folders. Virtual Reality for Architecture with Twinmotion | Webinar - YouTube this video has how to use the tool at 3min 55sec or so. the video can also help with some idea and techniques for optimising scenes i.e drop lights and shadows screenspace reflections etc although this is for twinmotion the techniques to Unreal are similiar. If it is for a client for first time first feedback performance is better than quality. So i would suggest having a more stripped down application that can build to apk for testing. However if time does not permit this and the client is to test it themselves , if they cannot meet you to test it, then creating a secondary temp account or using their own is your only other option. Unfortunately though there is no way around installing oculus software and drivers as it is required to enable the oculus link to run.
Unfortunately client will have to download oculus software on their pc to run it on their device , either airlink or via link cable. If they are not technically inclined there is lots to go wrong with this method such as drivers not detecting , HMD not detecting, clients hardware not up to spec ,etc. which could end up frustrating your client.
My suggestion is the video mirror call option of you driving the presentation to them. You could also record the session using OBS providing the client with a recording they may go through later with their teams if necessary providing you timestamp references with feedback changes etc. This is the best way to protect your developer account details, and prevent passing the burden of technicalities onto client. In my experience this method also speeds up feedback reviews as you can have a lot more video calls in shorter build cycles, and then later focus on quality once key build points are met for client.