Thank you both for your constructive answers and i will definitely be taking it all into consideration and coming back with any other help/results thanks again! :D
Yes im getting the right iv's and have 5 pokes in my party. Already knew out the cave but figured it could be avoided but guess not lolI'm assuming you've got five party Pokemon when you're walking your steps?
Walking in a cave advances the PIDRNG as well, in case you didn't know (each time you take a step, advances by 2, turn without taking a step, advances by 2). Are you at least getting the right IVs?
this is why you should stick to an IV frame of 1 :s
So my keypress combo is Start X A. How do I do that? Can I just hold Start and X, and then on the second I need to press A, press A and hold it? Or should I press A, release it and right after that press the whole combo?
Does a flawless naive wondercard seed exist for pokemon white? I've been searching for one and it takes a long time to load. Is there a faster way to search for seeds? Thanks
DS Lite delay is only one second, so it's possible you hit a different timer0 that gave the same TID as the result you found. You're only searching 10F5, so it's only searching for matching results under the 10F5 timer0 (afaik, anyway).
I use 10F5 because I got good at hitting that T0 for all other RNG purposes, and given the volatile nature of the T0 I figured that was enough. Would you suggest expanding the range of possible T0's? And if I do that are you suggesting that I will be more likely to find results for what I am actually getting? The thing with that is wouldn't it be meaningless if the seed I need to hit is using 10F5 anyway?
In your sample screenshot where you got an ID of 16603 you hit a timer0 of 10f3, and for the 33037 result you hit a timer0 of 10f6. Unfortunately, for TID frame searching, PPRNG currently only searches timer0 values in the range specified in your configuration. Since you only have 10f5 set in your config, it will not find results on 10f6.
When searching for good seeds it makes sense to narrow your timer0 range to those values which you can usually hit, but in this case you should widen it to allow you to find what you are actually hitting.