F keys not working properly in some games

[Ender519]

I have been enjoying ScummVM to play some childhood games and I've found that the F keys in some games such as Sierra games don't seem to work properly.

I am using a Retroid Pocket 4 Pro, an Android based retro gaming console. It runs Android 13, and I am using ScummVM 2.8.0 loaded from Google Play store. I am attempting to the overlay virtual keyboard.

For example, in Space Quest III, there is a part of the game where you are in Monolith Burger and after you order your meal you have to press F5 to exit. This is also the key the game uses to save in the Esc menu. Anyway, when you press F5 on the virtual keyboard, it keeps bringing up the ScummVM save/load screen. I went into game options and saw that F5 + Left Shoulder was mapped to Game Menu. I cleared the mapping so that only Left Shoulder was mapped. F5 is not mapped to anything else, however, it will still not work and you cannot progress in the game past this point.

I am including a screenshot as well as the same game file which happens just before the problem. From loading the save game, simply walk up to the counter, and you'll see at the bottom you have to press F5 to exit. Observe, you cannot use the onscreen overlay keyboard to get past it. Please advise. Thanks

[antoniou79]

As of yet I could quickly test running PQ1 (2.0G Dos/English (EGA) from GOG) with ScummVM 2.9git, a fresh build from master HEAD, on Windows 10.

The "F5" is mapped by default to "Game Menu" (according to the keymapper, which seems to be the "generic" "default game keymap" keymapper that most engines get, if they do not explicitly have implemented some more customized engine-specific keymapper). Pressing "F5" brings up the ScummVM GMM (Global Main Menu), and thus is essentially identical with clicking "Ctrl+F5". This is the behavior with "Use Original Save/Load screens" game option unchecked.

Clearing the mapping from the Keymapper Tab, wields no difference in the behavior. It still brings up the GMM. So, I believe this matches the issue being reported in this ticket.

The other F keys seem to work (F1, F2, F3, F4) and perform game specific functions, but those are not mapped to anything via the Keymapper.

I'd say the issue is not Android specific.

Note: Checking the "Use Original Save/load screens" makes the "F5" bring up the game's original Save screen, for PQ1 at least. In that case, Ctrl+F5 still brings up the GMM (which is expected/intended).

[Ender519]

Update - it seems that upon closer inspection, the F6 key is what is needed to get past this screen. I was using a smaller screen on my retro device and it looked like F5. Once I zoomed in on a picture, I could confirm it. Pressing F6 on virtual keyboard works. Seems that this is a non-issue, can likely be closed.

[sluicebox]

Great, glad it got figured out. There are occasional conflicts between original game keys and mappings, so it was a plausible issue.

Sierra had this problem too in some games where they'd use a one-off F* key, port it to a platform whose keyboards didn't have that, and have to update the game text.