You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.
Hello, I'm a user who plays Tekken 7 with GP2040. I got an issue, where the lever is mapped to the D-Pad suddenly changed to the left analog stick during the gameplay, and I was able to confirm that both inputs were changed even by accessing the web settings. Upon confirmation, other buttons remain the same, only the binding of the lever has been changed.
The environment used is Windows 10 Pro 21H1, x64 environment, XInput mode is being used, and the game being played is Tekken 7.
The same symptom is happening quite often, and the board I'm using is a Raspberry pi pico board.
The text was updated successfully, but these errors were encountered:
We would need to know which version of the firmware you have loaded and also get some images of your setup. This reads like there may be an issue with always held buttons that are activating the shortcuts in the firmware.
As a note - This project is no longer maintained. Please check out the Community Edition project and post your issue there if it continues. The Community Edition issues section can be found here: https://github.com/OpenStickFoundation/GP2040-CE/issues
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, I'm a user who plays Tekken 7 with GP2040. I got an issue, where the lever is mapped to the D-Pad suddenly changed to the left analog stick during the gameplay, and I was able to confirm that both inputs were changed even by accessing the web settings. Upon confirmation, other buttons remain the same, only the binding of the lever has been changed.
The environment used is Windows 10 Pro 21H1, x64 environment, XInput mode is being used, and the game being played is Tekken 7.
The same symptom is happening quite often, and the board I'm using is a Raspberry pi pico board.
The text was updated successfully, but these errors were encountered: