Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
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
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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.