Welcome to Spike has to explain like 2 different things.
Rerecord count.
13 frames slower than RTA?
Yes.
Now it's still up for debate (seriously,
it's a 25fps cam footage, that has whack RTA timing, even my frame count can be wrong, I still know it's slower than RTA) but, libTAS doesn't like holding down the space button in my case with this game, as one very specific instance is slower. Pulling out the sword.
Now it's not the first time where one, or the other (Ruffle) has
actually caused an issue in my case where in the future I
pushed something out faster thanks to better emulation (and tool usage for DSYP's case).
I confirmed outside of libTAS that the version of Ruffle used is capable of holding a button.
The premise of the game
You have one button that you must hold press at every instance that you can, and because this is a TAS and because of the issue above these are pressed at their earliest instances.
Future Improvements
Holding Space (better tool compatibility, unless I dumbed).
eien86: A handful of questions needs to be answer before accepting this submission.
- Is this really a game or a movie that does not advance until you press space? well, at least some sections of the game are dependent on you pressing space on time so that clearly puts this into the game category.
- Does it make sense to even TAS this. I'd argue yes, if for nothing else, for the reason that it seems to have had a decent speedrun scene behind it.
- Is it optimal? Seems like this movie is barely slower than the fastest RTA speedrun. However that speedrun is rather problematic in that it was recorded by a 19 century toaster and the timer is questionable. In addition, the difference is miniscule. And finally, the emulator seems to have problems with the inputs that seem to lead to a faster solution (keep space pressed). I think these are sufficient reasons to dismiss this as a problem.
In summary, I don't see a reason why this movie cannot be accepted to standard.
Encoder: remember to use '--no-gui' when launching ruffle
