That uses more bandwidth, not less. Subchannels are there for a reason.Quote:
Originally Posted by DS_Strider
Printable View
That uses more bandwidth, not less. Subchannels are there for a reason.Quote:
Originally Posted by DS_Strider
I think the reason behind that Jamie is so the x and y position data arrive at the clients at the same time. Especially if you are blasting the data. You wouldn't want to receive the x position of a peer, and then receive the y position a little later, right?
No, which is why the binary stack features are provided.
[To send]
Push short X("You")
Push short Y("You")
Send stack to channel on subchannel 0
[To receive]
* On stack channel message on subchannel 0
+ ID("Them") = Peer_ID("Lacewing")
- Set X position of Them to Stack_Short("Lacewing", 0)
- Set Y position of Them to Stack_Short("Lacewing", 2)
Check "Automatically clear stack" if it's not checked in the object properties.
Make sure when comparing to the alterable value ID you use "Compare to alterable value" and not "Compare two general values".
The expression names may be slightly different, because I'm not at home and can't access MMF2.
Nah, you have it right. Ok then that must be a new feature. Thanks, I'll update my example later.
It's not a new feature - it's been implemented since the first public alpha of OINC :)
Right, as was talking in respect to moo. Moo is what I was using before I switched to this, so naturally I did things the same. ;)