RealtimeTransform bandwidth question
does a RealtimeTransform continuously send values for position rotation etc on a transform that is not moving?
3 Replies
Hi @Anthony. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
The RealtimeTransform component in NormalVR does not continuously send values for position, rotation, etc., for a transform that is not moving. Instead, it synchronizes at a rate of 20Hz and sends the latest state. If you change something and then change it back immediately, nothing will be sent to the server. This is because Normcore, the networking solution used by NormalVR, doesn't send changes to the server immediately when you change ownership or the value on a model.
For example, if you call
RequestOwnership(), set the position of a transform, and then immediately call ClearOwnership(), nothing will happen. As long as the RealtimeView’s owner is None, then any other client in the future can just call RequestOwnership() to take over the transform and move it.
This approach helps to optimize bandwidth usage, as it avoids unnecessary data transmission for static or non-moving objects.
For more details, you can refer to the Common Questions (https://normcore.io/documentation/realtime/common-questions#im-calling-requestownership-setting-the-position-of-a-transform-and-then-immediately-calling-clearownershipbut-nothing-happens-how-can-i-fix-this) section in the Normcore documentation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------<@333783301263196161> kapa.ai is still learning and improving, please let us know how it did by reacting below
No, normcore all around uses delta compression which won't send any new data if the value was the same as the last