You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 16, 2022. It is now read-only.
When preparing like 33+ messages to be sent to the same handle in the same Bevy frame, NetworkEvent::Error and the plugin itself report the following errors:
ERROR bevy_networking_turbulence: Channel Incoming Error: channel receiver has been dropped
After this occurs the connection appears to be essentially dead.
An attempt of circumventing this issue by combining network message data so they become a single message to be passed to NetworkResource instead also has been in vain.
This makes me believe that this error is not caused by the number of messages, rather by the amount of information passed around in the connection. Once the server passes a certain amount of data to the client this issue consistently occurs.
When preparing like 33+ messages to be sent to the same handle in the same Bevy frame,
NetworkEvent::Error
and the plugin itself report the following errors:ERROR bevy_networking_turbulence: Channel Incoming Error: channel receiver has been dropped
NetworkEvent::Error: TurbulenceChannelError(IncomingTrySendError::Error(ChannelReceiverDropped))
After this occurs the connection appears to be essentially dead.
An attempt of circumventing this issue by combining network message data so they become a single message to be passed to
NetworkResource
instead also has been in vain.This makes me believe that this error is not caused by the number of messages, rather by the amount of information passed around in the connection. Once the server passes a certain amount of data to the client this issue consistently occurs.
What do I do to not run into this?
Reproduction project:
bevy_turbulence_error.zip
The text was updated successfully, but these errors were encountered: