TASEmulators / TASEmulators/BizHawk
[Feature Req.] Expose "may rely on uninitialised RAM" hint to TASers
Open
Nobody has claimed this yet.
App: EmuHawk
Open to design proposals only
Request: Feature/Enhancement
Tool: TAStudio
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Ideas for implementations:
- Internally, keep track of which memory addresses are initialised by the game, and set a flag on the movie if an uninitialised value is read.
- Mesen has something like this (source for NES)
- Distribute an ext. tool which plays a given movie, using memory hooks to detect when uninitialised RAM is read.
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 reviewing the linked Mesen NES debugger source, especially Core/NES/Debugger/NesDebugger.cpp around lines 202-208, and compare the two proposed approaches: tracking initialized memory in BizHawk or using an external movie-playing tool with memory hooks. Done means a movie or tool reliably reports when gameplay reads uninitialized RAM.
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