We're looking for feedback specially from people playing over 4G/5G, with double or triple NAT ie. chained routers/wifi repeaters, CGNAT (low tier ISPs), "WiMax" (just long distance WiFi links) and basically anything that's not an actual proper internet connection to their home and PC.

v2023.11.0 forces usage of the Xirsys network and we've seen an absurdly low % of TURN connections, meaning that for 99.9% of the playerbase v2023.11.0 is entirely peer to peer.

(note: we've tested it and it should work for the environments described, if you experienced problems before and were unable to play please try the new client!)

Current plan is that will be offering more options in the short future so people can try to "manually vpn" to a few servers that we will keep for this purpose, just like before.

We know of the problem, we're working on it

@comradestryker Thanks for your insightful answer. Cool to see someone attempting to play on Starlink.

More notes: we're only interested on feedback with version 2023.11, problems before it existed are ddos-related mostly and there's nothing there to learn.

2023.11 (for now) goes back to our 2020ish "only Germany" for turn, despite being called "Global". This is due to the release being rushed.
We're working on a more finalized solution that covers everyone's usecases, we wanted to ship this ASAP to finally end the DDoS thing even if it meant some downgrades.

If you were playing in the US exclusively against US players this is pretty bad and explains the ping increase.

While before the connections may have been "7/10" most of the day but a "0/10" for 4 hours a day while the DDoS happened, we preferred to go back to a stable 5/10 as soon as possible.

You can use my script. Can be fed to the client no problem and used to run faf games.
https://gist.github.com/p4block/8d947f85fa707b433af359a699b367fb

This will be integrated into the client in the future (tm)
You'll need to set your game location on it etc

@comradestryker Thanks for your insightful answer. Cool to see someone attempting to play on Starlink.

More notes: we're only interested on feedback with version 2023.11, problems before it existed are ddos-related mostly and there's nothing there to learn.

2023.11 (for now) goes back to our 2020ish "only Germany" for turn, despite being called "Global". This is due to the release being rushed.
We're working on a more finalized solution that covers everyone's usecases, we wanted to ship this ASAP to finally end the DDoS thing even if it meant some downgrades.

If you were playing in the US exclusively against US players this is pretty bad and explains the ping increase.

While before the connections may have been "7/10" most of the day but a "0/10" for 4 hours a day while the DDoS happened, we preferred to go back to a stable 5/10 as soon as possible.

We're looking for feedback specially from people playing over 4G/5G, with double or triple NAT ie. chained routers/wifi repeaters, CGNAT (low tier ISPs), "WiMax" (just long distance WiFi links) and basically anything that's not an actual proper internet connection to their home and PC.

v2023.11.0 forces usage of the Xirsys network and we've seen an absurdly low % of TURN connections, meaning that for 99.9% of the playerbase v2023.11.0 is entirely peer to peer.

(note: we've tested it and it should work for the environments described, if you experienced problems before and were unable to play please try the new client!)

Current plan is that will be offering more options in the short future so people can try to "manually vpn" to a few servers that we will keep for this purpose, just like before.

We know of the problem, we're working on it

In addition to FPU shenanigans, lightly quoting Marcan, the cores in the M1 speculate execution extremely hard, and that is making pre-existing unknown bugs surface. It's possible FA itself is broken in a way that never shows up in Intel/AMD cpus, and if that were the case it's probably pretty much unfixable.

It would also mean that the game would likely stop working at some future point when x86 cpus get more complex and trigger the bug. (you can talk about retro compatibility being x86's only reason to exist though and argue that last point may never happen)

You can use my script. Can be fed to the client no problem and used to run faf games.
https://gist.github.com/p4block/8d947f85fa707b433af359a699b367fb

This will be integrated into the client in the future (tm)
You'll need to set your game location on it etc

In the ideal scenario, your game packets aren't relayed through our servers, but you do need an external public facing server in order to establish a connection between two players behind your typical home router.

The issue comes with people with dysfunctional ISPs and/or ISP router which don't allow for this (UDP Hole punching) to happen, then we need to actually proxy the entire game from every user to every user in a centralized manner. This is surprisingly common nowadays, sadly.

Having more servers to bounce the game helps, such as the australian TURN server. We are working to get more alternative turn servers running. Yesterday we were testing one for a while and got good info. We will post an update soon.

The countermeasures to stop recent DDoS attacks on the server don't allow for other turn servers other than the one in germany to function. We are working on a solution and will post soon.