-
Notifications
You must be signed in to change notification settings - Fork 44
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
Autonomous States doesn't work properly with command centers #87
Comments
To add to this, I tested several things and I think I've narrowed down the issue to Autonomous States don't update while a system is ON. During testing of both Command Centers and Power to Command Centers, it appears that if I blow up the CC or Power to the CC without turning a SAM on, the autonomous state updates correctly and the SAM remains off. However, if you activate the SAM site, without being shot at, and then blow up the SAM site, it will NEVER turn off even if commanded to go dark at the loss of a CC. In the test mission, I have:
The SA-15 is set to act as point defense for the SA-10 (not that it matters). The SA-10, SA-15, and 55G6 are set to have a ConnectionNode to the command center. The Power Unit is connected to both the 55G6 AND the Command Center. In testing:
Here is the relevant IADS LUA.
The intended behavior is the SA-10 goes dark regardless of whether it was ON or OFF at the time of CC/Power destruction. |
I have performed the same testing with simple mission, included: One very different thing - I destroyed CC by friendly fire from F-18C, so, no contacts were displayed in debug.
Below the script I've used for the mission. Quite simple.
Earlier testing included power sources connected to CC - same behaviour, EWRs didn't go dark when CC is not powered. |
Autonomous states do not work right with command centers, they will turn off and go live when you get into range instead of staying off
The text was updated successfully, but these errors were encountered: