-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If I open a trace, modify a shader, perform a new trace, the shader list does not update. #1195
Comments
Did you happen to have a "RenderPass" node selected in the command tree? I was unable to repro this with the steps from the title, however, I have noticed that the indices in the tree nodes are strange and that if you select the render pass node, the textures/shader view is disabled. |
Tried a few more times to reproduce this and could not do so. Closing for now as discussed with @AWoloszyn. Please reopen with more detailed repro steps if you can reproduce, thanks! |
When selecting a command at a point in the trace where all shaders have been created, then opening/capturing another trace, will cause the shader view to stop updating itself, unless a command is selected in the (new) trace before all shaders were created. Fixes google#1195 Fixes google#1309
* Invert gapit frame boundary flag for sensible default value * Change help message * fix presubmit
This was specifically for a Vulkan trace.
The shader list does not seem to update ever again, nor am I able to push new shader modifications.
The text was updated successfully, but these errors were encountered: