The only reason the official client wouldn't start is if you are running a version of windows 10 before windows 10 build version 1803. There is an incompatibility with that old version of windows 10.
You can update your windows 10 or manually perform the fix detailed here. https://forum.faforever.com/topic/6240/new-client-2023-6-0/13?_=1724237238326
For those coming to help, this is an error in the python client.
I had a 3570k few years back, any microstutters I had were due to SW or HW issues, IMO they shouldn't be that noticeable.
Hence my listed suggestions to test if they can be removed.
Don't think it should be that obvious in frametimes as for the OP?
Things I'd do in this order to find the issue:
You can look up all the different settings in our IRC config: https://github.com/FAForever/gitops-stack/blob/83d63bde50b59bdb9eb06fe63adc1680aeca755c/apps/ergochat/config/ircd.yaml#L953
This is exactly what FAF is doing. Your local replay stream is saved locally, and the "consensus" replay is saved on the FAF server. "Consensus" means that this is the replay that matches the majority of the players still connected.
If you are interested then you should feel free to reach out to me or start by tackling some of the issues to get an introduction to the code base.
From the outside perspective it may sound easy, but I assure you it is not.
This problem does not apply to just the faf mod. It needs to be applied for fafdevelop and fafbeta as well, and for these you surely do not want to get a banner, but it still needs to be covered. Still then we didn't talk about the on-top featured mods like coop or phantom. These may or may not need to be updated depending on the game you want to play.
For the FAF client it's hardly possible to detect the currently applied version, since any given file could belong to multiple patch levels and things get messy with on-top featured mods.
The lobby server doesn't track the played base version and on-top featured mod version. It doesn't even know that versions exist at all.
The patch generation happens outside the lobby server and it would need to be notified about this change. But some deployments of featured mods happen partially manually, so there is not even a way to do that right now.
TL;DR: It is possible, but would require fundamental changes to patch handling in FAF. And all that for the few days a year were we release a patch. So it's not likely it will be tackled.
I am suspecting this map uses custom textures right? The red and black is the image used when the intended texture is missing. So that means that either the texture is missing from the zip file that is on the vault, or this particular user had an error when unzipping the map folder and the texture got corrupted on their system.
