dronenglish
Recruit

Summary:
I've been running a captain mode server for 7 months now. I've increased troop size to a point where this was a rare issue. On the rare occasion this did happen (with a full server and when mostly high troop infantry was selected by players) this error/warning would happen (see images in Media). The console seemed to indicate it would retry a bunch of times and 90% of the time it would eventually spawn everyone. The other 10% of the time it would crash. Which wasn't a big deal, because the server console would close and my batch file would restart the server.
I think there was an update to Dedicated Server this last week/a few days ago. Now when the above scenario happens, (a) it does not seem to retry and the server eventually stops responding, and (b) the console does not close (so unfortunately the server never restarts because the process is still detected as running by my batch file - which is arguably the bigger issue).
Wondering if something changed here with the last update. I think I saw something download a few days ago and this has been happening this way since. I know there is a technical limitation on the number of troops but it seems like it's handling this spawning issue differently after the update.
How to Reproduce:
1. Run a custom captain server with enough of a troop size and players to cause the error/warning during spawning of troops at beginning of round.
2. Wait for round to start
3. Observe server console
Results:
a. Since the last update, it doesn't seem to retry spawning
b. Since the last update, server stops responding but server console never closes so batch file does not auto restart server; server has to be manually restarted
Expected Result:
a. Before the last update, it would retry spawning and eventually spawn 90% of the time
b. Before the last update, if it didn't succeed at spawning it would at least close the console so server could auto restart.
Media (Screenshots & Video):
This is where I could see it retry before the update:
This is the state I found the server in a few hours after the issue occurred (did not close):
I've been running a captain mode server for 7 months now. I've increased troop size to a point where this was a rare issue. On the rare occasion this did happen (with a full server and when mostly high troop infantry was selected by players) this error/warning would happen (see images in Media). The console seemed to indicate it would retry a bunch of times and 90% of the time it would eventually spawn everyone. The other 10% of the time it would crash. Which wasn't a big deal, because the server console would close and my batch file would restart the server.
I think there was an update to Dedicated Server this last week/a few days ago. Now when the above scenario happens, (a) it does not seem to retry and the server eventually stops responding, and (b) the console does not close (so unfortunately the server never restarts because the process is still detected as running by my batch file - which is arguably the bigger issue).
Wondering if something changed here with the last update. I think I saw something download a few days ago and this has been happening this way since. I know there is a technical limitation on the number of troops but it seems like it's handling this spawning issue differently after the update.
How to Reproduce:
1. Run a custom captain server with enough of a troop size and players to cause the error/warning during spawning of troops at beginning of round.
2. Wait for round to start
3. Observe server console
Results:
a. Since the last update, it doesn't seem to retry spawning
b. Since the last update, server stops responding but server console never closes so batch file does not auto restart server; server has to be manually restarted
Expected Result:
a. Before the last update, it would retry spawning and eventually spawn 90% of the time
b. Before the last update, if it didn't succeed at spawning it would at least close the console so server could auto restart.
Media (Screenshots & Video):
This is where I could see it retry before the update:
This is the state I found the server in a few hours after the issue occurred (did not close):