PCSX ReARMed Troubleshooting Multitap
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 346
- Forks
- 860
- Avg merge
- 5d 16h
- Merged PRs (30d)
- 7
Description
Describe the bug
this old issue has nothing to do with latest pcsx_reamed. this is related to long standing issue that is related to Koro Koro Nin and has been fixed already. Current input problems are easily remedied if Multitap1 and 2 are set to none or disabled. Input type selectors are now moved where it should be, that is Settings > Input > Port Controls
Originally posted by @negativeExponent in https://github.com/libretro/pcsx_rearmed/issues/182#issuecomment-733992125
Expected behavior/changes
We need a troubleshooting entry to suggest to end users to try disabling multitap if the controls aren't working.
Additional context
N/A
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
Locate the PCSX ReARMed troubleshooting documentation in this repository and read the surrounding entries to determine the appropriate placement. Add guidance for users whose controls are not working to try disabling Multitap1 and Multitap2, then verify the entry matches the existing documentation style.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100