Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

More resilience to flaky network connections #3773

Closed
DorpsGek opened this issue Apr 18, 2010 · 5 comments
Closed

More resilience to flaky network connections #3773

DorpsGek opened this issue Apr 18, 2010 · 5 comments
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

timnew opened the ticket and wrote:

Client get disconnected very often.
We play the game in a lan with 2 players. one is Windows Version and another is Mac version. And the 2 computer is connected with a TP-Link Home Wireless Gateway.
And the connection get lost so easily. Especially when the client is trying to modify the terrain or click the "skip" button is transport route-list very quickly.
We tried to host game on both 2 computers, but the problem continues.

I guess it is somehow related to the network environment, our physical network connection is wireless, which is not so stable.
The delay changes in a big range, Here is a ping report:

Ping has started…

PING 192.168.1.2 (192.168.1.2): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.2: icmp_seq=1 ttl=128 time=42.279 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=128 time=30.023 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=128 time=133.277 ms
64 bytes from 192.168.1.2: icmp_seq=4 ttl=128 time=27.119 ms
64 bytes from 192.168.1.2: icmp_seq=5 ttl=128 time=69.326 ms
64 bytes from 192.168.1.2: icmp_seq=6 ttl=128 time=14.047 ms
64 bytes from 192.168.1.2: icmp_seq=7 ttl=128 time=24.622 ms
64 bytes from 192.168.1.2: icmp_seq=8 ttl=128 time=7.830 ms
64 bytes from 192.168.1.2: icmp_seq=9 ttl=128 time=98.473 ms
64 bytes from 192.168.1.2: icmp_seq=10 ttl=128 time=209.538 ms
64 bytes from 192.168.1.2: icmp_seq=11 ttl=128 time=168.155 ms
64 bytes from 192.168.1.2: icmp_seq=12 ttl=128 time=13.068 ms
64 bytes from 192.168.1.2: icmp_seq=13 ttl=128 time=360.470 ms
64 bytes from 192.168.1.2: icmp_seq=14 ttl=128 time=33.255 ms
64 bytes from 192.168.1.2: icmp_seq=15 ttl=128 time=11.035 ms
64 bytes from 192.168.1.2: icmp_seq=16 ttl=128 time=45.017 ms
64 bytes from 192.168.1.2: icmp_seq=17 ttl=128 time=15.289 ms
64 bytes from 192.168.1.2: icmp_seq=18 ttl=128 time=3.158 ms
64 bytes from 192.168.1.2: icmp_seq=19 ttl=128 time=50.118 ms
64 bytes from 192.168.1.2: icmp_seq=20 ttl=128 time=22.520 ms
64 bytes from 192.168.1.2: icmp_seq=21 ttl=128 time=509.666 ms
Request timeout for icmp_seq 22
64 bytes from 192.168.1.2: icmp_seq=23 ttl=128 time=103.626 ms
64 bytes from 192.168.1.2: icmp_seq=24 ttl=128 time=146.773 ms
64 bytes from 192.168.1.2: icmp_seq=25 ttl=128 time=53.668 ms
64 bytes from 192.168.1.2: icmp_seq=26 ttl=128 time=23.935 ms

Reported version: 1.0.0
Operating system: All

This issue was imported from FlySpray: https://bugs.openttd.org/task/3773
@DorpsGek
Copy link
Member Author

Rubidium wrote:

I'm not sure whether we can really fix this issue.

On one side we have OpenTTD that just kicks everyone that is more than 4 game days behind (almost 9 seconds), on the other side we have the operating system (TCP stack) that does the resending of lost packets for us and I think that those packets are not resent fast enough or resending of them failed multiple times. Sadly enough the latter isn't something we can do anything about and the former is gameplay wise already really annoying for clients; having to wait up to 9 seconds before something gets built is a really long time, a few hundred milliseconds starts to makes it already irritating.

Having said that, I've played some multiplayer a few days ago and my ssh connections and a few downloads got aborted but OpenTTD's connection remained open. I've got no idea what caused that, but it is kinda the exact opposite of the behaviour you're describing.

That might have to do with me being on Linux playing on a server running Linux and Linux having better settings for retrying/resending than Windows or Mac OS X, but that's all speculation.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3773#comment7894

@DorpsGek
Copy link
Member Author

timnew wrote:

I'm not sure whether is the problem caused by the version that we're playing.
Since there is no official Mac build on the open ttd website, this version is compiled by someone it self, and I downloaded from his ftp server.
I'm not so sure what version the source is! At least I found that this Mac version OpenTTD doesn't support PNG, it is really weird.
So I wonder can you provide an official build of game for Mac users, that's will be a great help for us~ :)

This comment was imported from FlySpray: https://bugs.openttd.org/task/3773#comment7905

@DorpsGek
Copy link
Member Author

Rubidium wrote:

Technically we likely can (we haven't tested whether the compile farm can still compile OS X lately), but providing such a binary would imply "official build" which implies we support it and that is exactly what we do not do.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3773#comment7908

@DorpsGek
Copy link
Member Author

timnew wrote:

That's a bad news for us Mac users :(
I think maybe we doesn't need some really strong support, as you can see, the game can be compiled and run on Mac well, so we just need someone to compile the game, and pack it into a mac Bundle.
So we can download it directly instead of compile it, which need us to download and deploy some libs or some other dependencies.

To provide a Mac compile for big update, I guess, which won't cost the team too much time, but will help the a great number of guys using Mac a lot! :)

Any way, no matter, what result it is, we're really appreciating your great work!
TTD is the most wonderful transport simulation game that I ever known, which accompany me for my growth. I met the game in 1998 when I was 13. Still today, I'm also fond of it!
The original TTD is a great game, but it is not perfect. There are still many defects in it. It's your guys' great work, making it better and better.
Guys, thank you every much!
If possible, I wish I could be one of you in the future not far away.

PS: I'm a TTD fan from China.

This comment was imported from FlySpray: https://bugs.openttd.org/task/3773#comment7913

@DorpsGek
Copy link
Member Author

DorpsGek commented Aug 5, 2017

andythenorth closed the ticket.

Reason for closing: Won't fix

Don't try to boil the ocean (networking issues are so beyond what OpenTTD can control). ;)

This comment was imported from FlySpray: https://bugs.openttd.org/task/3773

@DorpsGek DorpsGek closed this as completed Aug 5, 2017
@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DorpsGek