clarification about gen 5 pidrng

[pearl timber]

just to clarify pidrng frames get advanced by trainers moving around (and you can't really influence that, just get lucky), but the seed and timer0 you hit is based on the exact time you boot up the game? new to rnging

[brazen fjord]

The game decides the seed you land based on Date, Time, Buttons held whilst the game is starting up (between pressing A to start the game and the star appearing on the top screen) and the timer0.
The timer0 is the one of these things you can’t really control so you’ll have to get lucky there to hit the timer0 you’re targeting. After that randomly moving NPCs in the area can and will advance PIDrng frames yes so you’ll also have to get lucky there that they advance just the right amount for you to hit your target PIDrng frame

[pearl timber]

how precise is the window to hit your seed? obviously there's inconsistency with getting the right timer0, but do you literally have to be like frame perfect as you start it up?

[brazen fjord]

Gen 5 is only down to the second; having a full second window is a lot of time luckily

The only difficulty of gen 5 comes from timer0 randomness (BW2 is much worse than BW1 here) and moving NPCs pretty much

[pearl timber]

so just to clarify, (if i have the right tid and sid set up) then all I need to do is start the game within the right second window and hope the timer0 and pidrng lines up? is there any other potential source of error other than calculating the wrong id values?

I’ve done a few resets and i haven’t got a single pokémon that was obviously on an adjacent seed, idk if i’m just unlucky or doing something wrong

[brazen fjord]

You’ll need to make a copy of your profile for use in adjacent seed tool that has the timer0 min set to the lowest timer0 you got during calibration and timer0 max to the highest timer0 you got instead of having both be your most common so adjacent seed tool can search through them all

Also since You’re on dsi it’s possible the seed you’ll hit will be up to like 6-7 seconds later than expected with -95 calibration