FAF Server Admin group

Brutus5000

I added both CSS & JS and also retested it after update to 4.3.2.
CSS and JS are active, but I see no button to switch it on (forum.faforever.xyz)

Don't we somehow need to add the input box with class .theme-switch?

Brutus5000

@Kilatamoro said in Open discussion on testing and rollout of the new ice adapter:

Is this supposed to help against DDoS?

Yes and no.
Due to DDoS we can no longer run our own TURN servers, so we have to use 3rd party ones. Our current provider Xirsys seems to work, but people have still connectivity issues and it could be related due to issues in our current ice adapter. We know this, because it doesn't work together with Cloudflare TURN service at all.

With the new solution we can use Cloudflare, which is also cheaper than Xirsys.

So it does not directly impacts DDoS related problem, but it is related to it.

Brutus5000

I can't even get the client to properly run from source under MacOS. And I develop on mac (not for, just on) for a living. Tried to fix it, but too many problems...

Sheikah

@Brutus5000 said in Open discussion on testing and rollout of the new ice adapter:

So you need a new test-client version. That only works with other test clients. You can go back to the normal client (but I don't know if you can install them in parallel or need to uninstall and reinstall each time).

People should be able to have two versions of the client installed at the same time.

The only part that is really shared that might get wonky is the client prefs between them.

Brutus5000

So you need a new test-client version. That only works with other test clients. You can go back to the normal client (but I don't know if you can install them in parallel or need to uninstall and reinstall each time).

You can play on the production server.
But a test-client can only connect to a test client and a normal client can only connect to a normal client. That's why you should only play custom games, in the matchmaker you will be matched with people using the normal client.

If you encounter issues you describe the problem and tell us the game id and we can look at all the logs.

At some point we have to decide to roll it out for everyone. At this point there is no turning back for single users where it doesn't work (in worst case we need to do a global rollback to the old version)

Brutus5000

For quite a while we have been working on a new ice adapter implementation (server side, client side and the adapter itself which is now called faf-pioneer).

It has a few pros and cons compared to the old ice-adapter solution:

Pros

Auto-update in the FAF client. So far we needed to rollout a new client to make a version change. Updates are now possible without a client update, just by releasing a new version on Github.
It no longer requires a lobby server for ICE candidate exchange. We can run updates on the lobby server or the FAF client connection (or the client itself) might crash and it should still be able to reconnect.
It supports Cloudflare TURN services, which should make connections more stable and hopefully less expensive than on our current provider Xirsys.
(Unless you opt out in client settings) You share your connection logs centrally with FAF servers, so we have the accumulated logs of all players of a single game to debug issues.

Cons

No more debug connection window. The builtin UI is vanished and we also have no alternative WebUI so far. A reimplementation would take too much effort right now.
Probably more bandwidth required. We use the WebRTC protocol now, which does a lot of work for us, but it enforces encryption. According to the old ice adapter developer this idea was dismissed in 2017 because it required more bandwith (in worst case doubling it). But now its 2025 and even mobile connections offer more bandwith. And better slow connectivity than no connectivity I guess.

So what is the state?
It is now in a state that games are stable on 1v1 and we need to get more people on board to broaden the test experience.

There is a big problem however for both testing an final release. It's not backwards compatible. We deploy a new FAF client and people on that version can no longer join old client version games or vice versa. So testing only works if all players use the modified client version. And for that time they should probably use password protected games, and TMM should be avoided completely.

So once we go live, there is no turning back really. If it makes problem for some players, they cannot downgrade. They can't play anymore until the issue is fixed.

I know that this is undesirable, but we evaluated options and there basically no way to offer a fallback strategy and/or backwards compatibility.

.

So before I do anything big, I am asking you, the community, for feedback. How much time do we want to spend on testing? Who is willing to test? How much risk do we want to take?

Brutus5000

handshake timed out after 10000ms

There seems to be connection issues due to hardware or software issues. Nothing we can do about it. Since you are posting on the forum https seems to work in general...

Brutus5000

Unable to patch Forged Alliance to the required version due to conflicting version running

Make sure no game is running anymore. If it is already closed try rebooting your pc. windows thinks the file is still in use

Sheikah

Also start a normal game once. There is a bug I think if you try to start a replay first. Since it is looking for the non replay bin folder

Sheikah

Remove the space from FAF Client

FAF Server Admin

Posts

Member List