TASEmulators / TASEmulators/BizHawk
Add toggle to Virtual Pads for respecting AxisConstraints
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Title, i.e. to have a realistic Saturn 3D Pad stick (not that the 3D Pad definition has the constraint programmed in yet). N64 is a simpler example: clicking anywhere outside the circle should place the red dot on the circumference, at the closest value allowed by the constraint (if the toggle is enabled).
This feature would be implemented in AnalogSchema and SingleAxisSchema. Adding an "expected output range" prop in the constraint interface is required for the former to scale correctly.
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 reading AnalogSchema and SingleAxisSchema to understand how Virtual Pads apply AxisConstraints and how their output ranges are represented. Trace the constraint interface and the pad input handling, then define the toggle behavior and verify that constrained clicks map to the closest permitted value, including scaling for AnalogSchema.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100