504 means you were able to talk to api.faforever.com but it wasn’t able to reach the backend service. So the fact that it started working again after you flushed your firewall rules is just a coincidence.

Just noting that in case someone finds this in the future and thinks that if they get a 504 error they can fix it by flushing firewall rules. You can’t. Just wait a bit and try again or notify the server admins.

Ok, I fixed it by creating a new folder in my Downloads instead of transferring Gas Powered Games to downloads. Thank you for taking the time to help me and have a great rest of your week!

@jip Hello. I encountered the same problem, tell me how to fix it

On a second thought, might also be this assert that fails the first tick:

gpAssert( (_controlfp(0, 0) & _MCW_PC) == _PC_24 );

Since setting the _PC_24 flag does not do anything on ARM, when checking the flags, that will be unchanged. First thought - could we disable one of these asserts with a patch? Or somehow pretend the flags are always set as expected on Apple Silicon with _PC_24 set (or redefine _MCW_PC)?

However, two more interesting bits of information I found, comparing Intel and Apple Silicon, which seems to hint at calculations using binary64 (double) match but binary32 (single float / 32 bit (24 bit precision)) don't match:

https://stackoverflow.com/questions/71441137/np-float32-floating-point-differences-between-intel-macbook-and-m1

https://eclecticlight.co/2021/04/22/can-you-trust-floating-point-arithmetic-on-apple-silicon/

If so, that would mean the proper fix would be to replace all single floats in the game with double floats.

@lothar863 Try adding an exception/exclusion for the FAF Client in both the active scan & firewall sections of your AV software & Windows Security. I would also try clearing the cache of each browser you've tried & then try again.

If you still have an issue, then click the Reply button at the bottom between the 👁 (View) icon & the "Mark unread" button. Next, open Run (Windows+R) & go to the following:

%USERPROFILE%/AppData\Roaming\Forged Alliance Forever\logs

Sort by Date Modified. From there, drag/drop your client.log file (the Text Document file without the date) into the Reply message window so those that can help (not me) have that data to look at.

@mostlostnoob You think using a VPN and making my connection in America or somewhere can help mitigate the lag?

It would seem they were related to old mods I had been using, i've since disabled them and all seems to be well this far. Thanks for the help

Thank you for explanation. Could I somehow help you?

@amygdala said in Game bugs out (runs 1 frame per 5 sec) after someone dies and leaves:

@legendofthestars Supreme Score Board got broken some time ago, so be sure to use the fixed version "Supreme score board 2"

I had the old version so maybe that was the problem. Thanks for pointing this out.

@mostlostnoob
The link is dead.

Not Found
The requested URL was not found on this server.

Apache Server at faforever.uveso.de Port 80

I followed the steps you indicate and tried it with 2 more browsers, with the same result.

If you have the mod please share it with me via email.

Thank you.
Captura de pantalla 2024-04-04 145150.png

@mostlostnoob Cheers for the assist, I believe Avast was at work and I hadn't realised. Hopefully I shall be operational for awhile.

Try to change your default browser to something else, without any extensions, and try again. And check your security/firewall.

Once you get used to zooming out then back in those games with the wasd become very hard to play

ah yea thank you very much. your response here: https://forum.faforever.com/topic/7246/unable-to-install-faf-client?_=1710689766922 solves it for me

@zappazapper I'm sure that mod does exactly what you wanted, given that it's Jip who removed the function from the base game 😛

@spacewhales You may not see anything stating that it's blocking FAF specifically, but it may still be doing so. What is recommended is to add an exclusion/exception to the firewall for the FAF Client to allow it through.

As for the router, that could very well be a source of issues if it's not allowing you to get proper DNS records, so you might want to consider looking into resetting the router/gateway.

I know this is a common issue, but I also doubt all the affected people use Pi-Hole or similar products in between their host and DNS Server.

However, this made me think that people with this issue reocurring, also could try changing their DNS Server as a step of troubleshooting. Especially those default DNS Servers from ISP's are not very....reliable.

Just a thought.