SC: FA (Moho) engine sources
-
Does this also mean the core networking component can be upgraded to current protocols and standards?
What do you mean? It's using standard protocols, I did improved it slightly but we won't replace anything until it's tested in fafdevelop and accepted as primary game EXE.
-
I figured that the networking code is 20 years old - there must be newer/improved methods for fixing the common lag issues the faf P2P experience has (interruptions, disconnects, etc).
-
FAF develop has some connectivity improvements by adjusting network parameters to make use of more capable modern networking: https://github.com/FAForever/fa/pull/7364 That's the most immediate change I know we can test right now. I don't know what's the state of the other WebRTC-based netcode or ice adapter changes.
-
@hobosapien It will lag the same as now. Because the problem is not in the old protocols, but in FAF's weak infrastructure. Right now we have only one server in Europe for communication between players. I assume that DDoS directly affects the ability to launch new servers.
-
Well only partially true if the P2P connections are routed via relay/proxy. But I guess most are still P2P connections.
-
There are multiple ways, from spinning relay proxies regionally\geographical, to hosting regional client-server lobby-servers and having coordinated master server that show available games in client, any ddos in that case doesn't make sense - only for region. That's like ideal world with volunteers to host those things as they're pretty expensive to host for 100+ lobbies same time. So having just small regional relays might be smaller and achievable part of this idea.
Using native ICE in engine much better than any WebRTC according to my tests in multiple different games(player count)\servers. -
@draiget @giebmasse I often create lobbies. I would like to have the ability to assess connection stability at the lobby stage. To do test data runs to understand the packet loss percentage and stability. Send the received information about the connection with each player to the host.
Display the information in the lobby in a pop-up table.
In addition to the table, I would like an informative dashboard in the browser with detailed information, graphs, etc. (a lightweight web server will run on a local port and the dashboard will be available, for example, at http://localhost:7777 in the browser).The point is to start transmitting test data between players already in the lobby in order to identify connection problems before launch.
-
played a game, crashed after 15 minutes i reckon. Chat didnt work and sounds where weird
added crash report
crash.txt -
@Firv If you have the sound bug (due to 7.1 surround: "unknown speaker configuration" + "xact3dapply failed") the sounds on the new engine will be weird with now-functioning distance attenuation (quieter) and LFE/subwoofer channel (more bass for explosions/impacts). Is that your case?
-
Also the crash report file link is empty for some reason.
-
@Firv If you have the sound bug (due to 7.1 surround: "unknown speaker configuration" + "xact3dapply failed") the sounds on the new engine will be weird with now-functioning distance attenuation (quieter) and LFE/subwoofer channel (more bass for explosions/impacts). Is that your case?
Yes i had that too. You barely heard anything when zoomed out.
Normally you can hear a gunship or whatever attacking when zoomed out and try to find it. In that game you just didnt hear it at all
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login