The goal of this run is to complete the game as fast as possible in "Champion" skill mode with the character Shadow. It includes the Overkills, Sudden Deaths, and two Cinekills.
Hello and welcome to TASVideos, Entity!
I would love to give you my opinion on this TAS, but I unfortunately can't get it to sync, it always fails at the second round of the Larcen fight. I should also mention that this TAS was done on Bizhawk 2.11, not 2.11.1 like the submission page says.
As far as the gameplay goes that I was able to see, I would like to hear from you if this TAS is meant as a playaround. The notes say that the goal is to beat the game as fast as possible but also mentions Overkills, Sudden Deaths, and Cinekills. These sequences look cool but obviously waste time and would only make sense to be shown in some kind of playaround. And that would be fine, as it is an established category on our site after all, especially for fighting games.
Current project: Gex 3 any%
Paused: Gex 64 any%
There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
Hello, andypanther!
Thanks for informing me. I apologize for the inconvenience regarding the emulator version. Actually, I did this TAS on BizHawk 2.11, but some time after the run was complete, I switched to the latest version of the emulator, and when I checked the run before submission, I didn't encounter any issues. I accidentally wrote the wrong version while submitting.
Regarding the inclusion of the mentioned death sequences, yes, this run is indeed a "playaround".
I checked the run again, but there were no sync issues at all. If you can, please share the details about how it fails, I mean if the character moves randomly or doesn't move at all.
For what it's worth, I don't think Bizhawk 2.11 and 2.11.1 have sync differences for this particular run, as there have been no updates affecting the Sega CD core in 2.11.1.
The desync becomes clearly visible after Shadow grabs Larcen on the left side of the screen on frame 33027. After that, she starts taking hits.
Current project: Gex 3 any%
Paused: Gex 64 any%
There are no N64 emulators. Just SM64 emulators with hacky support for all the other games.
I have uploaded an updated movie here:
https://tasvideos.org/UserFiles/Info/639258607496255826
The problem you described is probably due to the emulator failing to read the inputs properly. The game has a strange way of receiving inputs; in some stages the player character responds only to inputs on even-numbered frames, and in other stages, on odd-numbered frames. In the Larcen stage the game responded to inputs given on even-numbered frames, and the input when Shadow grabs Larcen was on frame 33026. I have made minor changes in the update considering the possibility that the game somehow broke the pattern.
Joined: 4/24/2026
Posts: 31
Location: International
Entity wrote:
I have uploaded an updated movie here:
https://tasvideos.org/UserFiles/Info/639258607496255826
The problem you described is probably due to the emulator failing to read the inputs properly. The game has a strange way of receiving inputs; in some stages the player character responds only to inputs on even-numbered frames, and in other stages, on odd-numbered frames. In the Larcen stage the game responded to inputs given on even-numbered frames, and the input when Shadow grabs Larcen was on frame 33026. I have made minor changes in the update considering the possibility that the game somehow broke the pattern.
If in some stages, the character only responds to even-numbered inputs while in others, the character only responds to odd-numbered inputs, then it could be something RNG related. This could definitely be dependent on CPU cycles, and from what I'm seeing, this game's RNG is stage dependent. However, your movie file should be able to save such CPU cycles.
Check if there are any lag frames that could affect input. Generally, input cannot be registered in such frames. However, some frames don't alternate between lag and non-lag every frame. Chances are, there could have been a specific spot where for example there was two lag frames instead of one. If lag frame positions can be adjusted, then you can intentionally slow down in a stage or pause buffer.
Also, I have seen that you haven't explained much of this TAS. In fact, you haven't explained much at all. Generally, it's recommended that you explain your TAS as much as you could within the submission notes. That way both the viewers and judges can understand your TAS.
