I tried again, and the next attempt was at least 60+- my target.
#Eon timer gen 2 update#
After another run, I hit something like 600, and entered that into the Update field. After changing 'target seconds' to 45, I hit a 666 delay, entered that into the Update field, and re-tried. My normal calibrated delay at 52 seconds is 610 and my calibrated seconds is 14. Shouldn't the "seconds" value only be linked to the first timer?įor example, I tried out '45' for my seconds value. I just want to be able to change 'target seconds' values at will.
I tried re-calibrating at different second values, but I wasn't hitting the adjacents like I was 52 seconds, because timer #2 was different. After trying a few different second values, I realized that EonTimer was changing the second of the two timers every time I changed the seconds value. What's the easiest way to change my 'target seconds' value in Gen IV? It's at 52 right now, but that's like a 38 second wait for the first timer (unnecessary).
You obviously know this, but may I suggest mark it as milliseconds or even just changing it to frames to make it more consistent with the 4th gen display? BTW, the timer works just as well for Emerald as it does for the DS games, keep up the good work! I've been using the timer for Emerald lately and I noticed that when I enter the "actual" frame to calibrate for time, the offset is in milliseconds (it took me a while to figure out why the number was sometimes so big). ToastPlusOne, I have a suggestion to keep some consistency between your timers. All of this has been addressed in the research thread and in the on-site articles regarding RNG abuse. Every once in a while when I'm going for a frame, I'll encounter an odd frame when I typically hit even, but I don't know why this happens. However, I have not experienced this myself. To shed some light on the dual slot, it has been known to change the delay from odd to even (or vice versa) if a game is inserted, then change back when the game is removed.
0 kommentar(er)
