@jip said in The game keeps crashing:

The keyboard causes the crashes? 🤔

No, it wasn't the keyboard that caused the crash.
Yes I love the keyboard of this crashing computer, sorry my native language is not English and can only use google translate. 🙂

You can test to disable the sound card in BIOS and try with a USB sound card.

We've been dropping mods left and right. We'll try some vanilla runs when we can. In the interim, what can I do to track down the source of this?

An expansion is a new base controlled by its own location manager and with its own brain condition monitor.
So you basically start a new AI brain on any new expansion.

Expansions will be build at free startpoints, and mostly on areas with many mass extractor spots.
Naval bases are also expansions.

I would suggest to only use 2 land and 2 naval expansions for better game speed.
If you use my AI then i would suggest to set land expansions to only 1 and 3 naval expansions.

Onyl thing to mention, the map must have map markers for expansions created by the map autor
or the AI can't buld any expansions.
(If you use the AI-Uveso, then you can enable a option to autogenerate waypoints and expansion markers on any map)

this problem also exists while in lobby. i remember a few times the chat was flooded with messages and the game crashed. not only /31, plain text works too

Well, I tried what you proposed, my game didn't crash since then.

As if was not always crashing, I can't still be 100% sure that this was the problem, but it migh be!

Thanks a lot for your help, I'll come back if the game crashes again.

thanks!

Aaaand I can't get into a lobby again.

Log of failing to download mod before entry into game. I downloaded said mod (1.3x build range) from vault manually and it worked fine, then continued then it got stuck at the "connecting" screen ingame.

Traceback (most recent call last):
File "src\games_gameswidget.py", line 231, in gameDoubleClicked
File "src\fa\check.py", line 174, in check
File "src\fa\updater.py", line 186, in run
File "src\fa\updater.py", line 618, in doUpdate
File "src\fa\updater.py", line 635, in failureDialog
Exception: Update started at 2022-03-28 01:33:58
Using appdata: C:\ProgramData\FAForever
Connected to update server at 2022-03-28 01:33:58
EXCEPTION: <urlopen error [WinError 10054] An existing connection was forcibly closed by the remote host>

Runtime info:

FAF Username: Sine
FAF Version: 0.20.1
FAF Environment: production
FAF Directory: C:\ProgramData\FAForever
FA Path: : C:\Program Files (x86)\Steam\steamapps\common\supreme commander forged alliance
Home Directory: C:/Users/snip/Documents
Platform: Windows-10-10.0.19041
Uname: uname_result(system='Windows', node='snip', release='10', version='10.0.19041', machine='AMD64', processor='Intel64 Family 6 Model 79 Stepping 1, GenuineIntel')

@arma473 said in Trying to understand the T3 Air rush:

Also, T2 bombers are generally used in a much more deliberate way than T1 bombers. Apart from the very beginning of the game (where a T1 bomber is expensive and you won't have very many of them) players will "throw away" T1 bombers without much worry, the same way they might "throw away" a couple T1 tanks to try to raid the enemy.

T2 bombers are a lot more expensive. People generally won't put T2 bombers into an infinite build queue. It would be normal to have an infinite queue like "1 scout 3 interceptors 1 t1 bomber" but it would be weird to have a queue like "5 interceptors + 1 janus." Players generally make T2 bombers deliberately when they have a specific target in mind, like taking down all of the enemy's T2 pgens.

I definitely need to treat my T2 air with a more tactical approach, not the 'overwhelming blob' that works with Land.

I got this crash in current coop as well, 16562051, last version of Blocade mission from the coop discord, second part of the missions
I've tried to delete shader cache as well, didn't help.

@katharsas
That works, thank you very much!!!

The main thing is you're back to playing 🙂

mass is just distributed across projects based on the proportion of build power used. The second option^. So everything just builds slower.
Power stalling is more detrimental in that your mass extractors require power to function.

mission black day

or you could provide the feedback here https://discord.gg/ayzAVr9JUV
where me or someone else will take a look and try to help you out

I feel I should also thank others who posted suggestions. They didn't work, but it was still helpful in ruling out a method that doesn't work, and that is still a step toward a solution, thank you all as well.

Thank you all for your help, @magge, @deletethis, @Sprouto, @Zokora and @arma473. I will play around once more with my sound settings, config, etc.. Should anything useful appear, I will let you know.

Cheers

@poop_dynamics said in Bad connection with Wi-Fi:

cable is always better than wifi, you can have the best wifi router and your pc 30 cm away from the router, a 1,95 $ ethernet cable will still beat your 500 $ wifi setup.

Cable is the way to go, but just saying, wifi over cable is pretty reliable too ;). (actually more reliable if you're abusing an old copper cable for ethernet)
Also, please don't put your PC 30 cm away from the transmitter, the polarization might cause you not to get a signal, you should keep at least 1-2 meters of distance.

@askaholic said in Bad connection with Wi-Fi:

I mean in a 1v1 you’re only sending data over a single connection whereas in a 6v6 you’ve got 11 other people who you’re exchanging data with. Plus there are 6x as many people issuing commands which means each connection is transferring about 6x as much data. Multiply those two numbers together and you need about 66x as much bandwidth for a 6v6 as you do for a 1v1.

FA bandwidth requirements scale linearly with player count, they are symmetric. There are 10 ticks a second, each tick you send and receive two packets with each other player. One is 25 byte, the other is 35-70 byte. Total bandwidth requirement for a 6v6 is ~1.2 Mbit/s down, 1.2 Mbit/s up.

Glad to be of some service. The last resort, that will definitively prove that it's a sound issue - is to use the /nosound switch on the command line that launches Supreme Commander. This will turn off ALL sound - and if the game is stable then, you have proof positive that it's a sound related thing.

Some people have had success in these matters, just getting rid of the music files - which is just a matter of deleting the files associated with the game music - but I'll leave that for another discussion.

I could run the game on Steam and also on LOUD_AI.
The Steam version was old and Loud_AI seemed to always give miserable start resources to humans.
FAF is much better game experience.
I am glad to be back.

without loading savegame cutscenes work well.
How do you test missions then ?
can i somehow disable cinematic in savegame? (tryed to turn them off in the campaign lua script but it seems that these scripts are already included in savegame)