Testing the PSMove Nav on Windows
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 528
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
In my attempts to test https://github.com/thp/psmoveapi/commit/8cc40f73e62adbb8351a0180aa779cdd546170cb version of the psmoveapi I have ran across an error. Note: version is mentioned not for being the cause of the issue but to record which version of Psmoveapi I was using.
Current Bluetooth master: USB_REQ_GET_CONFIGURATION: Input/output error
Setting master bd_addr to 4c:82:a9:2c:45:b4
USB_REQ_SET_CONFIGURATION: Input/output error
I see the message on the documentation
This is not tested at all on Windows, contributions welcome.
Is there information that I may provide to aid in the resolving of this error or is the contribution expectation a little more on the code side of things?
I noticed some dependencies were out of date so I updated them locally on my PC. IDK if I updated them fully and correctly just that the git submodule was checked out. It didn't resolve my problem and I looked no further at that time. Any insight or information including what I can provide any of you would be greatly appreciated. Sometimes simple discussion aids understanding.
For now I may dual boot a Linux install on a spare 1tb hdd I have and enjoy.
Contributor guide
No contributing guide indexed for this repository
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 reproducing the USB_REQ_GET_CONFIGURATION and USB_REQ_SET_CONFIGURATION errors on Windows with psmoveapi at commit 8cc40f73e62adbb8351a0180aa779cdd546170cb. Review the Windows-related documentation and the locally updated submodule state; the work is done when the cause is identified and a tested resolution or actionable diagnostic is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100