Search Issue Tracker
Fixed in 5.0.X
Votes
0
Found in
5.0.0b14
Issue ID
649331
Regression
No
Execution of State Behaviours is wrong
Execution of State Behaviours is wrong
Repro:
1. Open the attached project
2. The Cube controller has 3 scripts attached:
- one on the Layer: LayerBeh
- one on New StateMachine: StateMachBeh
- one on The New Satate (inside the New Statemachine): StateBeh
3. When the Scene is run, the order of the execution is:
Layer-StateEnter (correct, this is the Default state being entered)
State-StateEnter (incorrect, the Layer code should be executed here)
Layer-StateEnter (incorrect, the StateMachine code should be executed here)
StateMachine-StateEnter (incorrect, the State code should be executed here)
The order is: State->Layer->StateMachine
Expected: Layer->StateMachine->State
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment