Get Insights working with Quest 2 and UE5

[fsk]

Does Anyone know? I did all the things i did for 4.27 (open adb ports and adding commands to the UECommandLine.txt) but no luck. It newer connects…

[vlab22]

I made it work yesterday. (UE 5.3.2, maybe works with any UE5)

Requirements:

• UE 5.3.2
• Build/Install/Run your apk in Development mode
• adb commands working
  • adb device must show your Quest2

I followed this guide with some modifications, adjusting the paths and names according with your project and Unreal 5 installation.

The guide is for UE4.25 so some paths are different in UE5.

• UE4CommandLine.txt -> UECommandLine.txt
  • e.g: C:\Unreal\UE_5.3\Engine\Build\Android\UnrealGame

Note:
You don’t need this file, you can just create it somewhere paste the correct commands into it, and send it properly to your Quest2

Paste the code below into it adjusting to your scenario, I’ll explain each section.

../../../MyVRProject/MyVRProject.uproject /Game/Maps/Map01 -trace=log,counters,cpu,frame,bookmark,file,loadtime,gpu,rhicommands,rendercommands,object -statnamedevents -tracehost=192.168.1.XX -tracefile=/sdcard/UnrealEngine/MyVRProject/MostRecentTraceCapture.utrace

• MyVRProject:
  • Your project name, if you didn’t change anything it’s your “project folder name”
• /Game/Maps/Map01
  • a level/map, this is in my Content/Maps folder (Content/Maps/Map01)
• -trace=log,counters,cpu,frame,bookmark,file,loadtime,gpu,rhicommands,rendercommands,object -statnamedevents
  • trace stats to return etc, don’t mess it
• -tracehost=192.168.1.XX
  • The IP of your machine, the one running the UnrealInsights, this IP must be reached by your quest2 in your network (and do the adb port commands from the guide`)
• -tracefile=/sdcard/UnrealEngine/MyVRProject/MostRecentTraceCapture.utrace
  • This path doesn’t exist and it was not created at all but it works, maybe it’s unnecessary

Now, you must find your project/app files in the Quest2, the guide points to /sdcard/UE4Game/<ProjectDir>, this is different for UE5.3.2.

• You need the correct path to adb push the UECommandLine.txt

IT’S BETTER if you find it by yourself. It’ll probably be in e.g:

• /sdcard/Android/data/com.home.MyVRProject/files/UnrealGame/MyVRProject

  • com.home.MyVRProject
    • Android Package Name: Project Settings -> com.home.[PROJECT]
  • you must know how to navigate into it using adb shell and cd/ls commands

After finding the correct path, push the UECommandLine.txt file

• Into the folder with the UECommandLine.txt
• adb push UECommandLine.txt /sdcard/Android/data/com.home.MyVRProject/files/UnrealGame/MyVRProject

Now

• Run UnrealInsights
• Check Auto astarts analysis LIVE
• Run your app in Quest2
• UnrealSights must connect and open the trace stuff

PS: remember to follow the guide for some clarification

PS2: BE AWARE! Idk butI believe when I installed and ran a new build UECommandLine.txt was vanished so I needed to push it again.

[BabbyGames]

Hi,

I successfully pushed it using ur tutorial but the problem is that the Myproject.uproject / maps…
all these folders and files are only available when u launch from editor using usb debugging not when the game packaged/ exported normally

So, even when i push the UECommandline.txt it does not run as the game is already open and when i close and open the game again it Says That the project files are not available

There should be a way to Modify the UECommandline.txt Before the game even launches

Please reply

[MrFr3Man]

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.