Got a question again. When I RNG, these are the values I always put in the PikaTimer 2.0:
Calibrated Delay: 480
Calibrated Second: 14
When I put my Wanted Delay in it, with the Wanted Second, I always end up with a Total Change of -14. That's when I checked my delay with calling Elm. When I got that -14 change applied, and do another run, I end op on 1 sec TO early. So let's say my time is 14:32:34, I suddenly hit 14:32:33. For that, I had to add 0,5 sec to my first timer, and with that, I can hit my delay right away. But, my question, how come that I have to edit the timer so much before I can hit my delay right? Do I need to calibrate?
I had exactly the same problem, and I think I know why it happens:
When you soft-reset your game when the first timer hits zero, the game
actually starts loading (and therefore starts the delay counter) when you
RELEASE one of the 4 buttons, not when you press the last of them. Try
holding Start + Select + L, and only press R really really briefly when the
timer hits zero. Should make a difference of about -14 to -16 in the
Total Change department.
Another thing I observed:
If you want to hit a certain second (which is always the case) along with a
certain delay, it's beneficial if you
set the DS clock and then start the
Timer around 0.5 seconds later. This way, you always press A within the
one-second time window you're trying to land in, but if you have to ajust
your delay and make it a bit shorter, you'll still land on the second you
want; if you set your DS clock and start the timer at the exact same time,
you'll miss your second by one if you press A just a tiny bit too early.