#is a 0 second delay on a delay chip an actual time ingame?

72 messages · Page 1 of 1 (latest)

worn creek
#

Yes, it's 1/60 seconds

earnest sparrow
#

noice

#

thx

worn creek
#

Np

cold torrent
#

A 0 second delay will output on the next Cv2 tick

#

If you run a delay for 5 seconds, it will run for 5 seconds, and after those 5 seconds, it will execute on the next Cv2 tick

manic pebble
#

Maybe they're referring to the 60hz thing everyone talks about where you use both outputs of a 0s delay?

#

I've been soooort of told that if you do it once it outputs at 60hz, as if it was delaying it by half a tick, but that if you do it any more than that it doesn't just keep improving and just attempts to do multiple executions in the same tick. Wasn't sure how it works but i stopped asking because nobody was able to explain why it works that way to me.

worn creek
cold torrent
#

You will never see delta time be perfectly at 1/60 or 1/30

#

which is why its better to say “Next tick” not “In 1/60 of a second”

manic pebble
#

Oh, so CV2 is 60hz?

cold torrent
manic pebble
#

I always thought it was supposed to be 30hz and some weird jank allowed it to be 60hz

cold torrent
#

Update 30hz doesnt update 30 times a second

It updates once every other cv2 tick

manic pebble
#

It's supposed to update at 30hz though, but i get that it doesn't always work

cold torrent
#

No, Cv2 is supposed to be 60hz

#

Event Receiver (Update 30hz) is half of the tick speed

#

which, in theory, should be 30hz

manic pebble
#

i'm saying the Update 30hz is supposed to update 30 times per second

cold torrent
#

but in reality its around 20-40

cold torrent
#

It outputs a signal once Every Other Cv2 Tick

manic pebble
#

It's supposed to be 30 though and just can't always be accurate, which is what i'm saying

cold torrent
manic pebble
#

Oh i was about to ask that, is the delta time not accurate?

cold torrent
#

its not delta time, at all

manic pebble
#

I thought it was meant to change with the frequency as it fluctuates

cold torrent
#

its 1 / 30

#

its litterally the reciprocal of 30

#

I believe this will be fixed next cv2 update, giving us working delta time

manic pebble
#

So it's just set to 0.03~ constantly

#

ahh okie

#

because yeah that literally has as much use as a random float variable or parse float 😆

#

Is there a particular reason it's been like that for so long? Or have they just not gotten around to it?

cold torrent
#

Or atleast they forgot about it until I brought it up lol

manic pebble
#

I've heard others mention making their own somehow, but i'm not sure how that would work, increment a variable by 1 constantly and then divide 1 by it at the change of each second?

manic pebble
#

Though that would give you results a little late

cold torrent
#

so you need a way to calculate the time between executions

manic pebble
#

Right, what i just said would be the average at the end of each second

cold torrent
#

you want the time between the last frame and the current frame

manic pebble
#

Yeah, so how do people do it?

cold torrent
manic pebble
#

and a delay chip?

cold torrent
manic pebble
#

To get it to 60hz, instead of 30

#

Unless it doesn't need to be that specific?

cold torrent
manic pebble
#

ah okie

manic pebble
#

Also random question, is there any benefit to making a "120hz" or higher execution? I understand that it'd just be double-executing each tick (or at least trying) but would there be any general use for that?

cold torrent
#

you cant go above tick speed

#

"120hz" just means "Execute twice every tick"

#

which also means double CPU

#

where as 60hz uses no more heat than 30hz, because they are both less than or equal to tickspeed, the only difference is that 60hz uses X amount of heat every Cv2 tick, and 30hz uses X amount of CPU heat every other CPU tick

manic pebble
#

I'm asking if there's any general use for it, i just like knowing weird bits of information for stuff

cold torrent
manic pebble
#

You know what

#

a use is a use 😆

#

Too sketchy to be anything i'd wanna use in my own circuits but it's something i know now

worn creek
manic pebble
#

It wouldn't make anything smoother, as it's not actually updating at twice the rate, just updating twice each tick at the same rate, so it would actually make movements more janky, having them stutter

worn creek