south crane
Delta time is the time between executions
Event Receiver (Update 30hz) doesnt output perfectly at 30hz (eg. 1/30, the old delta time)
It updates, usually, between 20-40hz, with inconsistent timing
If you want to see your hz, set a text sign to 1/ Delta Time
wispy talon
Depends on how often the executions are being fired
For some platforms it may be higher as they execute less often.
south crane
Heres a better way to think of it
Dont think of Update 30hz an 30hz
Think of it as half-tickspeed
Update 30hz does not output on its own, it actually only outputs once every other Cv2 tick
wispy talon
Heres a better way to think of it
Dont think of `Update 30hz` an 30hz
Think of ...
If only we had 60htz event receiver so we could have a Deltatime port with 60htz not using the setup 
south crane
If only we had 60htz event receiver so we could have a Deltatime port with 60htz...
30hz > 0 second delay > custom delta or (30hz delta / 2)
Because its the time between executions
wispy talon
30hz > 0 second delay > custom delta or (30hz delta / 2)
I wouldn't rely on /2 in case there is a lag spike
last oar
@south crane why is it not .033 on the screen, did they make it better to have actual delta time?