Renderdoc Meta Fork not providing performance counters for compute shaders
Hello! As the title says, I have been having issues profiling compute shaders. I am doing and investigation on VR volume rendering on the Meta Quest 2; and the performance counters on the Renderdoc Meta Fork have been fundamental on my work. But, right now, the only information that is provided on the counter are the millisencos for each pass, only when taking about compute shaders (the render passes present all the data as expected). At first I thought that it is as expected for some fields to present missing values, since we are not using the raster pipeline, but the texture pipelines are also reporting 0 fetch stall & 0 bytes readed; wich is not true since this shaders perform a surface nets algortihm. Am I missing something? Has anyone encoountered this issue? Also, it is not a dead-or-live situation, but the shaders run very fast; and would love to look a bit closer.Quest2 + 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
