Ability to configure NetworkTransforms to send as often as possible. #343
Closed
AlphaLul
started this conversation in
Feature Request
Replies: 3 comments 3 replies
-
Wouldn't an increased tick rate help in that case? |
Beta Was this translation helpful? Give feedback.
1 reply
-
This is not something I would include. You can disable synchronizing a
property or even axes of that property and do it manually if you like.
…On Wed, Apr 26, 2023, 1:37 PM Max Kratt ***@***.***> wrote:
Wouldn't an increased tick rate help in that case?
—
Reply to this email directly, view it on GitHub
<#343 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGPJC3URXAGDK2MHSQG4MSLXDFMOZANCNFSM6AAAAAAXLPJGTE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
2 replies
-
PS: marking as declined because the current behavior is not going to change. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I think it would be nice to be able to configure certain NetworkTransforms to send data as often as possible, similar to how Mirror's NetworkTransform works. This is useful because things such as aiming in top-down shooters often only look good if the rotation logic is in Update. However, since NetworkTransforms send at a fixed rate that is often lower than the Update rate, it can look delayed on observing clients.
It would be nice to have a client-authoritative NT that can just send values to the server right when they update. This obviously wouldn't be the recommended way to use the NetworkTransform since it takes up more bandwidth, but it would be a useful feature to have in cases where there aren't very many good alternatives.
Beta Was this translation helpful? Give feedback.
All reactions