2^32 = 4294967296, and RNG Reporter actually won't let me perform a 3rd Gen Time Finder search (on the "Capture" tab) with that as my max frame. Is the maximum number of spreads actually 4294967295 (2^32 - 1)? I believe I recall hearing that at some point, and it does let me perform a search with that as my max frame (though it crashes).2^32 unique spreads for each non-bred method.
Yes, by definition a 32-bit seed will have 2^32 different values. But generating that many frames at once is pretty much guaranteed to cause a crash unless you have a really good computer (mine can only handle about 100 million frames at a time in the main window, and even less in Researcher).2^32 = 4294967296, and RNG Reporter actually won't let me perform a 3rd Gen Time Finder search (on the "Capture" tab) with that as my max frame. Is the maximum number of spreads actually 4294967295 (2^32 - 1)? I believe I recall hearing that at some point, and it does let me perform a search with that as my max frame (though it crashes).
No, it's precisely 2^32. Don't forget the seed 0x0!2^32 = 4294967296, and RNG Reporter actually won't let me perform a 3rd Gen Time Finder search (on the "Capture" tab) with that as my max frame. Is the maximum number of spreads actually 4294967295 (2^32 - 1)? I believe I recall hearing that at some point, and it does let me perform a search with that as my max frame (though it crashes).
Are you inputting the correct time(Hr and mins) and date for
Eontimer?
RNGreporter?
DS?
How many calls you used to check your seed?
Roamers?
NPCs?
sync?
Need more data/result/information.
No RoamersRoamers?
NPCs?
Journal entry?
Are you really sure your seed and rngreporter is set for a specific sync?(this actually happen alot)
Need more data/result/information.
As far as I'm aware I am@zork
Are you inputting the correct time(Hr and mins) and date for
Eontimer?
RNGreporter?
DS?
How many calls you used to check your seed?
Roamers?
NPCs?
sync?
Need more data/result/information.
Yes, by definition a 32-bit seed will have 2^32 different values. But generating that many frames at once is pretty much guaranteed to cause a crash unless you have a really good computer (mine can only handle about 100 million frames at a time in the main window, and even less in Researcher).
Thanks. I'm referring to the number of frames in one seed, not the number of possible seeds. Do the frames range from 1 to 2^32? RNG Reporter won't even let me attempt to do a Time Finder search with 2^32 as my max frame; when I click "Generate," it just highlights the max frame. It will let me attempt to search with 2^32 - 1 as my max frame (although it crashes). Can someone please explain this to me?No, it's precisely 2^32. Don't forget the seed 0x0!
Anyway, RNG Reporter eats RAM for breakfast (in exchange for having a searchable list). If you want to look at frames above your crashing point, either change the Starting Frame to your crashing point (damn black magic, how does it work that quickly in a 6MB executable...), or you can use TurboRNG to instead eat up hard drive space (~300GB for all 2^32 spreads).
[/shameless plug]
On a side note, TurboRNG uses very little RAM itself. On Windows, it comes out to 4MB, while on a Mac, v1.1 uses less than 400KB IIRC.
[/shameful plug]
If you dont mind, I need your target time/date and the roamer saved location.As far as I'm aware I am
I'm using a DSi XL, and have Eontimer set to DSi
I haven't actually used any calls to verify as I'm using the Roamers verification method.
All 3 Roamers are up, Raikou, Entei and Latias
No NPC's in the room I'm in.
The Timid Nature Seed is a Sync and the Modest isn't.
The first one solved it. I didn't realize how far off from my seed I was so often. I know I'm setting the date and time right, is so much of this really complete luck?One of these
1. Your result range is too narrow(most likely the problem)
Delay +-99 sec: +-9 (widen the sec if you still cant find it or narrow the day and sec if you do)
2. You enter the wrong date and/or time on the ds or eontimer(which would throw off the result)
3. Your taking too long to check the seed and something is advancing the frame
4. There an bug with the reporter