Control order of Update functions, or do my own game loop, or a PlayerLoop?

Is there anyway to have finer control over the order of Update functions? I need a PreUpdate function to handle calculations used by the remaining update functions. I see a PreUpdate event in the docs, but it isn’t well documented and I see no examples nor threads talking about it. I’ve also looked at a PlayerLoop, but can’t find much information on how I would use it to adjust my update order.

Is there a standard way to control update orders without needing to write my own update loop?

There’s this:

But really if you need fine-grained control over this it’s often better to just write your own manager class that invokes the methods you need in the order you need.

2 Likes

Thanks. I think that will be enough for now. I might need more later, but this will accomplish what I want initially.

1 Like

Endeavor to put what you call “PreUpdate()” stuff in Start()… that’s what it is for.

Otherwise yes, you would need to control it explicitly.

I highly recommend NOT putting all your stuff in one giant loop because I work with projects like that all the time and it is usually a serious technical debt that cripples all future development.

Here is some timing diagram help:

Here is an abbreviated and better-annotated version of the above: