-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Example 3d/pbr.rs
panics
#16959
Labels
A-ECS
Entities, components, systems, and events
C-Bug
An unexpected or incorrect behavior
C-Examples
An addition or correction to our examples
S-Ready-For-Implementation
This issue is ready for an implementation PR. Go for it!
Milestone
Comments
The first commit that causes the panic is 460de77, but it just turns a warning into a panic. The first commit that displays
is 17e5048. |
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 27, 2024
# Objective - Fixes #16959 - The `pbr.rs` example in the 3d section panicked because of the changes in #16638, that was not supposed to happen ## Solution - For now it's sufficient to introduce a `never_param_warn` call when adding the fallible system into the app ## Testing - Tested on my machine via `cargo r --example pbr`, it built and ran successfully --------- Co-authored-by: Freya Pines <[email protected]> Co-authored-by: François Mockers <[email protected]>
mockersf
added a commit
that referenced
this issue
Jan 3, 2025
# Objective - Fixes #16959 - The `pbr.rs` example in the 3d section panicked because of the changes in #16638, that was not supposed to happen ## Solution - For now it's sufficient to introduce a `never_param_warn` call when adding the fallible system into the app ## Testing - Tested on my machine via `cargo r --example pbr`, it built and ran successfully --------- Co-authored-by: Freya Pines <[email protected]> Co-authored-by: François Mockers <[email protected]>
ecoskey
pushed a commit
to ecoskey/bevy
that referenced
this issue
Jan 6, 2025
# Objective - Fixes bevyengine#16959 - The `pbr.rs` example in the 3d section panicked because of the changes in bevyengine#16638, that was not supposed to happen ## Solution - For now it's sufficient to introduce a `never_param_warn` call when adding the fallible system into the app ## Testing - Tested on my machine via `cargo r --example pbr`, it built and ran successfully --------- Co-authored-by: Freya Pines <[email protected]> Co-authored-by: François Mockers <[email protected]>
mrchantey
pushed a commit
to mrchantey/bevy
that referenced
this issue
Feb 4, 2025
# Objective - Fixes bevyengine#16959 - The `pbr.rs` example in the 3d section panicked because of the changes in bevyengine#16638, that was not supposed to happen ## Solution - For now it's sufficient to introduce a `never_param_warn` call when adding the fallible system into the app ## Testing - Tested on my machine via `cargo r --example pbr`, it built and ran successfully --------- Co-authored-by: Freya Pines <[email protected]> Co-authored-by: François Mockers <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-ECS
Entities, components, systems, and events
C-Bug
An unexpected or incorrect behavior
C-Examples
An addition or correction to our examples
S-Ready-For-Implementation
This issue is ready for an implementation PR. Go for it!
Bevy version
main
branch, commit f9c8f51The issue does not occur with v0.15.0.
What you did
Ran example
3d/pbr.rs
with commandcargo run --example pbr
.What went wrong
A window appeared for a fraction of a second, then the program panicked with:
Additional information
Full output:
The text was updated successfully, but these errors were encountered: