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
I have noticed that sometimes when the connection is lost, it becomes more difficult to connect to FAF, especially when this happens during the game.
Describe the solution you'd like
I suggest reducing the timeout between connect. From 30 seconds to 5 seconds for the time when you are in the game.
Describe alternatives you've considered
I've done some tests.
Creating a game.
We are waiting for 1 player.
Let's start the game.
In windows, go to the "Network connections" tab.
Disconnect the Ethernet network adapter for 5-10 seconds.
We are waiting for automatic auto-connection to FAF.
Test1. Timeout 30 seconds. TEST-1.log
More than 5 connection attempts.
18:19 -> 20:09 = waiting for more than 2 minutes and 9 seconds. That is, an automatic kick in game. It doesn't make sense to wait any longer.
Test2. Timeout 5 seconds. TEST-2.log
More than 5 connection attempts. On the 6th attempt, the connection is successful.
27:58 -> 28:43 = The connection takes less than a minute and a successful return to the game.
Conclusions:
Perhaps more tests with more test subjects are needed. The connection loss was almost the same. In only one case, we were able to restore the connection in a reasonable time (less than 1.5 minutes).
And in the second case, we waited for more than 2 minutes and could not connect.
The text was updated successfully, but these errors were encountered:
The client costs 60 attempts to connect.
In normal mode: 30*60 = 1800 seconds = 30 minutes
Let's be realistic in an online game, no one will wait for me for 30 minutes.
Considering that the game is waiting for an average of 1.5 minutes and during this time I will at best have time to make 3 reconnects.
The change I propose only affects the "game mode".
Is your feature request related to a problem?
I have noticed that sometimes when the connection is lost, it becomes more difficult to connect to FAF, especially when this happens during the game.
Describe the solution you'd like
I suggest reducing the timeout between connect. From 30 seconds to 5 seconds for the time when you are in the game.
Describe alternatives you've considered
I've done some tests.
Test1. Timeout 30 seconds.
TEST-1.log
More than 5 connection attempts.
18:19 -> 20:09 = waiting for more than 2 minutes and 9 seconds. That is, an automatic kick in game. It doesn't make sense to wait any longer.
Test2. Timeout 5 seconds.
TEST-2.log
More than 5 connection attempts. On the 6th attempt, the connection is successful.
27:58 -> 28:43 = The connection takes less than a minute and a successful return to the game.
Conclusions:
Perhaps more tests with more test subjects are needed. The connection loss was almost the same. In only one case, we were able to restore the connection in a reasonable time (less than 1.5 minutes).
And in the second case, we waited for more than 2 minutes and could not connect.
The text was updated successfully, but these errors were encountered: