movement is one of my hugest hurdles right now. very curious on how world war z handled their ai

Will you be so kind to make an example with pseudo code and/or diagram? It would really help me to understand your point.

@@alexandrm3073 sure man, no problem! It's a word diagram which goes like this: If you're too dumb or lazy to understand what I said or watch the video, consider another vocation. Perhaps custodial services or president of the United States.

@@Deck_Dynasty First of all English is not my native language, so I didn't understand well enough. Second, when I'm elected as a president of the US this November, such rude comments will lead to the death penalty.

When players client does a Sail tick... What is more important: The ships right next to your player character or the ships on the other side of the map? For ships on the other side of the map, the client may not need a sail tick at all for that frame because it wont be seen anyway. Also, its not as important to get thats ships replicated transform data. So the server build will not prioritize that ships replicated transform when sending data to your client. In short, it does not make the tick logic itself faster. It just stops less important ticks from happening that frame in the first place. It helps 2 fold: 1) delay less important ticks to other frames 2) reduce network traffic and replication logic.

Not too much into Unity, but if it is then we have a good chance of epic bringing this system to unreal :p

Yes it is indeed. A big gain of Unity's ECS relies on the cache performance. It's good to see that Rare used it without seemingly having to re-design the standard Unreal way too much.

@@tom.looman I hope we see more stuff like this in more detail 😉😉

@@tom.looman Do you have any idea how you would aggregate something as dynamic as the movement component (since they listed this), where n objects are not depending on one other object, like it is the case with the shown water example? The only idea that came to my mind is caching all controllers and looping through them, but it doesn't look to me like this would result in a noteworthy performance gain. Would love to see one of your great videos tackling that topic, really liked the one showing the gameplay ability system btw :)

Hi @@calmsh0t, that's a great question. Caching all movement components and looping through them manually can have a surprising perf improvement. If you consider the movement component instructions cost is well over 30% of your instruction cache (as I mention in the talk) making sure you do them all when the instructions are hot in the cache is important for cache coherency in a single frame. There's also a surprising knock on improvement from fewer ticks to queue at the start of your frame (especially if you're talking 10's of characters all moving at once). That's only the start of it though. As with most things we've optimised, aggregating is just the first step. Once you have a list of things to transform it's now possible to change your algorithms and get the real speed ups (as per my example with the water heights). Granted that is tricky with the movement components because they're so complicated, but we haven't ruled it out yet! :)

Yeah?