-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Add render diagnostic functions for reading from a buffer #22326
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
base: main
Are you sure you want to change the base?
Conversation
tychedelia
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not blocking but would be nice to add vec2/3/4. thanks this is great!
| name: Cow<'static, str>, | ||
| is_f32: bool, | ||
| ) { | ||
| let dest_buffer = self.device.create_buffer(&BufferDescriptor { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probs not a huge deal since this is debug code but we could probably re-use these allocations
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah we could reuse them or suballocate from one larger buffer, but I didn't want to deal with the complexity of that... Decided to go the dumb route for now.
Sadly bevy diagnostics only supports a single f64 value :/ |
pcwalton
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please. Would be nice to have i32 support as well but obviously we shouldn't block the PR on that.
|
Actually going to punt on i32, it's rarely used in graphics contexts. |
See release note file.
Tested locally on a modified copy of Solari.