TASEmulators / TASEmulators/BizHawk
Implement Hex Editor/RAM Watch mid-frame reads (from scanline, CRT-based consoles only, example: Game Boy) + sync Hex Editor/RAM Watch with Debugger
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
This allows you to look where the game writes a byte outside of V-Blank. Note that this would decrease peformance, so this should only work when Debugger (or Hex Editor) is open.
This also matches BGB's behavior (unfortunately, this is not a rerecording emulator, so rerecording has to be a separate request on BGB)
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 tracing the existing Debugger and Hex Editor/RAM Watch read paths for CRT-based consoles, using Game Boy as the example, and compare the timing with BGB behavior. Done should allow mid-frame reads of writes outside V-Blank, limit the performance cost to when Debugger or Hex Editor is open, and keep Hex Editor/RAM Watch synchronized with Debugger.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100