Oh, that makes sense then - the CPU has only 4 cores and then this feature is disabled. The feature disables the first core because the first core is also used by a lot of other processes. This may cause stutters. But it is only enabled when the CPU has at a minimum of 6 or more cores. The reason for that is simple: if you have 4 and you drop one then 3 may not be sufficient to run the game smoothly at all.

In your case, the warning is meaningless in my opinion 🙂 .

Ah! I didn't realize that. Thanks for the response!
In the same replay, the Notha's attacked ground units, completely on their own, without any orders, so I was expecting the same here. They weren't on a Patrol order at that time, so obviously Patrol works differently. They act as Fighters-only when on Patrol.

@thehonorablegeff Try to change your default browser and/or clear browser cache

Yes - those filled with SND/XACT error messages - caused by surround sound.

@dorset said in Setons Opti Ballancing:

Wouldn't it be better for the lowest rank players to battle it out on air and have a slower building air game while the higher ranked players held the front line arc created by the other three positions?

It seems like that, but in actual fact- recovering a broken front is MUCH easier than a broken air.

@geedie Try adding an exception/exclusion for the FAF Client in the AV software & Windows Security.

If that doesn't work, then please open RUN (Windows+R) & go to the following:

%USERPROFILE%/AppData\Roaming\Forged Alliance Forever\logs

You should see a client.log file (the one without the date). Please click the Reply button at the bottom between the 👁 (View) icon & the "Mark unread" button. Next, drag/drop that client.log file (the file without the date) into the Reply message window so those that can help (not me) have that data to look at.

Leaderboards have been bugged for some time and are a separate issue.

While I’ve pulled together some fixes for bugs that can stop this mission progressing I’d have thought it unlikely the fixed bugs would have caused the op’s issues (as they generally related to cases where the player completed an objective much faster than expected), and the fixes I’ve proposed also require someone to review/approve them so I don’t know if/when they’ll be incorporated.

Thanks! I just uninstalled citrix and now I can play again. It seems weird it kept me from playing even if it wasn't open but simply installed on my pc.

@majiko Simple fix steps are:

Windows key > type: Control Panel > Open > Sound > Playback > select the Device you use: Configure > Stereo > finish configuration, Properties: Enhancements > Disable all enhancements, Advanced > 16 bit, 44100 Hz, Spatial Sound > Off, Restart or Shift+Shutdown (not just Shutdown) of PC

If your headphones come with any applet/program, then you may want to disable that & try using the headphones without it. Similarly, if they use a USB or Bluetooth dongle to connect to the PC, see if you can connect directly without the dongle.

See this thread for further troubleshooting: https://forum.faforever.com/topic/4084/solutions-for-snd-error-xact-invalid-arg-xact3dapply-failed

Here is ACU moving in circles: https://replay.faforever.com/22003007
I think it happens when you order it to attack a unit that is close but not in its radius of attack

That's neat, I'll see what I can find 😃

@arma473 A little longer into the replay I did that and once it was in range of the power generators the attack order worked, but when I moved it back out of range to a different spot and gave the order it still walked in circles. But first it retreated out of range of the enemy commander, so I think it has something to do with that. Both times it walked in circles was on the edge of the range of the enemy commander.

@hitagi Disable all your mods (both in the client > Mods tab > Manage Active Mods & also in the in-game lobby > Mods). Then play a game without those mods enabled. If you get another crash, then we'll know that there's a problem with the base FAF game.

If the issue isn't replicated when playing with all mods off, then that means you have a mod that's causing the issue & you need to troubleshoot to determine which one it is. The best method is to enable only 1 or 2 mods & play a game to test if you have another crash. If not, then enable another 1 or 2 mods & play another test game. Continue this until you replicate the crash.

Once you've determined which mod is the culprit, then you'll need to go to the Modding & Tools area of the FAF Forums & find the thread for the mod you're having an issue with. Make a post in that thread reporting the issue along with your most recent game_21xxxxxx.log so the creator/maintainer of the mod can look into it.

@magge that helps quite a lot actually, thank you!

For anyone seeing in this in the future -

PLAY a custom game FIRST. It can just be a 1v1 versus an AI. The client does not create all necessary files and directories until you play your first game.

Replays should then work.

"Talistan's Handicap Mod" does it! Have fun

@brucelee This shouldn't have anything to due with the lag/stutter issue you're experiencing, but you have a sound bug which you can tell by the SND/XACT warnings. This sound issue can result in unexpected behavior, including crashes. Simple fix steps are:

Windows key > type: Control Panel > Open > Sound > Playback > select the Device you use: Configure > Stereo > finish configuration, Properties: Enhancements > Disable all enhancements, Advanced > 16 bit, 44100 Hz, Spatial Sound > Off, Restart or Shift+Shutdown (not just Shutdown) of PC

If your headphones come with any applet/program, then you may want to disable that & try using the headphones without it. Similarly, if they use a USB or Bluetooth dongle to connect to the PC, see if you can connect directly without the dongle.

See this thread for further troubleshooting: https://forum.faforever.com/topic/4084/solutions-for-snd-error-xact-invalid-arg-xact3dapply-failed