fix(detector): fix player detection by guards and cameras #19
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.
I've implemented a new
Detector
mechanism which is used by cameras and guards to check if they can see the player.Description
This
Detector
remembers if player is still in the detection area until he gets out. On each_process
call, if player is still in the area, it will trigger a raycast to check if it sees the player and emit a signal when it does.Motivation and Context
There was a bug when player entered the detection area while partially hidden behind a wall. At this point we didn't detect him and that's what expected, but this issue was if the player, while staying in the detection area, goes fully in front of camera/guard and wasn't detected.
How has this been tested?
I've altered levels to make this cases simpler to test, and I've reset them.
Screenshots (if appropriate):
Types of changes
Checklist: