Open topic with navigation
PerfHUD ES 2.1
- Support debugging multiple contexts.
- Improve “Set Frame Delimiter” dialog box for multiple contexts and multiple frames.
- Improve stability in editing and applying user shaders.
- Better appearance in displaying program tree and performance information in Shader Viewer.
- Two directed tests are added: disable depth test and disable stencil test.
- Display PCB powers in Dashboard for shield.
- Better compatibility for loading profiling data.
On the host:
- Show correct bucket id and contribution in the Bucket List.
- Fix crashes for user shader in recapturing frame after editing, applying it or deleting it in Shader Viewer.
- Fix wrong range or crash for pack vbo buffer when stride exists in Geometry Viewer.
- Fix mismatch of uniform values between detail view and tooltip in program tree in Shader Viewer.
- Disable "Capture next frame" button when load debugger frame or profiler frame.
On the target:
- Fix the fps decrease problem when "Disable Filtering" directed test is enabled.
- Exclude glClear() from Draw Calls per Frame in Performance Dashboard.
- Fix force clear on stencil buffer and incomplete FBO.
- Fix crashing when VBO is mapped.
- Fix "Null Viewport" directed test.
- Disable counter 'GPU Idle' on T30.
- Be aware that using the Null Fragment Shader test causes your program object to be substituted for a new one. Setting the value of a fragment-side uniform will have no effect. The
glUniform* functions are automatically re-directed to the new program. Attribute bindings are automatically re-mapped as well.
- Note that
eglSwapBuffers does not perform an implicit
glFinish, so the visible frame may correspond to a program iteration that was executed in the past. As a result of this, there might be a small delay between the time that the user interacts with Performance Dashboard (eg, toggling a directed test), and the time that it appears to take effect. This is due to the fact that PerfHUD cannot modify a command buffer that has already been set up by the driver. The delay is noticeable only with highly GPU-bound applications that have low frame rates.
- Sometimes the frame buffer result of Emulation mode is different than the target side. This is because OpenGL ES has some extensions which cannot be mapped to corresponding OpenGL support on the host machine. If your target application is trying to use these extensions, the emulation can’t get the same result with target due to the lack of extension supporting. For example,
GL_OES_matrix_palette is a valid target OpenGL ES extension, but we can’t find corresponding support for it in your GeForce 8600 host GPU. In this scenario, it's recommended to use the Capture mode, which is more accurate and more valuable, rather than Emulation mode.
NVIDIA® GameWorks™ Documentation Rev. 1.0.200608 ©2014-2020. NVIDIA Corporation. All Rights Reserved.