TASEmulators / TASEmulators/BizHawk
PicoDrive potentially marking polling frames as non-polling
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Initially reported by Tuffcracker on Discord.
so in knuckles chaotix, i've been working on special stages for the best ending, and i've noticed that some frames are not being considered "lag frames," they're labelled green in TAStudio but the game doesn't register any inputs on that frame, is that just a picodrive issue? it's also kind of the same vice versa where a frame that's red in TAStudio does actually register a button input on that frame (most noticable in speed slider in my any% tas)
[...]
i actually have a couple examples in the improved movie i submitted a bit ago, there's a spot on frame #74772 where i press up to throw mighty up and right, and the game registers that i pressed up on the frame
[Knuckles' Chaotix any imp.bk2]
frame #87017 has the same thing, where i press up and the game registers that
frame #87249 has a similar thing, but the game also registers that i hit A to deduct 10 rings from my counter
frame #96980 has the same thing except i'm throwing him downwards
i'm able to jump on those frames as well, i don't know if it means anything that they're all in speed slider and maybe there's something with the zone itself? as far as i remember i don't think i encountered anything like this in the other zones as well
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported frames from the attached Knuckles' Chaotix movie in TAStudio with the PicoDrive core. Compare the polling-frame classification against the inputs the game registers at frames 74772, 87017, 87249, and 96980. Done means the classification consistently reflects whether inputs are registered on those frames.
Written by the indexing model from the issue text.
Assessment
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100