The server saves the map at a specific tick, let’s say tick 100 and sends the saved map to you.Instead, the process of joining a multiplayer session looks something like this: It means that you are catching up to the new actions in the game, because you have an older copy and the server can’t instantaneously send you a completely new copy of the save for you to run from. “Catching up” is a process very specific to Factorio. Generally speaking, anything should be fine, but mileage may vary. The speed of your download does however affect for how many ticks you will be catching up (the part of loading the map after you download it). It doesn’t really matter how fast a save downloads though, since it is just a file transfer in the end. Generally, savefiles are within 50MB (if you don’t run with seriously modded games), so on an average connection, a save would be downloaded within 15 seconds. The speed of the map downloading depends on your download speed and the server’s upload speed you can’t download something faster than it is being uploaded. NAT punching is the process of your client asking an external server ( Pingpong server, which is a server hosted by Factorio that serves just this purpose) to tell the Factorio game server to establish a connection with your client, because some routers and firewalls may block “random” connections from IPs that you have not requested anything from, which is good for preventing someone from brute-forcing your computer, but is also an obstacle for the Factorio developers.įor Factorio, your download and upload speeds don’t need to be very high, as the map (savefile) is sent over to you when you connect to a server. UDP is also very important because it allows NAT punching to work. Hornwitser however has had a go at analyzing the traffic with his dissector, which even helped fix a bug that was in the game since 0.17! This means that they still have the speed that they want, but they can also have the reliability of TCP - or close to it, as the Factorio protocol is not publicly available for people to analyze. cube said that Wube have solved this with implementing parts of the TCP protocol into their version of UDP. The fact that UDP removes the guarantee of delivering data however directly contradicts how Factorio must work using fully-deterministic, lockstep algorithms as I explained in an earlier post, as the data must arrive or you would recieve a desync. This however also removes the ability to guarantee the delivery of data, ordering the data properly or removing data duplicates (which can sometimes happen). UDP achieves this speed by not having a “handshake”, which is two clients (computers) agreeing that they want to communicate together and establishing a connection, which simply means it doesn’t care about what happens with the data, it just sends it. UDP has the advantage of being much faster than conventional TCP (which is used for most day-to-day things). One of the most significant things they have done is using UDP but adding back things that are in TCP. cube has explained this process nicely in FFF#136. To explain how Factorio’s networking works, however, is a longer process.
There are a few utilities that can however help mitigate these sorts of issues. It can be due to many things, such as maintenance from your ISP or a power outage of your DNS’s datacenters. Sometimes, your network may not be the best. Well, what does that actually mean? What can you do about it in the short and long term? Network Speed Issues If you don’t have a state-of-the-art computer, you probably have seen a message like this saying that you were dropped from the game because your network or computer was not fast enough.
0 kommentar(er)
