Moderator, Senior Ambassador, Experienced player
(898)
Joined: 9/14/2008
Posts: 1007
EZGames69 wrote:
For what it’s worth, the current all levels publication says it’s console verified, but I’m unsure how it handles the resets and if it has different rng each time.
Just like this:
python3 tastm32.py --hardreset --blank 2 --console nes --players 1,5 --transition 675 S --transition 1614 S --transition 2910 S --transition 4067 S --transition 5153 S --transition 6318 S --transition 7279 S --transition 8247 S --transition 9118 S --transition 9995 S --transition 10832 S --transition 11676 S --transition 12528 S --transition 13385 S --transition 14247 S --transition 15170 S --transition 16133 S --transition 17313 S --transition 18515 S --transition 19573 S --dpcm drmario-resets-2b.r08
For what it’s worth, the current all levels publication says it’s console verified, but I’m unsure how it handles the resets and if it has different rng each time.
Just like this:
python3 tastm32.py --hardreset --blank 2 --console nes --players 1,5 --transition 675 S --transition 1614 S --transition 2910 S --transition 4067 S --transition 5153 S --transition 6318 S --transition 7279 S --transition 8247 S --transition 9118 S --transition 9995 S --transition 10832 S --transition 11676 S --transition 12528 S --transition 13385 S --transition 14247 S --transition 15170 S --transition 16133 S --transition 17313 S --transition 18515 S --transition 19573 S --dpcm drmario-resets-2b.r08
Just to provide some context in case this is unfamiliar to anyone: What dwangoAC posted above is the command used to tell the TAStm32 replay device what inputs to replay (drmario-resets-2b.r08), and on which input "frames" a reset should occur (--transition X).
As long as the replay starts from power on (for Dr Mario), the moments the resets must occur at are consistent between attempts. Actually, that's how resets are always handled on the NES; they are initiated at predetermined frame or latch counts relative to the beginning of the replay.
