search

KhronosGroup / VK-GL-CTS

Khronos Vulkan, OpenGL, and OpenGL ES Conformance Tests
https://www.khronos.org/
Apache License 2.0
521 stars 290 forks source link

Failed to capture a dedicated cts case using renderdoc #398

Open wangdefa opened 1 year ago

wangdefa commented 1 year ago

In the readme of glcts: https://github.com/KhronosGroup/VK-GL-CTS/blob/main/external/openglcts/README.md#command-line-options, there are options which is designed for capture the CTS, just like below: --deqp-renderdoc=[enable|disable] Enable RenderDoc frame markers

The problem is:

  1. When I run a group of CTS case(It may take serveral seconds), I can get a random frame. The cmdline parameter is "--deqp-case=dEQP-GLES3.functional.texture.wrap.astc_6x6.* --deqp-renderdoc=enable"
  2. When I specify a dedicated CTS case name, the cmdline parameter is "--deqp-case=dEQP-GLES3.functional.texture.wrap.astc_6x6.clamp_clamp_nearest_divisible --deqp-renderdoc=enable", I get nothing since the rendering process exit before I can launch a capture.

Is there anyone can help ?

rg3igalia commented 1 year ago

You're supposed to launch deqp from RenderDoc itself, avoiding problem 2. See https://renderdoc.org/docs/getting_started/quick_start.html and the Launch Application tab.

wangdefa commented 1 year ago

You're supposed to launch deqp from RenderDoc itself, avoiding problem 2. See https://renderdoc.org/docs/getting_started/quick_start.html and the Launch Application tab.

Yes, I also try to use the Launch Application tab to capture a single frame. The parameter settings is as below:

  1. executable path: org.khronos.gl_cts/android.app.NativeActivity
  2. Intent arguments: -e cmdLine \"cts --deqp-case=dEQP-GLES3.functional.texture.wrap.* --deqp-log-filename=/sdcard/NonMustpassDeleteStress.qpa --deqp-surface-width=256 --deqp-surface-height=256 --deqp-surface-type=window --deqp-screen-rotation=unspecified --deqp-renderdoc=enable --deqp-gl-config-name=rgba8888d24s8ms0\""

When I click the "Launch" button, and the result is the same as I said before.

  1. When I run a group of CTS case like "--deqp-case=dEQP-GLES3.functional.texture.wrap.astc_6x6.*"(It may take serveral seconds), I can get a random frame.
  2. When I specify a dedicated CTS case name like "--deqp-case=dEQP-GLES3.functional.texture.wrap.astc_6x6.clamp_clamp_nearest_divisible", I get nothing since the rendering process exit before I can launch a capture.
rg3igalia commented 1 year ago

Oh, no idea about launching it on Android, sorry. :(