RenderDoc Meta Fork v55.0 does not show Tile Timeline or Tile Browser for UE 5.2 builds
I have an application in Unreal Engine 5.2. When I try and view a captured frame, I do not get any information in the Tile Timeline. It appears to load the capture fine, and I get information in the Timeline, Event Browser and other windows. I get the the following error at the end of the log: Android 1469 09:54:25 vk_counters.cpp(1361) Error Failed to retrieve vulkan renderstage trace results. Here is the full log for context (username and serial numbers have been sanitized): https://pastebin.com/HnCgZwAE Is this a known issue? Is there any known way to resolve it? Any help in getting the Tile Timeline and Tile Browser working would be most appreciated. Thanks!
Is profiling of a native Unity plugin with RenderDoc, on Quest2?
If I wanted to profile a native Unity plugin responsible for rendering operations via OpenGL on Quest2, is this supported with the Meta fork of RenderDoc? I have included the following OpenGL push/pop debug groups throughout my plugin. GLES31Ext.glPushDebugGroupKHR(GLES31Ext.GL_DEBUG_SOURCE_APPLICATION_KHR, 0, -1, "myMessage"); When analyzing my capture with RenderDoc, I see my gl calls in the event browser, but I don't see the debug groups show up anywhere. I have ovrgpuprofiler enabled as well. Also, I don't see any values in the duration column of my event browser.Renderdoc Meta Fork 44.1 - Failed to install Android remote server
Hi, I've been having this really frustrating issue with Renderdoc Meta Fork (previously called Renderdoc for Oculus). When selecting replay context (both Oculus Quest 2 and Oculus Quest 2 Profiling Mode) I'm getting a following error message: "Failed to install Android remote server for unknown reasons: Couldn't install APK(s). stderr: . lease check that your device is connected and accessible to adb, and that installing APKs over USB is allowed." Of course I have adb configured and Quest 2 in developer mode. I am able to install any apk's and when using regular Renderdoc (not the oculus-specific fork) the replay context attaches successfully. I've been able to succesfully connect with previous version of this tool (v40.1) in the past. However, when I downgraded today, even the old version showed the same error. I have no idea why this issue magically popped up, but I would be really glad if something could be done about this. Here's the renderdoc log if this is of any importance: RDOC 008684: [13:09:16] core.cpp( 497) - Log - RenderDoc v1.22 Windows 64-bit Release (RENDERDOC_FOR_META_QUEST) loaded in replay application RDOC 008684: [13:09:16] core.cpp( 500) - Log - Packaged for RenderDoc Meta Fork (44.1) - www.oculus.com RDOC 008684: [13:09:16] core.cpp( 508) - Warning - Couldn't open socket for target control RDOC 008684: [13:09:16] settings.cpp( 460) - Log - Loading config from C:\Users\<user>\AppData\Roaming\RenderDocMetaFork\renderdoc.conf QTRD 008684: [13:09:16] qrenderdoc.cpp( 169) - Log - QRenderDoc initialising. QTRD 008684: [13:09:16] mainwindow.cpp( 270) - Log - Disabling error reports due to invalid commit hash QTRD 008684: [13:09:16] mainwindow.cpp(3202) - Log - Couldn't load layout from "C:/Users/<user>/AppData/Roaming/QRenderDocMetaFork/DefaultLayout.config" "Nie można odnaleźć określonego pliku." RDOC 008684: [13:09:16] android_tools.cpp( 347) - Log - Initialising adb using 'C:\Program Files\Android\platform-tools\adb.exe' QTRD 008684: [13:09:16] toolwindowmanager.cpp(1548) - Warning - area parameter ignored for this type RDOC 008684: [13:09:16] d3d11_replay.cpp( 142) - Log - Running replay on nVidia / NVIDIA GeForce RTX 3060 31.0.15.1694 RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 root' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.manufacturer' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.model' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:17] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell "getprop ro.product.manufacturer"' RDOC 008684: [13:09:17] streamio.cpp( 428) - Warning - Socket unexpectedly disconnected during reading RDOC 008684: [13:09:17] remote_server.cpp(1211) - Warning - Didn't get proper handshake RDOC 008684: [13:09:17] streamio.cpp( 428) - Warning - Socket unexpectedly disconnected during reading RDOC 008684: [13:09:17] remote_server.cpp(1211) - Warning - Didn't get proper handshake RDOC 008684: [13:09:18] d3d12_sdk_select.cpp( 370) - Log - System D3D12 runtime is version 2 RDOC 008684: [13:09:18] d3d12_replay.cpp( 111) - Log - Running replay on nVidia / NVIDIA GeForce RTX 3060 31.0.15.1694 RDOC 008684: [13:09:18] vk_replay.cpp(4711) - Log - Created device. RDOC 008684: [13:09:24] streamio.cpp( 428) - Warning - Socket unexpectedly disconnected during reading RDOC 008684: [13:09:24] remote_server.cpp(1211) - Warning - Didn't get proper handshake RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell "getprop ro.product.manufacturer"' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm list packages com.oculus.renderdoccmd' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.cpu.abi' RDOC 008684: [13:09:24] android.cpp(1187) - Log - Starting RenderDoc server, supported ABIs: RDOC 008684: [13:09:24] android.cpp(1189) - Log - - armeabi_v7a RDOC 008684: [13:09:24] android.cpp(1189) - Log - - arm64_v8a RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.product.cpu.abi' RDOC 008684: [13:09:24] android.cpp( 480) - Log - Checking for server APK in C:\Program Files\RenderDocForMetaQuest/plugins/android/ RDOC 008684: [13:09:24] android.cpp( 487) - Log - APKs found: C:\Program Files\RenderDocForMetaQuest/plugins/android/ RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:24] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 install -r -g "C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm32.apk"' RDOC 008684: [13:09:29] android.cpp( 538) - Log - Installed package 'C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm32.apk', checking for success... RDOC 008684: [13:09:29] android.cpp( 374) - Log - Checking installed version of com.oculus.renderdoccmd.arm32 on 1WMHHA6DBG1454 RDOC 008684: [13:09:29] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm dump com.oculus.renderdoccmd.arm32' RDOC 008684: [13:09:29] android.cpp( 416) - Log - Installed server version (122:441) is compatible RDOC 008684: [13:09:29] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell getprop ro.build.version.sdk' RDOC 008684: [13:09:30] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 install -r -g "C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm64.apk"' RDOC 008684: [13:09:34] android.cpp( 538) - Log - Installed package 'C:\Program Files\RenderDocForMetaQuest/plugins/android/com.oculus.renderdoccmd.arm64.apk', checking for success... RDOC 008684: [13:09:34] android.cpp( 374) - Log - Checking installed version of com.oculus.renderdoccmd.arm64 on 1WMHHA6DBG1454 RDOC 008684: [13:09:34] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm dump com.oculus.renderdoccmd.arm64' RDOC 008684: [13:09:35] android.cpp( 416) - Log - Installed server version (122:441) is compatible RDOC 008684: [13:09:35] android_tools.cpp( 321) - Log - COMMAND: C:\Program Files\Android\platform-tools\adb.exe '-s 1WMHHA6DBG1454 shell pm list packages com.oculus.renderdoccmd' RDOC 008684: [13:09:35] android.cpp( 573) - Error - Couldn't install APK(s). stderr: RDOC 008684: [13:09:35] android.cpp(1216) - Error - Failed to install RenderDoc server appPlease help me understand Unity Profiler and RenderDoc output for my simple app
I have a simple scene that is performant on PCVR, but struggles to make a reasonable frame rate when run natively on Quest. After stripping out about half the scene geometry and some of the shadow overhead, it is still failing to run smoothly so I've run the Unity Profiler (Standalone) and RenderDoc to try to understand where my bottlenecks are. This development is currently running in Unity 2021.2.14f1, GLES, with up-to-date Oculus XR Plugin and Oculus Integration packages. Please look at the following and let me know if anything jumps out that I should look for. First, Unity profiler: The profiler suggests nearly 32ms of my 43ms PlayerLoop is waiting in EarlyUpdate.XRUpdate->OculusRuntime.WaitToBeginFrame. I've seen discussion online that suggests this is most likely related to "Vsync" like timing and missing a frame budget could cause excess time waiting on the next available frame. But I don't understand why it should appear to be almost 33 ms. At 13ms per frame @72Hzthat's almost 2.5 frame budgets every frame cycle. Because I can't get accurate timings of the GPU in the profiler, I can only see the Batches (20) and Tris count(~27K) and these should both be well-within recommended limits. I've highlighted what I *think* illustrates the RenderLoop timing as best I can and it seems to imply some 4-5 ms where the RenderThread is not in WaitForGfxCommands... Trying to dig deeper into the GPU, I've captured a frame under RenderDoc. Two quick up-front questions about RenderDoc and "Gather Timings", if anyone knows the answer... You must capture the frame under "Quest Mode", but can Replay it under "Quest Mode" or "Quest Profiling Mode" I get ~42ms under the former and 12ms under the latter. Which one is more trustworthy here? Should Gather Timings report times for each stage in the series, because I can only get it to report for the entire frame. I'd love deeper information for timing, but I can't seem to get at it. Finally, RenderDoc echoes the 20 Draw Calls, but I can't tell whether I'm doing anything else here which should be causing such poor performance. My overall framerate is around 27, but I can't understand why. Please advise if I've got something obvious going on, but I'm at a loss to explain the behavior I'm seeing. TIA, G7Quest2 + Renderdoc Meta Fork - Injection failed : couldn't locate the launched activity....
Hi, This started happening since last week. The development APK build launches through RenderDoc OK, but while the application is loading, Renderdoc Meta Fork returns this error message: I've tried Renderdoc Meta Fork versions 39.2, 39.6,40.1,44.1,50.1 and 51.1. It seems to be quite random when it appears. The only way to fix it at the moment seems to be to keep installing various versions on the Quest2 until the error doesn't appear anymore. Sometimes the ADB and Renderdoc log/dmp files get updated during a crash, examples are shared here: https://drive.google.com/drive/folders/1-z4-VxMAwEnXskJ6hnngPlxAIaIWNVKC
Interpreting renderdoc meta fork tile timeline
Hi, I started profiling our application with the renderdoc meta fork, and i'm having trouble reading the results. The application is made with unity (2021.3 branch), and I'm profiling on oculus quest 2. Renderdoc is version 51.1, headset is up to date with firmware v51. Everything works fine on the capture / profiling steps with renderdoc; I can open a capture, click on "Time durations for render stages", and the tile timeline gets populated with the data I was looking for : Since I'm on quest 2, I'm expecting to see only one surface in the timeline, corresponding to the rendering in multiview of the application. So the rendering step works fine, but strangely there is an other surface being computed in the timeline right after. I cannot really relate this surface to anything in the application (there are no post effects set up in the project), but I can see with the tile browser that the surface seems to be affected by the fixed foveated rendering setting of the application, while the first one does not seem to be affected. Anybody would happen to know what this surface could relate to ? Thanks for the help,Meta GPU counters on RenderDoc
Hello, I'm trying to use the RenderDoc python API with the RenderDoc Meta fork to automate some profiling tasks. However, even though I'm able to connect to the RenderDoc Meta fork remote server (profiling mode), if I call `ReplayController.EnumerateCounters()` I don't get the Meta counters back. Is there a way to access those counters via python? Cheers
RenderDoc crashes apps
I am using RenderDoc Meta Fork 44.1 and Quest 2 with OS VERSION: 49068160412800150 and Version: 47.0.0.282.341.428237303 Lately, anytime RenderDoc launches a Unity built application, it crashes with a backtrace: /apex/com.android.runtime/lib64/bionic/libc.so /system/priv-app/VrDriver/VrDriver.apk ... After failing to launch, any subsequent attempts to launch within Quest or using Meta hub also fails with a crash until the headset is restarted. I should note the applications I tried start and work fine unless they are started from RenderDoc.
RenderDoc connected makes development build crashes instantly
Trying to use RenderDoc for the first time to debug frame from the device gpu. I made a unity build (Unity 2021.3.12 LTS) with development flag enabled and debug script enabled. Then I loaded it on the oculus, tested and it runs without issues. Then I switched from local to Device in the RenderDocMetaFork (v441), tried to launch the build from Launch Application tab like described here, but the build crashes instantly, if I try to open normally the build when RenderDocMetaFork is connected the build crashes.
Renderdoc for Quest: no Render Stage Trace
Following the instructions at https://developer.oculus.com/documentation/tools/tools-renderdoc-renderstage/ I expected to see a render stage trace. But clicking the "oculus logo" button in the Event Browser has no effect for me, and the Tile Timeline view is blank. I'm using Oculus Mobile SDK 1.40
