Как получить аватарку ноябрьский турнир на сетоне?

@zomebody The simulation mostly runs single threaded, so only on one core. depending on you CPU core count 20% might be one core fully utilized for the simulation. Network speed and lan vs. online has no impact on the simulation speed. With bad network connectivity the game will micro stutter instead of the sim actually slowing down.

@Matr1 Same issue like OP here and you can resolve it with the same solution: https://forum.faforever.com/topic/6807/unable-to-join-a-custom-game/5

@timmony What happens when you click the "Link your FAF account to Steam" button? [image: 1700267029309-link-your-faf-account-to-steam.jpg]

Hi guys, Thanks for getting back to me so quickly. I had tried 'windowed' and 3 numbers separated by commas before, but this was my last attempt (I saw the resolutions for primary_adapter higher up and it had two similar lines for each resolution). I really appreciate that strategic icon scale tip and will give it a go. Thank you. I found the issue. For some reason on the compatability tab of the sc fa properties it was set to run in compatibility mode for windows 7 and run in 640x480 screen resolution was checked. I have no idea why, I have never opened the properties for the game before. This is now resolved.

Name doesn't look bad

No there aren't. It's not possible from a browser alone.

To expand on Nex's answer: You have a sound bug which you can tell by the SND/XACT warnings. 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 > no higher than 24 bit, 48000 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.

i did the sound thing with my headset, i disabled the sound via number 2 and a few other things, but it still crashed, i edited the original message with the new log

thank u so much all this time i had to enable the write box qwq

The client has been flaky lately (heh) because all of the architecture behind the client has been DDOS'ed the past weeks. The server admins have put in a lot of effort to combat this but in the end our resources are limited. It also doesn't help that Cloudflare (that we use for file distribution) has been a bit flaky too the past week. All in all I think your experience matches with what is going on; luckily we're working on it and we've even recently made a major step towards stability and we'd love to hear your feedback on that

@magge Thankyou for your response. I restarted my computer twice. I also re-installed FAF. I also, checked my firewall 'allowed programmes list' as with all the updates something may have snagged on there. It now connects fine. Thanks for your quick response.

Everything worked. with update V2023.11.0 -everything ok

I'd love to have a button to save certain seeds locally.

Command line: C:\ProgramData\FAForever\bin\ForgedAlliance.exe /init init.lua /nobugreport /log "%USER_PROFILE%\AppData\Roaming\Forged Alliance Forever\logs\game_21128057.log" /gpgnet 127.0.0.1:60717 /mean 1765.51 /deviation 429.192 /savereplay gpgnet://127.0.0.1:60715/21128057/Spyhunter777.SCFAreplay /country "" /numgames 2 /numgames 1 Exit code: 1 Engine ver.: 3772 Game tick: 0 ACCESS_VIOLATION: Write to 0x0128CACC Stacktrace: 0x0128CACC KERNEL32.DLL+0x0001FCC7 ntdll.dll+0x00067C6C KERNELBASE.dll+0x00136DC0 gameoverlayrenderer.dll+0x00088288 MiniDump: From 0x0128CA8C to 0x0128CB0C 401CC35589E58B45085D8B4004C35589E58B45085D8B4004C35789F1E89EFBFFFF5F5E5B89ECE979245EFFC3F30F10442410F30F1105F0132901E9C04F64FFC3 5589E557565383EC3CC7042492152901FF1578F3C0005189C3C74424041E172901890424FF158CF4C000565689C6C74424049B152901891C24FF158CF4C00057 DLLs: C:\WINDOWS\SysWOW64\KERNEL32.DLL C:\WINDOWS\SysWOW64\KERNELBASE.dll C:\Program Files\AVG\Antivirus\x86\aswhook.dll C:\WINDOWS\SysWOW64\SHLWAPI.dll C:\WINDOWS\SysWOW64\msvcrt.dll C:\WINDOWS\SysWOW64\USER32.dll C:\WINDOWS\SysWOW64\win32u.dll C:\WINDOWS\SysWOW64\GDI32.dll C:\ProgramData\FAForever\bin\BugSplat.dll C:\WINDOWS\SysWOW64\gdi32full.dll C:\WINDOWS\SysWOW64\ADVAPI32.dll C:\WINDOWS\SysWOW64\msvcp_win.dll C:\WINDOWS\SysWOW64\sechost.dll C:\WINDOWS\SysWOW64\ucrtbase.dll C:\WINDOWS\SysWOW64\RPCRT4.dll C:\WINDOWS\SysWOW64\comdlg32.dll C:\WINDOWS\SysWOW64\ole32.dll C:\WINDOWS\SysWOW64\combase.dll C:\WINDOWS\SysWOW64\combase.dll C:\WINDOWS\SysWOW64\shcore.dll C:\WINDOWS\SysWOW64\SHELL32.dll C:\WINDOWS\SysWOW64\WININET.dll C:\WINDOWS\SysWOW64\WS2_32.dll C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.19041.3570_none_c0ddcb7e38bd1f11\COMCTL32.dll C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.19041.3570_none_c0ddcb7e38bd1f11\COMCTL32.dll C:\WINDOWS\SysWOW64\urlmon.dll C:\WINDOWS\SysWOW64\VERSION.dll C:\ProgramData\FAForever\bin\dbghelp.dll C:\WINDOWS\SysWOW64\X3DAudio1_2.dll C:\WINDOWS\SysWOW64\faultrep.DLL C:\WINDOWS\SysWOW64\DSOUND.dll C:\WINDOWS\SysWOW64\d3dx9_35.dll C:\WINDOWS\SysWOW64\d3d9.dll C:\WINDOWS\SysWOW64\WINMM.dll C:\WINDOWS\SysWOW64\iertutil.dll C:\WINDOWS\SysWOW64\srvcli.dll C:\WINDOWS\SysWOW64\netutils.dll C:\WINDOWS\SysWOW64\powrprof.dll C:\WINDOWS\SysWOW64\powrprof.dll C:\WINDOWS\SysWOW64\kernel.appcore.dll C:\WINDOWS\SysWOW64\winmmbase.dll C:\WINDOWS\SysWOW64\dwmapi.dll C:\WINDOWS\SysWOW64\windows.storage.dll C:\WINDOWS\SysWOW64\Wldp.dll C:\WINDOWS\SysWOW64\IMM32.DLL C:\WINDOWS\SysWOW64\bcryptPrimitives.dll C:\WINDOWS\SysWOW64\uxtheme.dll C:\WINDOWS\SysWOW64\UMPDC.dll C:\Program Files (x86)\Steam\gameoverlayrenderer.dll C:\WINDOWS\SysWOW64\OLEAUT32.dll C:\WINDOWS\SysWOW64\CFGMGR32.dll C:\WINDOWS\SysWOW64\PSAPI.DLL

There was a recent hotfix patch that caused this issue. I know it is frustrating; Creating more threads about it will not speed up the process. As mentioned in the initial post, a fix is being worked on. Please, just be a bit more patient.

Since this issue pops up every now and then: https://github.com/FAForever/faf-user-service/pull/185

Seems to be working for me now on the same alpha client

Fixed. No idea how.