Page 1 of 1
Unicast packet client disconnect
Posted: Thu Jan 15, 2015 6:55 pm
by bteitler
Can someone explain to me how to "disconnect" a packet client using Unicast protocol from Motive? From what I can tell, the packet client example sends a single "ping" packet which causes Motive to start sending data, but it is unclear how to de-register a client, as there is no example for this. I'm a bit worried that clients connecting and disconnecting is causing bandwidth to increase unnecessarily.
Re: Unicast packet client disconnect
Posted: Mon Jan 19, 2015 10:44 am
by morgan
Currently there is no message for direct depacketization clients to register a disconnect from server when using Unicast. We've made a note to schedule this for the next NatNet release.
In the interim, is it possible for you to use Multicast, which would prevent the duplication of packets when multiple clients are involved?
Morgan
Re: Unicast packet client disconnect
Posted: Mon Jan 19, 2015 5:27 pm
by bteitler
Thank you for your response. Unfortunately, I cannot use multicast because my use case is wireless, and wireless multicast performance is very poor, and seems unpredictable. After reading a bit on wireless multicast, it seems that this is somewhat expected and not recommended to use multicast for time sensitive and bandwidth intensive applications over a wireless network.
Re: Unicast packet client disconnect
Posted: Thu Jan 22, 2015 5:02 pm
by morgan
OK - We'll work on getting a disconnect for unicast clients into the next release of Motive.
thx!
Morgan