Ownasaurus / Ownasaurus/TAStm32

Erroneous Start press?

Open
#70 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
C
Stars
76
Forks
16
PR merge metrics
No merged PRs in 30d

Description

Years ago, DwangoAC reported occasions where there was an extra start press at the beginning of a replay. Perhaps on the first frame? Perhaps it was when the console was already on while a reply was loaded? Ideally, someone could reproduce this and fix it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported replay-start conditions: the first frame and loading a replay while the console is already on. Trace the replay startup path to identify when the extra Start press occurs; done means reproducing the original behavior, preventing the erroneous press, and verifying normal replay startup.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.