Pico 4 and Unity Profiler

Unity Engine
, , , ,
1

Hello,

im developing an App with Unity Open XR for the Pico 4. My biggest problem at the moment is, that i cant connect the Unity Profiler analysis tool to the running app at the headset. I really tried everything and spend half day to find a workaround, but without success. Maybe someone else encountert that problem and could help me?

Things i tried:

  • Installed Android SDK and checked on console with adb devices that pico4 is connected.

  • activated Development Build … in the Build Settings in Unity.

  • tried to connect Profiler via Wifi, but without success.

  • of course the headset is in developer mode with usb debugging enabled.

  • tried to activate/deactivate option automatic profiler connection

  • got the latest Unity and Pico Open XR versions, and XR Toolkit pp.

I dont know why, but im really frustrated and i hope someone can help me out.

2

I only profile via USB. Sometimes there are multiple ADB instances. Restart your PC, open the project, make sure autoconnect profiler is checked and build and run. This almost always works for me

3

Hey thank you for your answer. I tried restarting my PC but its still not connecting…

4

Does regular adb (like install and run) work?

5

Hello !

I’m in the same situation as the OP was (I tried everything I tried aswell). Adb Logcat works fine in Unity Editor. I have other similar projects that work “fine” (it’s always annoying to connect the app to the profiler but it’s always been the case with Unity’s Profilers).

The only difference is that I use a Vive Focus 3.

If you have any idea on what could cause this, I’m open to suggestion !

@applisations do you remember what was the solution you found ?

6

Hi! Even tho this is an old thread me and my team came across very similar problem. We needed to get build with profiling enabled for performance testing.

02-04 14:29:03.602 23061 23061 F DEBUG   :       #00 pc 00000000001f39c4  /vendor/lib64/hw/vulkan.kona.so (!!!0000!8d728ae2d4087ff5667ded39962458!76b617b5a74!+116) (BuildId: ---------------------------------)
02-04 14:29:03.602 23061 23061 F DEBUG   :       #01 pc 00000000000e5df8  /vendor/lib64/hw/vulkan.kona.so (qglinternal::vkCmdEndDebugUtilsLabelEXT(VkCommandBuffer_T*)+56) (BuildId: ---------------------------------)

This is the only thing I was able to get from ADB logcat this gave me a clue that vulkan might be the coulprit. Disabling

Auto Graphcis API
Selecting and deleting Vulkan as graphic API (for our Pico game it was not mandatory).

image
image423×118 4.41 KB

Enable development build
Enable Internal Profiler (even tho it’s depricated I saw in Pico documentation that it might be necessary to be on if you want profiler to be in use.

image
image432×139 8.53 KB

Enter Pico headset IP into direct connect (not fully sure why but USB profiling on my machine is not working as expected. Declining my connection request).

image
image470×310 14.2 KB

Additional things you might want to try

  • Kill any adb process from task manager
  • Pick diffrent SDK for target and minimum version (pico is android 10)
  • Update pico to latest version
  • Make sure deweloper mode with debuging is enabled in headset.

Wish everyone luck with their games & pico development!

3 Likes