Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Make the most accurate counter for one second.
For program testing I'm going to use this nice online tool. You can use it yourself to test.
You have to make a one second counter that beats the person's above OSS.
What's OSS? One Second Score. How many seconds untill your little counter breaks, and starts counting incorrectly?
You have to try beat the person's above OSS.
Rules are simple:
1) Beat the person's above OSS.
2) The entry into your machine has to be able to be done automatically, e.g. from falling hits a few boosts and enters into your machine
3) You can define when to start counting
4) OSS score stops as soon as you feel the timing's beginning to go wrong.
5) Anything you want really.
Here's mine:
OSS: 3 (3 seconds before it starts to noticeably fail)
Offline
PWOInZhuJqcEI is accurate to 1000ms +/- ~25ms.
I just wrote a little application that started and stopped a stopwatch every time a cake was touched.
You'll never be able to get a fully accurate 1 second timer, since there will always be lag within the client.
Additionally, your resource won't help very much given the average human reaction time is between 200-400ms.
*u stinky*
Offline
Pages: 1
[ Started around 1738280515.4023 - Generated in 0.040 seconds, 10 queries executed - Memory usage: 1.41 MiB (Peak: 1.52 MiB) ]