@sheikah yeah seems like it was largely a bad interaction between firewall and AV thanks

thx @magge

Thank's for the advice! I joined the discord and searched a little bit through it. It looks like there is already a solution for the issue and it's even fixed: https://github.com/FAForever/faf-coop-maps/issues/401 But it seems like it is not yet within the formal release. I tested it by fixing the lua script locally as described in the link above and it works for me.

@melanol Queue isn't displaying properly when selected with the control group. It isn't two entities, giving a build order to the control group selected variant still adds to the queue as expected.

@drwho42 you can right-click on the programm exe/link and launch it as admin. that is not recommended to do regularly and should be used just for testing purposes. However there is some very weird stuff going on here and you should probably reset all settings/reinstall the client. C:\Program Files\FAF Client\Documents This path is just not a thing and I have no idea why it would try to access that. %USER_PROFILE%Documents is also wrong as it expands to C:\Users\eholDocuments which is just not a path that exists (it's missing a \ between your username[ehol] and Documents)

@infiltraitor_69 Please go to client > top left menu > Show logs folder > logs > sort by Date Modified. From there, drag/drop the most recent game_21xxxxxx.log file (should be of the game that just froze/crashed) into here so those that can help (not me) have that data to look at.

@milthiad I would suggest that you go to client > top left menu > Show logs folder > logs > sort by Date Modified. After that, go to the XtremeWars forum thread. From there, drag/drop the game_21xxxxxx.log file of the game that you noticed this issue into a post along with the replay# & timestap of when you noticed it.

I reinstall FAF client, and its working

It was determined that there was an issue with the new managed Coturn server. That issue has been fixed & you should be able to play now

Gotcha, thanks for the clarification

This is a Nomads game. If the same does not happen in the standard featured game modes then it is a bug with Nomads. You can report those here

I believe I have found the problem. Looks like the function GetTerrainHeight(posX, posZ) was calling a value it didn't have access to, which must have been causing the infinite loop. Error wasn't getting written to the log in prior playthroughs, so hopefully that is it.

@clyf I’ll try turning off no rush, thanks

Who uses "they" when speaking about a person?

Restarting my pc fixed the issue. Thanks

I haven't gotten the melee functions to work yet, so their nature is occluded from me. The concept seems a little hacky though, have to see how they look if I do ever get them working. I added a SetSpeedThroughGoal adjustment to the Beetle PR, and it improved tailchase performance by another major step (also had no idea about navigators and what they did, some interesting possibilities there). Current issues: Performance against experimentals with large hitboxes is bad, because weapon targeting is generally evaluated to the center of the target. This is an issue with the stock beetle. No improvement for non-attack attacks (guard, patrol). Adding another dummy weapon with a range significantly larger (~`10) than the current AOE (6.5) could help. Right now the main kamikaze weapon doesn't have a target until immediately prior to detonating, so it's no help with fudging our detonate radius. A dummy longer range detector could address that, both with large hitboxes and for letting the unit know if it has a target or is just on patrol.

@zoodoo4u If you think allowing live replay viewing is a bad idea why do you think having the entire map revealed doesn't matter?

No, the UI code of FAForever

@relentless We fell into a defensive playstyle given that harassment just wasn't very viable when outnumbered 5 to 1. We've tried experimenting with AIx now and that seems to be the way to go given how many options it has for tuning. Thanks for the feedback.