Disable g-forces for UAV AI #5094
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
How about moving the virtual unit detection to a more central component such as ace_common? Only one unit event handler would be needed an all components could grab the data. I think it would be useful for a few other cases as well. |
|
So #5093 only applies when remote controlling the drone, not when managing it as drone operator? |
|
Can confirm. Just happening from zeus. UAV operators are uneffected. |
jonpas
approved these changes
May 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A zeus can remote control UAV
Doing so means that typeOf ace_player = B_UAV_AI
(has some other weird effects)
This exits the gfroce pfeh if the unit is virtual or AI