Post subject: BizHawk - Killer Instinct combos not working?
Joined: 5/29/2020
Posts: 6
I'm trying to do a simple TAS of Killer Instinct for the SNES (I will admit this is only my second TAS so maybe I've bitten off a bit more than I can chew). All I want the TAS to do is get to Practice Mode, select a character (currently Jago), and then demonstrate all of that character's combos. I've managed to complete the first two goals pretty easily - currently I'm looking at Jago standing in Practice Mode. The problem arising for me is that I can't get any of his combos to fire. A good portion of the combos for every character in Killer Instinct require quick movement on the D-pad, for example swiping from down to down-right to right, and I can't seem to make this work - instead of performing the combo, Jago just ducks then performs his normal attack. Does anyone know how to simulate the quick movements on the D-pad using the piano roll?
Editor, Emulator Coder, Site Developer
Joined: 5/11/2011
Posts: 1108
Location: Murka
Quick movements would be ones that are just held for fewer frames. If it's quarter circles and stuff, sometimes the games require any of the 8 cardinal directions passed to be registered, so for instance a half circle forward might (depending on game), need B, DB, D, DF, F in sequence.
Joined: 5/29/2020
Posts: 6
I've tried doing that. The problem I keep running into is that BizHawk doesn't seem to register anything past the first button press. Currently what I have is "D, DL, L" with no frames in between any of them. Do I need frames in between at all? Does BizHawk not like pushing buttons that quickly?
Editor, Emulator Coder, Site Developer
Joined: 5/11/2011
Posts: 1108
Location: Murka
Bizhawk doesn't have any limitations like that. I'm not much of a TASer, but I know that when you start getting into the nitty gritty details of frame by frame tas precise input in games, there can be a lot of surprises in what the game will and won't accept. Might check if there's a game thread on this in the snes forum?
Joined: 5/29/2020
Posts: 6
I figured it out. I keep mixing up the L and R buttons - changing the L in that sequence to a R solved the problem.