Closed AgustinRamiroDiaz closed 4 months ago
I've been digging into this issue, and it goes away if the example is built with the bevy multi-threaded
feature.
When digging, I also found the following:
WebRtcSocket::try_update_peers
returned Err(ChannelError::Closed)
even though the channel was neither dropped, nor closed. So it looks like a bug in futures_channel::mpsc::UnboundedReceiver
, that it's not behaving as documented, though that seems somewhat unlikely. I'm not sure what to think.
In any case, the workaround is to add multi-threaded
to the bevy features. Perhaps we should add it as a requirement for bevy_matchbox as well...
What
The example under
examples/bevy_ggrs
is broken.How to reproduce
Additional context
v0.6.1
v0.7.0
doesn't panic, yet it's not working. It only shows the floor with a bright magenta