A simple wireframe object that takes a CpuMesh, for use in debugging. #552
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Unfortunately, this approach has some limitations: meshes with shared vertices will not be displayed correctly.
|
This would be extremely helpful for debugging my math visualizations. Thank you! |
Not-A-Normal-Robot
suggested changes
Aug 24, 2025
| } | ||
|
|
||
| fn id(&self) -> EffectMaterialId { | ||
| //TODO! |
| use crate::core::*; | ||
| use crate::renderer::*; | ||
|
|
||
| pub struct Wireframe{ |
There was a problem hiding this comment.
Missing space, you should use cargo fmt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This uses that barycentric coordinates trick: unfortunately, this approach has some limitations: meshes with shared vertices will not be displayed correctly.
I just did this for personal use -- so feel free to disregard for any combination of reasons (technical/aesthetic/etc) -- and there's also a couple of points in the code (specifically GeometryIds) where I didn't know what to do.
Anyway, if you're interested in the feature, I could extend the code to handle meshes with indexes (by duplicating verts). It's also probably possible to handle effects, although I'm not sure that's necessarily desirable.
I would obviously also add some documentation.