Skip to content
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

Have Wireframe view overlay a colored (red?) wireframe. #818

Closed
AWoloszyn opened this issue Jul 27, 2017 · 3 comments
Closed

Have Wireframe view overlay a colored (red?) wireframe. #818

AWoloszyn opened this issue Jul 27, 2017 · 3 comments

Comments

@AWoloszyn
Copy link
Contributor

Currently the wireframe is the same color as the mesh, making it more difficult to see. If we re-write the shader to make it red or inverted, we would be able to see which draw-call we are referencing.

@dsrbecky
Copy link
Contributor

dsrbecky commented Aug 4, 2017

Alternative would be to provide the client with the screen space vertex positions, and let the client render it.

I am think forward to situation where the client might want to know the raw positions anyway so that can user click the vertex and debug it.

@ben-clayton
Copy link
Contributor

Yup, that's the plan.

@ben-clayton
Copy link
Contributor

Closing for #817

purvisa-at-google-com pushed a commit that referenced this issue Sep 29, 2022
This extension lets us add a "divisor" to some vertex attribute
bindings used in instanced rendering. See chapter "Vertex Attribute
Divisor in Instanced Rendering" in the Vulkan spec, which has a bit of
pseudo code at the end that recaps how divisor values may be used.

Bug: b/190150915
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants