-
-
Notifications
You must be signed in to change notification settings - Fork 305
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
Panic when drawing no_fill() without also calling stroke_weight() #627
Comments
I'm not sure if all of the following are related, but I've seen a very similar stack trace in the following examples in Generative Design: p_1_0_01.rs Could this be related to #631 as well? |
I also get a similar stack trace when running those same examples @sbauer322 mentioned, at least for the ones I've tried:
Interestingly, these all run with no issue when I switch from the locally built # in generative_design/Cargo.tml
[dev-dependencies]
# nannou = { version ="0.14.1", path = "../nannou" }
nannou = "0.14.1" |
For what its worth, @justinsilvestre , #636 might have fixed this behavior for the examples mentioned and was merged this morning. If you pull the latest code from master and run the example again then it should work (at least it does for me). My basic understanding, thanks to the people of the Nannou Slack, was that if nothing is actually being drawn in the window then wgpu would crash due to 0 vertices. In the case of some of those examples, such as |
@justinsilvestre Hi bro! :) @sbauer322 Ahh yeah I was thinking that could be the case with the mouse coords. That's probably different between desktop environments, which would explain why it happens to others on the first frame, but didn't happen to me until I moved my mouse to make the Rectangle shrink on purpose. |
I've managed to find a few examples that are crashing now when an object that is set to
no_fill
does not also callstroke_weight(val)
. In these instances, running a backtrace reveals that the line below is where nannou panics.let point_buffer = device.create_buffer_with_data(points_bytes, vertex_usage);
here is the full backtrace.
The text was updated successfully, but these errors were encountered: