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
Hi!
After I connected my physical Bluetooth keyboard to my Android TV box, I've faced the following issues with Fuse core:
Keys Q and W don't work at all on my physical keyboard. Even in Game focus mode.
When I push left physical shift it always opens a virtual keyboard, instead of Shift key functionality. There is almost no sense to open a virtual keyboard when a physical one is connected.
These bugs make usage of this core with a keyboard impossible.
I'm using RetroArch 1.19.1
The text was updated successfully, but these errors were encountered:
idealogica
changed the title
Physical keyboard adaptation
Physical keyboard support
Sep 15, 2024
"There are some conflicts in the way the input devices interact because of the use of the physical keyboard keys as joystick buttons. For a good gaming experience, set the user device types as follows:
For joystick games: Set user 1 to a joystick type. Optionally, set user 2 to another joystick type (local cooperative games). Set user 3 to none. This way, you can use L1 as RETURN, R1 as SPACE, and SELECT to bring the embedded keyboard.
For keyboard games: Set users 1 and 2 to none, and user 3 to Sinclair Keyboard. You won't have any joystick and the embedded keyboard won't work, but the entire physical keyboard will be available for you to type in those text adventure commands.
If you set a joystick along with the keyboard, the joystick will work just fine except for the bindings to RETURN and SPACE, and the keyboard won't register the keys assigned to the Cursor joystick, or to the L1 and R1 buttons for all other joystick types."
Hi!
After I connected my physical Bluetooth keyboard to my Android TV box, I've faced the following issues with Fuse core:
These bugs make usage of this core with a keyboard impossible.
I'm using RetroArch 1.19.1
The text was updated successfully, but these errors were encountered: