วีดีโอ

yes. you can now set task success in the Enter-function.

There are actually scenarios where state tree is better over BT. State Tree is Unreal Engines implementation of a finite state machine mixed with behavior tree tasks. Behavior Trees are more task based and are not built with the mindset of jumping from one node to another by user's direct control. So if you want precise control over an AI behavior then a behavior tree is less ideal. I have created boss AI in Unreal Engine and I typically use a behavior tree combined with a blueprint created finite state machine for more precise control over the AI while still having the benefits of BT tasks. State Tree has the potential to be the only solution I need. A state tree allows you to access varialbles easily through UE5's new property access tool so a black board isn't as essential as you might think. Tho a black board type of solution for variables related to AI behavior would be nice, maybe they might add it eventually.

It would be really simple I think! You can have a few states and name them based on the behaviors you would want: ex. "Flee", "Wander". You would just have a state tree task(s), that would run the code for running away from a target or something similar, be under a state. Then this state you can just add conditions for when it should switch over to other behaviors/states. The only thing is that there could possibly be a bit more complexity for the conditions or for when some code should be run on tick. But you can always use child-states to improve the structure.

Because Epic doesn't give a fuck about the user

Because their target audience is people smart enough to read what's there and figure it out.

@@TH-camAccountMan yeah... probably... or probably the documentation was not even there on the source code for this feature at the time of this post... who would know.

As of now its likely better to stick with behavior trees due to the lack of documentation and debug features for state trees. Behavior trees are simply a more polished feature. However, if you are willing to make your own methods of debugging or once debug features get added to state trees by unreal then I think its worth learning state trees! Though if you really want precise control over your AI then state trees will help you a bit more here. As for the future plans of unreal and state trees, I can't answer that since I don't know, but it seems they might keep it for now. And the Ontick event stuff, currently the main aspect being on tick would be that workaround for the "Enter State" bug, but if Unreal fixes this bug then State Trees should have less code on tick compared to behavior trees, so performance should be better in theory!

I definitely think this is sticking due to its general purpose. This is not only an AI tool. I've used it for other actors and it makes for nicely structured code, often taking complexity from a big actor and splitting it out into separate simpler bps. As for AI use, I'm struggling a bit to get the grips on the order of events.. and how things are executed.. so def something to be learned. It is not as simple as it looks, imo.

Heard nothing so far about it, I'm not even entirely sure if its a bug or not but I believe it is. Maybe it might be fixed in some future updates.

By the same I assume you mean if there will be more tutorials about State Trees? Unfortunately as of now I don't have any plans for any more tutorials regarding state trees (Or other kind of tutorials). Maybe if there is plenty of demand for a specific tutorial I could look into it. You could start giving me ideas if you'd like! I would need to consider if I have the necessary knowledge to actually create a tutorial though as I don't want to teach wrong information and I'm still learning things in unreal myself :) But if I feel confident enough I can create more whenever I have the time!

@@uberaugh476 That's very kind of you to be so upfront. I appreciate your point of view regarding this. I'll be contacting you here (or if you've other means) regarding my progress with State Trees, with the hope that we both can learn from each other ☺️

Short Version: If for your care more about performance and precise control of AI behavior execution. Then state trees area probably the better choice. Note that lack of support resources means you might very likely be on your own incase you run into problems. (for now) Long Version: As far as I know, if you want to focus more on performance then you might want to consider using state trees over behavior trees. That's one of the main appeals for state trees. What I had realized is that with state trees, the AI doesn't have that awkward "pause" I see occur with behavior trees if you set it up right. (not sure if this still happens) Furthermore, state trees gives you precise control over how the AI behaviors execution flows. So if you want to really control when and how the execution of the AI (while keeping good performance) changes, then state trees would be better. They are also good if you want a bit of an easier overview of the AI behaviors if that's important for you. However if you are using the EQS System you might want to stick to behavior trees, as I'm not sure if these work with state trees as I've never tried them. I'd personally say its down personal preference or a per-project basis. If you want to practice specifically using state trees, or if your project relies on very precise control of AI execution flow, then state trees are likely better to choose. But by default, most other projects should be fine using just behavior trees. But keep in mind that is still a rather big lack of documentation, tutorials & any forums for state trees. So if you ever run into problems with state trees you are very likely on your own until more of these tutorials and stuff comes out.

@@uberaugh476 Thanks for the comprehensive anser! :) I like the look and feel of State Trees much more and I am a bit more used to state machines as a concept that generalizes to a lot. I also like to be able to run as many tasks in parallel as I wish. However, in Behaviour Trees, the highlighting of active branches and leaves when playing in editor is a really nice debug feature. And as you just said, documention is much better. So I go with Behavior Trees for now and switch to State Trees when necessary. Event I'd really like to ditch Behaviour Trees.

@@donnyjoe7653 Yes you are indeed right! I forgot to mention the part where behavior trees do have much better debugging features like you said. And this is something that I think is probably holding state trees back as a more viable option. Since I have run into issues debugging with state trees due to the lack of debug features that I know it contains.

Generally StateTrees will probably replace BT at same point, they can do all the same and much more/better from what I can see, just a matter of getting polished, quality of life improvements, bug fixes. I think you can still do the debbuging of AI behaviours with other debugger tools like VisualLogger/GameplayDebugger. Though if you are planning on adding upon complexity to your game, different types of AI etc/tasks, it seems much cleaner and more flexible with State Trees - well you gotta learn them one day anyway so it might be just better to start off as soon as possible :)