[UE4]AI中使用Tick()函数的性能问题

最新推荐文章于 2024-08-16 18:12:04 发布

原创最新推荐文章于 2024-08-16 18:12:04 发布 · 1.5k 阅读

1 ·

CC 4.0 BY-SA版权

文章标签：

#UE4

UnrealEngine 专栏收录该内容

186 篇文章

订阅专栏

本文探讨了在Unreal Engine 4 (UE4)中使用Tick函数控制AI的传统做法及其存在的性能问题，并介绍了现代AI设计中采用事件驱动和行为树的方法来提高效率。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Tick()函数一般是debug时用的，正规的逻辑中，如果要用Tick函数，可以考虑用UE4提供的事件代理(Event Delegate：http://aigo.iteye.com/blog/2301010)。

参考：
Using Tick() within AI?

https://answers.unrealengine.com/questions/62519/using-tick-within-ai.html

Using Tick for controlling AI has a (very) long tradition, so it's a good start. Nowadays we don't do that since every tick counts (as if it was not the case more years back! ;)). The main problem with tick is that most of the time your AI won't have anything new to do every tick, so most of that Tick function calls will be wasted performance.

The right way to do AI is to have it event driven, where AI responds to events in the world (like being shot) and case of no events it's just performing some kind of scripted behavior (scripted in a sense there's a piece of code producing a sequence of action that AI follows).

UE4's way of controlling AI is by Behavior Trees. And don't be scared by the "Experimental" label - all that's experimental in our BTs are tools, and only because they just need the Epic polish to reach the right quality bar. I strongly encourage everyone to use it! :D

Cheers,

--mieszko