Error "A key appears to be stuck"

Flame Flame Questions
1

I installed the 2022 trial last night and all day today I’ve been receiving the error “A key appears to be stuck. Please release COMMAND to continue”.

I’m on a brand new iMac 27", Apple Magic Keyboard, brand new Wacom Intuos Pro, MacOS Big Sur 11.2.3

Any ideas how to make this go away?

2

UGH. That was fixed in the 2021 release. By any chance, are you only seeing it when you command-tab to another app and then back into flame?

3

Yes, I’ve been using command-tab to go between tutorials and the application.

4

I’ll fire up 2022 on my Mac and see if I see it. I don’t recall seeing during the beta.

5

I am getting “a key appears to be stuck, Please release PRINT to continue”. I’ve tried toggling that and all other keys and nothing seems to release it. I’m on Flame 2021.2. Any suggestions short of rebooting?

6

image (1)
image (1)896×286 14.9 KB

Was this a known issue? Was it fixed in later releases? Not a big problem when sitting in front of the mac but it can be debilitating when using remote access. Using Flame 2020.3.1. Mac OSX 10.15.7

Some Flame 2019 on OS X Mac users have found that Wacom driver 6.3.22-3 does not exhibit this problem.

The driver has improved the situation but the error message still pops up. It then quickly disappears. Progress.

1 Like
7

A reboot seemed to fix it and it never came back, super strange.

1 Like
8

I get this every single time I tab out of flame and go back.
No matter the version of flame at least a few different Wacom drivers(2 diff tablets), diff versions of MacOS and previously OSX, trash can to 2019 MacPro etc, etc, etc…. Lol

9

Same here, and also when using a mac to teradici in a linux (currently with a pc keyboard, but also true with mac apple keyboard if i remember correctly)

11

Same here. Flame 2022 on iMac Pro macOS 10.15.7 and 11.5.

12

Does anyone have the stuck key problem in 2023?

13

Yes, on a quite regular basis. But only after I Cmd-Tab into another app and then come back to Flame. On Mac OS. Simple click on Cmd solves it for me. A bit of a drag, but all things considered not a big issue.

1 Like
14

I normally find that WD-40 fixes it.

1 Like
15

I don’t have WD-40 on my keyboard. Is it F19? :wink:

1 Like
16

In all seriousness, there is probably an easy explanation…

All keyboards generate separate ‘press’ and ‘release’ events for each keystroke. Flame must be receiving the ‘press’ event from the Cmd-Tab, but by the time you press Tab the OS has taken the keyboard focus away and thus Flame never sees the ‘Tab’ or the ‘release’ event of the Cmd key. Hence it determines after some timeout that the key must be stuck.

There should be some way to distinguish that they lost keyboard focus, or have the Cmd press timeout after 5s or some reasonable amount of time, as a Cmd-Tab means you’re likely spending extended time in some other app before coming back to Flame.

2 Likes
17

Im actually getting that randomly in 2024, Mac Studio, Mac keyboard, no Adobe software on my machine either

18

I do a lot of remote connections, even in-house, from Linux to Mac over AnyDesk, from Mac to Mac with ScreenSharing, and usually experience this is when remoting between systems…