We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Commands
ParamSet
0.7
Windows 10
Wrapped a Commands object in a ParamSet and accessed it with .p0(). Any commands queued this way get ignored.
.p0()
Commands should be queued and then flushed at the end of the stage, just like when using Commands without a ParamSet.
The commands got ignored and were never run.
Minimum reproducible example: https://github.com/JoJoJet/param_set_example/blob/main/src/main.rs
The text was updated successfully, but these errors were encountered:
ec805e9
I'm continually impressed by how quickly this community responds to issues. Thanks @DJMcNab !
Sorry, something went wrong.
Apply buffers in ParamSet (bevyengine#4677)
9078fc3
# Objective - Fix bevyengine#4676 ## Solution - Fixes bevyengine#4676 - I have no reason to think this isn't sound, but `ParamSet` is a bit spooky
a7292c8
dcffedc
Successfully merging a pull request may close this issue.
Bevy version
0.7
Operating system & version
Windows 10
What you did
Wrapped a
Commands
object in aParamSet
and accessed it with.p0()
. Any commands queued this way get ignored.What you expected to happen
Commands should be queued and then flushed at the end of the stage, just like when using
Commands
without aParamSet
.What actually happened
The commands got ignored and were never run.
Additional information
Minimum reproducible example: https://github.com/JoJoJet/param_set_example/blob/main/src/main.rs
The text was updated successfully, but these errors were encountered: