Search Issue Tracker
Not Reproducible
Votes
1
Found in [Package]
1.0.5
Issue ID
BEHAVB-105
Regression
Yes
[build only] Behavior event channels not initialized when start node is run
Original thread: https://discussions.unity.com/t/behavior-event-channels-not-initialized-when-start-node-is-run-build-only/1556967
*Description*
Event Channel is null in build when called directly by OnStart node.
*Reproduction steps*
# Create a new Behavior Graph
# Create a new Event Channel
# Call {{SendEventMessage}} node using the EventChannel
# Bind the graph to a scene (using a BehaviorGraphAgent)
# Build the scene into a player
*Expected behaviour*
The EventChannel instance is always valid to be used.
*Actual behavior*
The EventChannel instance is null on player build.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note:
User reports that this issue has been fixed in a recent version: "When I reported this, v 1.0.5 was the newest one (Nov 20), since v 1.0.6 came out Nov 21. Issue is fixed."
On forum:
https://discussions.unity.com/t/behavior-event-channels-not-initialized-when-start-node-is-run-build-only/1556967/8