Frame synchronization It is in the customer service side running a server, each server based on the same frame rate, synchronization in the same frame input, to achieve consistency.
State synchronization server operation to send the change of State to the customer service side
The first thing to say is that frame synchronization does not mean that you cannot join state synchronization, the state service cannot have frame synchronization similar things, so their advantages are based only on
Frame synchronization server and customer service side in a piece, only send input
State Synchronization Service operation, state of the hair
Internet:
The network burden of frame synchronization must be smaller
But the problem of delay is all there is, the solution point is not the same. Frame synchronization to solve the synchronization problem is good, state solutions and ideas more, such as customer service side pre-award, part of the operation of customer service also do once. In general, frame synchronization to solve the network delay is more difficult, of course, the solution is good, reusability is better. State synchronization is relatively easy, just a little bit, but more ways to solve the difference is also OK.
Performance: State synchronization is not necessarily all service operations, frame synchronization is not to be all put on the customer service side, all this basically Dora
Experience: Frame synchronization server and customer service in a piece, all the input pre-judgment must be accurate, but a lot of accurate, that look at the network situation, this thing can only be better, how much hard to say. Specifically, the more units, frame synchronization is easier to do better. Some people say that fighting game frame synchronization must be better, I disagree. In the case of small data volume, the same as the network situation, the status of the hair must represent a difference between? What's the difference? Network latency? First of all we need to know that state synchronization is not a lobbyist's service can not do a certain state of the subsequent operations, such as moving, animation, or do pre-judgment processing. All, state synchronization, in the small order of magnitude, synchronization effect there is no reason than frame synchronization poor.
Development difficulty: Frame synchronization is really suitable for large companies, many people, but also the team of cattle, frame synchronization is actually difficult to give the synchronization, that is, the problem is lost to a single person. State synchronization, less difficult, but it is very difficult to do well.
Individuals feel that frame synchronization is only suitable for special situations, such as orders of magnitude and technical ability of the team
State synchronization fits very wide
Choose which only depends on your team situation, frame synchronization, state synchronization are required to have experienced people can do better,
More technical Team frame synchronization, game understanding better team State synchronization
In addition, it is not said that the state of synchronization can not put a server in the customer service, in fact, this is also possible, the server with state synchronization can, if the offline stand-alone can be made, single-machine when the server in the customer service, many people at the end of the services.
It is not that frame synchronization can not use state synchronization to do some processing, even some use the state synchronization some with frame synchronization
Technology stems from a solution to a problem rather than a category
State synchronization and frame synchronization are not the opposite of the gap can be fused
Frame synchronization and State synchronization