Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing/Wrong mapped keys on Xbox 360 Wireless #67

Closed
mikart143 opened this issue Nov 24, 2019 · 2 comments · Fixed by #86
Closed

Missing/Wrong mapped keys on Xbox 360 Wireless #67

mikart143 opened this issue Nov 24, 2019 · 2 comments · Fixed by #86
Labels
area-Input bug Something isn't working

Comments

@mikart143
Copy link

Summary

I noticed that some keys are not mapped correctly to names.
Button number 11 (counting from zero) is responsible for DPadUp but it s not correct. When i click DPadRight then this button is true.
There is not a a DPadLeft.

Steps to reproduce

  • Platform: Desktop
  • Framework Version: .NET Core 3
  1. First I did this
    I created from my .Net Standard 2.1 Library
  2. Then I did this
    Then I called function responsible for detecting buttons

Comments

There is list of detected buttons
First collumn is index, second current state, last is name of button

0 False A
1 False B
2 False X
3 False Y
4 False LeftBumper
5 False RightBumper
6 False Back
7 False Start
8 False Home
9 False LeftStick
10 False RightStick
11 False DPadUp
12 False DPadRight
13 False DPadDown

@mikart143 mikart143 added the bug Something isn't working label Nov 24, 2019
@mikart143 mikart143 changed the title Missing/Wrong mapped keys on Xbox 360 Wireless keys Missing/Wrong mapped keys on Xbox 360 Wireless Nov 24, 2019
@Perksey
Copy link
Member

Perksey commented Nov 24, 2019

Hi there, thanks for using Silk.NET!

I've made PR #68 to fix this problem, can you please try version 1.0.0-preview420191124.1 on the experimental feed to see if this fixes your issue?

@mikart143
Copy link
Author

mikart143 commented Nov 25, 2019

Nothing has changed. Still getting DPadRight as DPadUp. There is also no DPadLeft.
When I make ....Buttons[14].Position I am getting out of range argument. I made clean solution and rebuild but I am keeping getting error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Input bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants