Dear commanders,
over the years, memory usage of the FAF client was regular subject of complaints. We worked hard to figure memory leaks and reduce memory usage. Our maintainer assumes, that memory issues >1GB are a thing of the past. But I am not convinced yet. Thus, we need more data and feedback.
Therefore I challenge you: Send me your worst RAM usages images from your task managers. Minimum requirement is it's from version >= 2026.4.0
Thank you!
I also to be clear it isn't that the mod client doesn't know about the options it is that the server doesn't in w how to create map names given a set of options that the client can use to generate a map.
To support this effectively the entire client server communication with regards to generated maps in the matchmaker has to change.
Also it's not that "I need it", I don't have access to the mod client. But I know a couple of folks, who usually come with the pools, have complained about the lack of options in the past.
I was under the assumption you have access. Then just forward my message to the people complaining please.
It may work for some versions of the generator but there is no guarantee it continues to do so in future versions.
It'd be great if you had a separate sub-site, where you can give it a seed (if you like the map), but let it iterate through different settings for mex and reclaim.
Just so you know changing any setting can lead to an entirely different map. There is no guarantee that changing the number of mexes gives you the same map with a different number of mexes.
Raise a feature request in the github repo then and explain what you need. Nothing will be done if a feature request only exists in someone's head...
Yes I understand so he can use the steam account to reset the password on the old account if he forgot it.Otherwise he should log into the old account and change the email
He can recover his old account using his steam link by resetting the password on the account.
We use websockets to communicate from the client to the server. So if the proxy doesn't support long lived websocket connections then that could be the issue
