SC: FA (Moho) engine sources
-
this is insanely cool
-
Will this allow devs at some point to enable proper multi-core support for the performance benefits?
-
Will this allow devs at some point to enable proper multi-core support for the performance benefits?
I did it already, all possible optimizations so far are in this build and giving up to 43% performance increase compare to retail. There is no magical "multi-core" thing that could be easily enabled if we're talking about replay and simulation parity (equal to current binary without desyncs). More things could be done to improve it thought, but old replays will no longer work on same version of binary, which is fine way to do (since FAF keeps old versions of game to see replays anyway) but it will change game behavior, I won't be making those improvements before we rollout this version to fafdevelop for larger audience.
-
@Draiget Awesome! I was thinking in terms of large maps + lots of players + lots of units and how it tends to slow down player's CPUs, and thusly the game itself as all players can only play at the speed of the slowest CPU. You're saying that's been improve 43% which is a huge deal.
-
Just in case, RE EXE available in latest pre-release client and
fafdevelopfor testing - https://github.com/FAForever/downlords-faf-client/releases/tag/v2026.11.1-alpha-2 -
Does this also mean the core networking component can be upgraded to current protocols and standards?
-
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.
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