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
Does LinkConditionerConfig belong to SharedConfig?
As I understand SharedConfig is a set of configuration that absolutely needs to be in sync between server and client in order for the network communication to work properly.
Link condition does not belong to this category. Usually this is the other way - server and client have really different network link reliability. It should be possible to configure different link condition in NaiaServer and NaiaClient.
The text was updated successfully, but these errors were encountered:
Hey Tomasz! Hey thanks for looking through naia in such detail, I love getting this feedback!
Yes, eventually I would like the LinkConditionerConfig to be specific to either the Client OR Server, like you say. The reason that it's in the SharedConfig right now is that the LinkConditioner currently buffers their INCOMING messages, but not OUTGOING messages. If both the Client & Server share the same link conditions, then we don't have to worry about buffering outgoing messages, because it'll be buffered once it arrives.
I would definitely like to change this, but opted for this solution as I was getting frustrated and wanted to move on to the clientside prediction stuff 👍 If you can add buffering to outgoing messages in naia-socket, then feel free to change this!
Does
LinkConditionerConfig
belong toSharedConfig
?As I understand
SharedConfig
is a set of configuration that absolutely needs to be in sync between server and client in order for the network communication to work properly.Link condition does not belong to this category. Usually this is the other way - server and client have really different network link reliability. It should be possible to configure different link condition in
NaiaServer
andNaiaClient
.The text was updated successfully, but these errors were encountered: