derkork
commented
3 months ago Thanks a lot for going through the trouble of making a video! So if I get this correctly, the problem is that for some reason the move state is not entered consistently all of the time. So now I see two ways that this could go wrong:
- There is some bug in the library that randomly occurs. In this case we should see an event being sent to the state chart but no transition would result from this.
- The library works correctly but the event that should trigger the transition is not sent to the state chart - hence no transition happens.
In either case the solution revolves around the appropriate event being sent so a state change can happen. So as a first step I think we'll need to check that the event is indeed sent at the right time. As you have pointed out there isn't a lot to see in the C# debugger. This is because the C# scripts are just a very thin wrapper around the core library which is written in GDScript. So all the "magic" happens in GDScript land and is therefore invisible to the C# debugger (arguably there isn't really a lot to see on the GDScript side as well). Nevertheless, we have some debugging aids that can help with this.
- We can use the built-in state chart debugger to see what's going on. Every state chart has a "track in editor" flag. If we turn this on, we can see the chart in the editor while the game is running:
There is a history panel showing what events were received and how the state chart reacted to this.
- We can drag a state chart debugger directly into the scene and connect this to the state chart. This gives us a similar view than the in-editor debugger but right in the game:
- We can listen to the
event_receivedsignal of the StateChart and print whenever we receive an event in code. This can help us see whether we get the event in the first place:
and then:
// this is for debugging purposes so we can see when some event is received
private void OnEventReceived(StringName evt)
{
GD.Print("Event received: " + evt);
}I have created a small demo project showing all these options if you want to see it in action:
I think with this we should be able to see what events go into the state chart and how it reacts to these and this will hopefully help in finding the root cause of the problem and coming up with a fix.
BasHamer
when it fails then it fails for all initializations.
below is my Godot setup and the code. When this condition occurs I find that the mob never enters Move State. None of the mobs do. When the bug is not happening everything works great. I've been chasing this thing down for a while now trying to figure out (6+ weeks) where the race condition could be and I'm getting pretty confident that it is in the Compound State. When looking in the Debugger (C#) I have a hard time telling what is going on as the StateChart and Compound State show as Node and I can't figure out how to view the Compound State state.
`public override void _Ready() { ... StateChart = StateChart.Of(GetNode("StateChart"));
...
}
internal void _on_spawn_state_entered()
{
AnimationPlayer.Play("spawn");
}
`
video should be ready in 40 min https://youtu.be/beAuaZE9S_g (unlisted)