flutter3d_net_webrtc 0.8.0
flutter3d_net_webrtc: ^0.8.0 copied to clipboard
A NetTransport over a real WebRTC data channel — net-01's rollback engine, P2P, with net-02's relay carrying only the SDP/ICE handshake.
0.8.0 #
Moves with the stack to 0.8.0, whose flutter3d_hardware changes
PassEncoder.bindTexture to return bool and makes every backend forget its
bindings at bindPipeline. Nothing in this package changed.
Its flutter3d_* dependencies ask for ^0.8.0.
0.7.1 #
Released with the rest of the stack at 0.7.1. Nothing in this package changed. The release it resolves against builds from pub.dev again and no longer crashes Metal on the first unlit draw.
Its flutter3d_* dependencies ask for ^0.7.1.
0.7.0 #
- The first publication, and no code since 0.6.0 was written. That number
was carried inside the workspace and never reached pub.dev. 0.7.0 is the one
number the whole shelf goes out on, so
^0.7.0here resolves against^0.7.0on any otherflutter3d_*package;doc/boundary-0.7.0.mdhas the list. What changed is the floor onflutter3d_net, now^0.7.0, and the formatter's line breaks inwebrtc_transport.dart. - Worth knowing before depending on it, since the entry below does not say:
this is the one package of the two that needs Flutter, through
flutter_webrtc^1.6.2, andflutter3d_netstays plain Dart because of that split. The connection is configured with one public STUN server and no TURN, so a NAT that neither side's candidates get through isWebSocketTransport's case.readycompletes when the data channel opens, and the channel is unordered.
0.6.0 #
net-02's primary transport.WebRtcTransport.createOffer/awaitOfferset up a realRTCPeerConnectionand a data channel over it, exchanging SDP/ICE through whateverNetTransportcarries signalling (net-02's relay) — game frames afterwards go peer to peer, never through the relay.