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
Describe the bug
In the new MCU version(318 updated in 2024/08/30),
└ the M1, M2 buttons are recognized only as M1.
└ can't combination keys with M1, M2 buttons
└ can't recognize long click Quicktool button and ACSE button
These bugs appear once ACSE is run.
To Reproduce
Steps to reproduce the behavior:
Go to Hotkeys
Click on 'Press to define hotkey input'
Click M1 or M2 Button
Only recognize as M1
Expected behavior
A clear and concise description of what you expected to happen.
└ I would like to add an option to recognize M1 and M2 respectively, and an option to recognize both buttons with the same key.
Screenshots
If applicable, add screenshots to help explain your problem.
└ not needed
Logs file
If applicable, add logs file stored in your install location, logs folder.
└ not needed
The text was updated successfully, but these errors were encountered:
kmjg6357
changed the title
There is a problem with specifying a Hotkey in the new MCU(318) of the ROG ALLY. (not X)
There is a problem with specifying a Hotkey in the new MCU(318) of the ROG ALLY when once ACSE is run. (not X)
Aug 31, 2024
Device manufacturer
Device model
ASUS ROG ALLY (not X)
Handheld Companion Version
0.21.5.4
Describe the bug
In the new MCU version(318 updated in 2024/08/30),
└ the M1, M2 buttons are recognized only as M1.
└ can't combination keys with M1, M2 buttons
└ can't recognize long click Quicktool button and ACSE button
These bugs appear once ACSE is run.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
└ I would like to add an option to recognize M1 and M2 respectively, and an option to recognize both buttons with the same key.
Screenshots
If applicable, add screenshots to help explain your problem.
└ not needed
Logs file
If applicable, add logs file stored in your install location, logs folder.
└ not needed
The text was updated successfully, but these errors were encountered: