How does the game loop actually work?

[anonymous_user_f77a82de]

The debugger helped a lot figuring this out. The easiest way is to create a custom actor with a tick function adding a break point to the beginning of the function; using the debugger one can easily see the call stack. Alternately, you can also perform an "informed’ crash by dereferencing a null-pointer which will also yield the call stack in the crash reporter; the call stack looks much nicer in that reporter than in the debugger haha.

Is there something you are looking at in particular?

Yeah i think I recalled that everyclass atleast gets called once per cycle? Like if it 120 frames unless it’s in some tick or special function it just gets called once every 120fps or 60fps etc etc. And is 4.15 a build I’m supposed to be using I’m running into alotttt of bugs… Where I think it’s my called but not and just have to reset the engine