05 February 2021, 20:05 | #1 |
Registered User
Join Date: Feb 2021
Location: Darlington
Age: 44
Posts: 3
|
Key Mapping Not Working On Chromebook
Hi all,
I'm using FS-UAE in Linux on Chrome OS, with Pegasus as the frontend. It runs well, smoothly, and looks great. However, when I set keymapping it doesn't seem to work. Pegasus takes all the FS-UAE config line in its own metadata file, and they all work apart from the key mapping. I've also made a config file with the same info in and tried it direct from the FS-UAE Launcher, and the key mapping doesn't work from there either. I'm aware that joypad support isn't available in Linux on Chrome OS, yet, but I would have thought the key mapping would work fine. In the Pegasus metadata file my FS-UAE launch command is as follows: launch: fs-uae --floppy-drive-0=ASI014.adf --fullscreen=1 --amiga_model=A500 --writeable_floppy_images --keyboard_key_f1 = action_key_1 --keyboard_key_f2 = action_key_2 Now from what I understand those commands should make the '1' and '2' key on my keyboard act like they were 'F1' and 'F2'. However, it doesn't work. It might be something obvious I'm missing, or may just be an issue running on Chrome OS. Anyone have any ideas? Thanks, Bobby |
05 February 2021, 20:39 | #2 |
FS-UAE Developer
Join Date: Dec 2011
Location: Førde, Norway
Age: 43
Posts: 4,043
|
You got it almost correct, except it's the other way around: With this config, you make the "F1" key on your keyboard press the "1" key on the emulated Amiga.
|
05 February 2021, 20:53 | #3 |
Registered User
Join Date: Feb 2021
Location: Darlington
Age: 44
Posts: 3
|
I've just swapped it round so it now reads:
--keyboard_key_2 = action_key_f2 That should mean when I press '2' on my physical keyboard the Amiga will see 'F2' being pressed? If thats right, it still isn't working inside the emulation. Chromebooks don't have physical Function keys, so for lauching games from an Assassins disk I'm trying to make it easier by using the regular number buttons instead. I know you don't directly support Chrome OS FrodeSolheim, so I appreciate your help. |
06 February 2021, 11:36 | #4 | |
FS-UAE Developer
Join Date: Dec 2011
Location: Førde, Norway
Age: 43
Posts: 4,043
|
Quote:
Yes, but remove the spaces around = (when specified as command line arguments), or otherwise it won't work. If it still does not work, you can make FS-UAE log what happens when you press keys, for example: Code:
FS_DEBUG_INPUT=1 fs-uae --stdout --keyboard-key-1=action_key_f1 |
|
06 February 2021, 14:36 | #5 |
Registered User
Join Date: Feb 2021
Location: Darlington
Age: 44
Posts: 3
|
That's done it! It was the spaces causing the problem.
Thanks for your help, just need to wait for Google to enable joypad support now. Again, thanks for FS-UAE and your support. Bobby |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
switch key mapping? | powrslave | support.Other | 0 | 13 February 2017 04:48 |
Dualshock 4 key mapping | Mrklaw | support.FS-UAE | 4 | 21 February 2015 13:52 |
FS-UAE (1.1) Help Key -> where?, mapping? | ManuelHH | support.FS-UAE | 14 | 14 March 2014 05:46 |
Key mapping Problems | k2uphill | project.ClassicWB | 13 | 28 February 2007 03:44 |
Key mapping | dreamkatcha | support.WinUAE | 1 | 11 June 2003 16:38 |
|
|