Bug: Local Sensor Not Called
See original GitHub issueDescribe the bug
Local World Sensor is not updated, and the main action stalls. The sensor is never called. In the Screenshot below the action is ShootAction
and the key is InCooldown
. The InCooldown
is updated per update, but for some reason even the sensor’s Sense
method is not called.
Steps to Reproduce Steps to reproduce the behavior:
- Change the local sensor value from the outsdie.
- Action has an old sensor value and it stalls.
Expected behavior The local world sensor should update even even if there are no current actions.
Screenshots
Unity Version 2022.2.8f
Package Version 2.1.5
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created 4 months ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
javascript - Generic Sensor API not working on localhost
I myself had a ton of difficulty with the generic sensor api and discovered that one of the rarely mentioned requirements for it...
Read more >IOS 16.1.1 proximity sensor
Since updating to IOS 16, the proximity sensor isn't working while I'm on calls. It keeps muting and changing to speaker mode... Is...
Read more >Scrape Sensor: "scrape: Error on device update!"
First time user of the Scrape sensor, but when I try it out I got this error in the log: Log Details (ERROR)...
Read more >Fixed - Sensors are broken [00264] - Community Forums
Sensors can have a dectection field that goes beyond their rendering limit, and they just stop working when not being rendered.
Read more >My entry sensor is not responding.
It was working for a few months t. ... The "Not Responding" error means that the sensor is having trouble checking in with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ok so it’s expected, will close it.
Yes, I do not recommend using the GOAP state as the source of your actual game state. It should just be a compiled version which is only updated when the resolver is run.