#Unbindable keys in latest Core version

8 messages · Page 1 of 1 (latest)

robust chasm
#

Hii, a few of my keys such as \ / . ' ] [ - don't seem to be recognized by the game anymore, the issue is that 3 of them are grab demo and lcj which are basically essential. i'm playing with an azerty keyboard and i tried with both azerty and qwerty and i can't bind these keys to anything anymore, and since that's a whole region of the keyboard that i can no longer use it's pretty hard to resolve to just switching up binds (i tried installing Legacy back and the binds worked with it so i'm guessing it has to do with the latest Core version)
Got any solutions that i could use ? or is it a bug that i'll be waiting to be fixed ? (no pressure i can wait all the time needed)

frank pawn
#

i think you can just add --use-scancodes to the end in everest-launch.txt

#

where is that? click on browse on the bottom left corner, click on browse local files, and look for everest-launch.txt

tough fossil
#

I'm having the exact same problem and --use-scancodes doesn't work 😔

frank pawn
#

you'll need to rebind your settings i believe

dry joltBOT
#

For some people certain keys will not be picked up by FNA Celeste / Everest.
To fix this you need to use the --use-scancodes launch option, which can be done by:

  • Going to Olympus and clicking the "manage" button on the installations window (bottom left side).
  • Click the browse button (far right side) - This will open your celeste folder, which contains your everest-launch.txt.
  • Add --use-scancodes as a new line at the bottom of the everest-launch.txt.
    This will break existing binds, however will allow Celeste to detect buttons that would otherwise be ignored.
tough fossil
frank pawn
#

@muted echo snip_confused