Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Zeus spawner breaks/broke with HCs #156

Open
Joecuronium opened this issue Mar 20, 2023 · 2 comments
Open

[Bug] Zeus spawner breaks/broke with HCs #156

Joecuronium opened this issue Mar 20, 2023 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@Joecuronium
Copy link
Collaborator

Describe the bug
During the first LdB op, when trying to spawn units with the Zeus interface, the spawner would spawn one (1) base unit and not gearscript it. It did not try to spawn more than one, even if given the command to spawn a group, and gearscript never ran. Issue persisted after the HCs disconnected, units already spawned on HC needed to be deleted and respawned on the server to function again.
To Reproduce
Steps to reproduce the behavior:

  1. Start mission with HCs
  2. Try spawning enemies from the CAFE3 Zeus interface
  3. Watch as it may or not work (worked as expected 10 minutes before the above incident)
  4. Non-Profit????

Expected behavior
itjustworkstoddhoward.png

Environmental Info(please complete the following information):

  • MAIN
  • GM
  • 1.51.joe.whateveridontfuckingnowitsrunningmyforkwhichdoesnttouchspawningonlycampaignstuff

Additional context
Thx Gibbs for reminding me.

@Joecuronium Joecuronium added the bug Something isn't working label Mar 20, 2023
@dgibso29
Copy link
Collaborator

Replicated today while testing AA3 mission #2. 1 HC connected, same symptoms as original report and same resolution after killing the HC.

The units we not added to the Zeus overlay either, so execution is getting lost/stuck/errored out prior to that point.

@dgibso29 dgibso29 added this to the 1.7.0 milestone Aug 14, 2023
@Bubbus
Copy link
Collaborator

Bubbus commented Apr 24, 2024

Looked through the related code today to see where it might be potentially failing - about all I can do locally.

Nothing obvious, but there is a fair amount to go through. Given that the reports say "works until it doesn't", I'm tempted to say it's some variable or parameter changing in a way we're not expecting. We'll need to test on a live HC with logs.

We don't use HCs in CA currently, so I'm thinking we push this back into 1.8.0 for now.

@dgibso29 dgibso29 modified the milestones: 1.7.0, 1.8.0 Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants