@Alsabino: Your best recourse for high frames is to journal flip. Sad but true! There is no way of legitimately
getting around it.
Originally Posted by Fat Jawshua
So, I'm trying to figure out how to use emloop to hit higher delays today, and I've come across a problem. When I get to this step (in Syberia's guide):
I get a seconds value of 12.95. I adjust my pre-delay time to 60.2 to account for the adjacency of my seconds result to 13. My problem, however, is that I can't hit a target time of 13 seconds. My typical seconds range is 14-15. What do I need to adjust in order to make this work?
You need to find out what delay it takes for your game to load. He details how to do so in step nine; basically, you take a target delay that has a higher seconds value than the time it takes for you to hit A on the Continue Screen (from when the game starts loading at the blank, white screen). You try to hit that seconds value as closely as possible, and then catch a Pokemon to figure out what delay you truly got.
Then you take the true delay, subtract the target delay from that value, and the resulting number is your game's loading delay. You would now add that result to any target delay you wish to hit; you'll find that now your targets should be more accessible (unless they were extremely low to begin with, but I don't believe you'll have much trouble with that).