-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Update bevy to 0.11 #93
Conversation
bevy_renet/src/transport.rs
Outdated
app.add_systems(PostUpdate, Self::send_packets.in_set(TransportSet::Server)); | ||
app.add_systems(PostUpdate, Self::disconnect_on_exit.in_set(TransportSet::Server)); |
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.
Maybe group these systems in one call?
Similar for other places.
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.
Done!
bevy_renet/src/transport.rs
Outdated
app.add_systems(PostUpdate, Self::send_packets.in_set(TransportSet::Client)); | ||
app.add_systems(PostUpdate, Self::disconnect_on_exit.in_set(TransportSet::Client)); |
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.
Could you combine these two systems too?
There might be a regression. As the server I am unable to obtain the IP addresses of incoming connections. |
@@ -24,9 +24,9 @@ impl Plugin for RenetServerPlugin { | |||
fn build(&self, app: &mut App) { | |||
app.init_resource::<Events<ServerEvent>>(); | |||
|
|||
app.configure_set(RenetSet::Server.run_if(resource_exists::<RenetServer>())); | |||
app.configure_set(Update, RenetSet::Server.run_if(resource_exists::<RenetServer>())); |
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.
You configure set for Update, but use it in PreUpdate
. I think that's the issue.
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.
Do we need to configure this with all default sets?
Like:
app.configure_set(PreUpdate, RenetSet::Server.run_if(resource_exists::<RenetServer>()));
app.configure_set(Update, RenetSet::Server.run_if(resource_exists::<RenetServer>()));
app.configure_set(PostUpdate, RenetSet::Server.run_if(resource_exists::<RenetServer>()));
This set is used to simplify the run_if(resource_exists::<RenetServer>()
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.
I guess we hit this issue:
bevyengine/bevy#9139
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.
It seems we shouldn't be using SystemSets, and should just use directly run_if(resource_exists::<RenetServer>
/ run_if(resource_exists::<RenetClient>
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.
I will go and remove the SystemSets.
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.
I probably should remove the set enum too then.
This is actually not exposed in the |
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.
Thanks! 🙏
Will work on porting the examples, prob tomorrow/weekend will release the new version 👍
|
Just updates bevy to 0.11, and changes some stuff to fix errors. Let me know if I should make any changes!