Current millisecond

sugarglidertotten

broadcast [ the answer isv]
broadcast [No v]

BloatedUnderpants3

no support. many people who use scratch wouldn't notice

-iviedwall-

Macie1234 wrote:
Abstract- wrote:
Macie1234 wrote:
Abstract- wrote:
No Support. We don't need to track down every millisecond.
Think animations and clocks
Most real clocks don't track milliseconds.
How would this be used in animation?
Timing between frames.
In clocks, sometimes you want to have a smooth second hand.

Yes, you can use

wait (.05) secs

that's 50 millisecs.

-iviedwall-

Scratch has speeded 30 frames per second, which there will be a 0.033 secs (or 33 millisecs) delay between every movement even there are no wait blocks, and apparently, it's the fastest speed on Scratch (unless you have TurboWarp, you can make the speed 2 times faster) without any other modes, so we don't have to track down every millisec.

templeofbruh2

thx

sugarglidertotten

if <> then
(your mum is vegan<[] = []>)
end

Tunde123

sugarglidertotten wrote:
if <> then
(your mum is vegan<[] = []>)
end

Please do not blockspam. You can do that here.

LightBoy77

This falls into the category of this would probably be useful for people who want to make advanced code, but normal Scartchers wouldn't really use it.

_3qp

I'm confused. Are we talking about the current millisecond (gets back to 0 after one second/minute/etc) or milliseconds since the Epoch (milliseconds since January 1, 1970)?
If it is the first one, then this workaround should work (I haven't tested it):

((current [second v]) * (1000))

SuperMarioHome

Milliseconds are 1/1,000th of a second and Scratch frames are 1/30th of a second. This would be unnecessary.

Joyoforigami

No support.

It's called “days since 2000”.

Tunde123

Joyoforigami wrote:
No support.

It's called “days since 2000”.

That isn't what this topic is about.

RED-001-alt

No support, there wouldn't be much use, and as you posted, there's already an easy workaround.

Last edited by RED-001-alt (May 23, 2022 15:12:11)

lolecksdeehaha

-iviedwall- wrote:
Macie1234 wrote:
~snip~
Yes, you can use
wait (.05) secs
that's 50 millisecs.

Scratch has delays between blocks, so that's not nearly as accurate as you think.

Crow_Boy08

we already have milliseconds in scratch its called

wait (0.001) secs

Last edited by Crow_Boy08 (May 23, 2022 15:53:44)

RED-001-alt

Crow_Boy08 wrote:
we already have milliseconds in scratch its called
wait (0.1) secs

lolecksdeehaha wrote:
-iviedwall- wrote:
Yes, you can use
wait (.05) secs
that's 50 millisecs.
Scratch has delays between blocks, so that's not nearly as accurate as you think.

blablablahello

Crow_Boy08 wrote:
we already have milliseconds in scratch its called
wait (0.001) secs

thats literally the same as

wait (0) secs

Since scratch is 30 FPS, for that to run like supposed to be, scratch needs to be 1000fps at the VERY least

Wax01

when green flag clicked

forever
set [ current millisecond] to [((days since 2000) * (((365.25) * ((2000) * (86400000)))
end

kexy321

The Timer variable is the only accurate time with millisecond precision. Using this, we can use the timer to collect the best accurate time from the real world.

when green flag clicked
set [Last Second v] to (current [second v])
forever
if <not <(Last Second) = (current [second v])>> then
reset timer
set [Last Second v] to (current [second v])
end
end

The problem is, the timer wouldn't be accurate from the start of the project. But will then soon reset the timer and send a current millisecond. (This can only give you a timer between 1 ~ 1000.)

Last edited by kexy321 (Aug. 21, 2022 04:36:21)

00ff00

bump

Support.

the

(timer)

block only has 10 ms precision D:

Last edited by 00ff00 (Oct. 31, 2023 21:30:29)

Discuss Scratch