I was finally able to test the Duke Nukem test run that Dimon12321 made. Works fine on console.
Holy Father! I didn't expect it to sync at all, knowing it's unusual hardware utilization, 3D graphics and uncapped framerate, because all three FPS TAS tests I've provided are lag-sensitive.
Judging by verifications of side-scrollers, all those RNG troubles, I was convinced "When every known game can be played back, only then Duke Nukem can be played back too". Well, that feels different now.
I made a 100% low-effort TAS of Duke Nukem. In case you'd like to check it even further, here's the movie: User movie #638510452607262334
Regardless, you've influenced my TASing priorities!
TASing is like making a film: only the best takes are shown in the final movie.
I was finally able to test the Duke Nukem test run that Dimon12321 made. Works fine on console.
Holy Father! I didn't expect it to sync at all, knowing it's unusual hardware utilization, 3D graphics and uncapped framerate, because all three FPS TAS tests I've provided are lag-sensitive.
Judging by verifications of side-scrollers, all those RNG troubles, I was convinced "When every known game can be played back, only then Duke Nukem can be played back too". Well, that feels different now.
I made a 100% low-effort TAS of Duke Nukem. In case you'd like to check it even further, here's the movie: User movie #638510452607262334
Regardless, you've influenced my TASing priorities!
Unfortunately the 100% run desync in v2.1.3 because 2.1.2 used the wrong EEPROM size.
If you plan on TASing Duke Nukem or Doom, be sure to use v2.1.3 where these EEPROM issues are fixed.
Unfortunately the 100% run desync in v2.1.3 because 2.1.2 used the wrong EEPROM size.
Oh. I though EEPROM is used for game saves and high score boards only, and I didn't make a single save in my run. It goes out of sync about half way through Level 1-3.
I assume, the reason is I changed the weapon auto-switching option and the emulator wrote to the wrong part of RAM which caused extra lag frames and/or RNG change. Am I on the right track? Just a guess.
My Doom TAS of Level 1 goes out of sync when I save the game at the end on v2.1.3. More time is spent saving
TASing is like making a film: only the best takes are shown in the final movie.
Oh. I though EEPROM is used for game saves and high score boards only, and I didn't make a single save in my run. It goes out of sync about half way through Level 1-3.
I assume, the reason is I changed the weapon auto-switching option and the emulator wrote to the wrong part of RAM which caused extra lag frames and/or RNG change. Am I on the right track? Just a guess.
My Doom TAS of Level 1 goes out of sync when I save the game at the end on v2.1.3. More time is spent saving
Yes, when you change weapon to auto-switch it writes to EEPROM, and that causes the desync.
Even with the correct EEPROM size, timing can still be variable. If you want a complete run to work on console, I recommend only TASing like one level / stage past the first EEPROM access / save, then test on console to make sure timing on that particular cart matches emulator before continuing.
Or maybe for Duke Nukem its not a big deal to avoid to weapon switching thing to preserve determinism.
