@zokora said in It is not a bug that the engineers have a bigger reclaim radius when the fab has an attack move. At least not in FaF. Chris Taylor confirmed it was a bug, not an intentional design. This was covered in a great video interview, it's one of these (not sure which) https://www.youtube.com/c/ForgedAllianceForever/videos

Great, thanks for the replies!

You can learn how to attach the debugger here: https://forum.faforever.com/topic/3262/exception_access_violation-with-logs/2 Please do so - and report back with the full logs. You can upload them to www.pastebin.com to prevent cluttering your post.

We've all benefitted from this from time to time #blush

Sounds good

@zokora I may have picked up the wrong definition, which may cause misunderstanding

Yes - I'd have to go with the XACT errors as well. It's well known that they almost always result in random and frequent crashing.

@femboy he died in a fire of change but promised to return to us.

We're aware of it and we're on it

Can you differentiate between the client and the game? Since when did this start to happen?

@arma473 Thanks for the suggestion. All mods are off, still desyncing @Sheikah Uh oh. I AM getting the same error again. (see pic) Doesn't matter how many times I re-try the replay. Have tried restarting client, logging out and in again, same problem. I seem to have a knack for breaking things! [image: 1642471892270-faf-replay-error.png]

Laptop ratings are completely wrong as well. On my old laptop i always had a cpu score of +-220 but i was always 1 or 2 simspeeds lower than others

Just one addition: client 2021.11.0 does not have this problem. I re-installed the previous client version and the connection problem is gone.

I use Sophos

Ive managed to switch to windowed mode.

Not only is it allowed but that's exactly what the upgrade is for

Yes having that as an option would be great, thanks!

Tested; It will lead to this error: WARNING: Error running HandleEvent script in CScriptObject at 17507140: ...mdata\faforever\repo\fa\lua\ui\game\construction.lua(2145): attempt to call method `GetEntityId' (a nil value) stack traceback: ...mdata\faforever\repo\fa\lua\ui\game\construction.lua(2145): in function `FormatData' ...mdata\faforever\repo\fa\lua\ui\game\construction.lua(1288): in function `OrderEnhancement' ...mdata\faforever\repo\fa\lua\ui\game\construction.lua(1531): in function <...mdata\faforever\repo\fa\lua\ui\game\construction.lua:1530> c:\programdata\faforever\repo\fa\lua\ui\uiutil.lua(873): in function `OnClick' c:\programdata\faforever\repo\fa\lua\ui\uiutil.lua(937): in function <c:\programdata\faforever\repo\fa\lua\ui\uiutil.lua:933> c:\programdata\faforever\repo\fa\lua\ui\uiutil.lua(797): in function <c:\programdata\faforever\repo\fa\lua\ui\uiutil.lua:788> :GetEntityId() is called on the destroyed commander.