How to Launch App within Oculus Quest 2 using Meta Quest Developer Hub 3.2
Hi, I am using Unreal Engine 5.02 as engine, and I am using the VR Template from the engine. I can generate the apk file without any problem. I add the apk file from my computer to MQDH 3.2 and everything seems fine. The problem that I am facing is the Launch App option from the 3 dot is not available in MQDH. The only thing that I can do is uninstall. However, I already have another apk from a different project and the Launch App option it is available. Has anyone known how to solve this problem? BTW, I checked to File Manager ---> Apps---> and tried to launch the app and it is not working. Same problem as described in my previous paragraph. I am connecting my Oculus Quest 2 using the link cable. The image below shows that the other apk have the option to be Launched within the Quest 2.
Informal Poll, Which Build Environment is best?
I'm just getting started with developing for the Meta Quest, and I am wondering what "build" environment most of you use? I guess there are basically 3: 1. Native coding (Visual Studio?), 2. Unity Engine, and 3. Unreal Engine? I have installed all 3 so far. Found an outdated tutorial on creating a basic app with Unity, after what seemed like several hours sifting through scattered information (could have been organized much better), most of the info for unity did not match the version I installed, I ended up with a very rudimentary "virtual" world on my device, but the controllers were non-functional. All that took about 15minutes to "compile". As for unreal engine, I have only been playing around with it's user interface, but haven't gotten into the actual "coding" yet. Off hand, it seems like it might work better? Lastly, there's the native made? Just code for the most part? Are there any other options? Which one do you prefer? Can you list any pros and cons for each? Thank you in advance for taking the time to read this and hopefully respond.Tips on how to attain the player's boundary type in Oculus Quests VR Preview (UE4-27.2)
Hello everyone, I am currently developing a VR game within Unreal Engine 4, and I am trying to ascertain within my blueprint whether or not the player is using a room-scale or stationary boundary while in VR Preview. I have attempted to work with the nodes within the Oculus Library - Guardian folder, however they currently don’t appear to be returning any values. Does anybody know if there is a more simple way to attain this information? The only value I need is the player’s boundary type.
Movable Lights limits? Oculus quest 2 / Unreal Engine
Hi guys, sorry for the long text but I feel that it's easier if you know my background or the lack of it. I'm a neuropsychologist trying to build alone a 'simple' home to test a possible intervention in VR for patients with traumatic brain injury. I recently got the Oculus Quest 2 because the wireless feature it's the best to use in a hospital setting. I have zero formation in computer science or programming knowledge. However, I learned a lot with all the available tutorials online about the UE blueprint system and I managed to do almost everything that I want. What I'm trying to achieve: I have 4 square rooms (kitchen/dining/bedroom and a living room) and each one of them has ONE movable light (Points light) linked to a light switch that can be turned on/off. I did this so the patient has to work with some type of energy cost, each room has a different cost being turned on (ex living room cost 1 per second, while the kitchen cost is 2). In the session, the patient has to do some daily living activities to earn money and 'pay' the energy cost at the end of the sessions. My questions: Is it the limit, described in the UE4 documentation for mobile, is it the same for oculus quest 2? A total of 4 movable lights in the whole level? Or you can't have more than 4 movable lights touching? For example, Can I have 2 lights per room? Is it better to have two movable lights with a smaller attenuation radius (ex. two with 750) or one movable light with a larger attenuation radius (ex. 1500) Is the number of draw calls linked to how many movable lights you have at the time? I posted below the current triangle counts and draw calls that I get in my scene. How can I optimize the number of draw calls, since I can see that I'm way over the limit (170-175?) for the Oculus Quest described in the Oculus Documentation? I see that I have room for more objects in my scene since the described is 750k to 1kk, Is the number of triangles and draw calls limit higher for Quest 2? My problems: The game automatically closes when I try loading the level I created inside Quest 2. No errors givens, the HMD simply returns to the home screen one to two seconds after loading the level and showing the objects on the screen. I can run the game with no problem when I'm using the usb3 cable linked to my computer using UE VRPreview. This got me thinking that maybe I'm running out of memory or something and what I'm doing is "too much" for quest 2 to handle? The initial level that I use to load the main level runs fine inside Quest 2. I'm using the "MotionControllerMap" created by the unreal engine. Triangle Counts: imgur.com/Dy0gxon Draw Calls: imgur.com/cpIWTBc Sorry for the long post, I really appreciate any help.
