Factorio Forums

Server was updated to 18.10 today. Before this time while our map is decently sized (137MB) 5 players were able to play with relative ease and smoothness. However since the update 2 players (myself and one other) are unable to play due to the latency tick being at 254. The server starts to drop us but never successfully does so as the latency will recover just in time.

My typical network speed is ~100-300mbs and 200mbs was recorded near time of issue.

While the server is not my own, I
1) Know the person who owns the server quite well and can easily get requested information
2) Work as a sr. cloud admin so please bring on the technical details/questions
3) As I work in IT am frequently up late in US-East timezone and am willing to trouble shoot and perform live tests.

Other things of note
- Single player of map runs smooth at ~ 58-60 FPS/UPS
- Latency Spike happens almost immediately and excaserbated by walking, placing items, and getting in trains.
- Latency Spike is reduced by sitting still and listening to factory sounds.

What was the last game version you were on when it worked? There have been a total of zero changes to the network logic between 0.18.0 and 0.18.10.

18.6 was what we started this game on. did not upgrade until 18.10

the_cat_is_maybe wrote: ↑

Fri Mar 06, 2020 4:09 pm

18.6 was what we started this game on. did not upgrade until 18.10

Sorry, then the issue is with your network configuration, hardware, or software on the client or server end. As I said; the multiplayer code has not had a line of it changed in the last several months so it's impossible for the update to have caused any issues purely because of the update.

Is there anything I can do or look at to get more detailed networking logs. So I can self troubleshoot.

or should I just be running wireshark.

I wrote a partial Wireshark protocol dissector for the factorio game protocol and could use that look at what's going on.

I would be very interested in that. As that is what I was about to do. Going to spin up an AWS server to try and replicate issue and so that I can have end to end wireshark logs