Unreal Insights Quest 2 UE5

Did you ever figure out how to do it? Been trying to get it working all day with no luck for UE5.

The official tutorial doesn't work for me. Confused.

I'm unable to get this working either. Anyone found the answer?

I was able to get unreal insights working for apps running on Quest 2 from UE 5.2 using Unreal's "Project Launcher". If you are unfamiliar, it is a powerful feature that lets you fully customize your builds and save the different types of builds you do as "profiles". Then you can just launch a profile and all the applicable settings for that profile will be built and deployed, including the command flags needed to get the game to talk to insights.

More on project launcher:
https://docs.unrealengine.com/5.2/en-US/using-the-project-launcher-in-unreal-engine/

The difference between this way and the other way from the guide is that your quest will be sending the profiling data over the network.

1. Get the the IP address of your computer (you can use "ipconfig" in a command line on windows) on the local network and
2. Connect the headset to the same network and/or disconnect air link and attach with usb cable as if you are doing a normal build to device
3. Tools > Project Launcher in Unreal
4. Create a new profile using the Add button.
5. In the "Build" section, open the Advanced Settings dropdown and add the same commands documented in the original guide (https://developer.oculus.com/blog/get-started-with-unreal-insights-on-the-oculus-quest/). The only difference is to add your computer's IP you got from step 1 to -tracehost instead of 127.0.0.1
   

    

6. In the "Cook" section select "By the book", select "Android_ASTC" for platforms, and for maps select whichever maps you want to test with
7. For the "Package" section select "Do not package"
8. For "Archive" uncheck
9. For "Deploy" section select "Copy to device" and check Quest 2. You should see it as long as your device is connected via usb and adb is able to see it (adb devices)
10. For "Launch" section you can leave as default or set initial map to a specific map you want to profile.
11. You can rename the profile by clicking on the name at the top. Now you can click back and select the launch profile button in the project launcher window. Once the window says Launching on device, you should be able to see live data coming into insights

I posted a solution into Unreal Forum:
https://forums.unrealengine.com/t/get-insights-working-with-quest-2-and-ue5/529386/2?u=vlab22 

Hello everyone. Maybe it is no longer relevant for the author of the post, but for those who are still looking there is a much simpler option, tested on UE 5.5 and Quest 2.
Here are 2 commands for adb to turn on recording and turn it off at the right time. Important! Correct 192.168.1.1XX in both commands to the IP of your PC on which you are going to receive traces.

adb shell am broadcast -a android.intent.action.RUN -e cmd ‘Trace.Send 192.168.1.1XX cpu,gpu,frame,log,counters,bookmark,file,loadtime,rhicommands,rendercommands,object’

adb shell am broadcast -a android.intent.action.RUN -e cmd ‘Trace.Stop 192.168.1.1XX’

Total:

1. Enable Unreal Insights on your PC.
2. Launch the packed game Development or Debug on the helmet
3. Activate the first command at the moment when you want to start recording
4. Activate the second command at the moment when you want to stop recording
5. View the result in Unreal Insights on the PC

Naturally, your devices must be on the same local network, you must have access to debug Quest 2 via adb. You may also need this command, I don’t know for sure, but I used it once.

adb reverse tcp:1980 tcp:1980

If you have the Meta Quest Developer Hub app installed, you can add Custom commands to avoid manually entering the start and stop of traces.