You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
The MDReplicatorGroupManager currently has very simple logic for balancing the updates between frames. What could be needed is some more advanced balancing logic and possibly rebalance logic.
Also is it worth it to allow users to set custom group names? It seems like allowing this just makes balancing harder, if we don't have group names any form of balancing we introduce could be much more efficient. I know I was the one who introduced the concept but now after thinking about it I am questioning the value of it.
The text was updated successfully, but these errors were encountered:
There might be value in letting users choose to replicate out all the properties of a given node by giving them a common group. It's definitely something I've wanted before when making games.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
new featureBrand new functionality to the frameworkquestionFurther information is requested
The MDReplicatorGroupManager currently has very simple logic for balancing the updates between frames. What could be needed is some more advanced balancing logic and possibly rebalance logic.
Also is it worth it to allow users to set custom group names? It seems like allowing this just makes balancing harder, if we don't have group names any form of balancing we introduce could be much more efficient. I know I was the one who introduced the concept but now after thinking about it I am questioning the value of it.
The text was updated successfully, but these errors were encountered: