Keybinding OEMBACKSLASH not recognized when using Everest

[lucid falcon]

I use OEMBACKSLASH (located between left-shift and Z on my Swedish keyboard) for an extra jump button. It is recognized when I launch Celeste, but unrecognized when I launch Everest. I am wondering if the keycode has been renamed in some update of Everest that I just now downloaded (I just updated Everest after a few months of inactivity).

[safe maple]

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.

If you're on Everest 4501 or later, the XNA keyboard driver has been reimplemented, but you need to manually enable it yourself. This will change from opt-in in the future.

• Create an everest-env.txt file inside your Celeste folder
• Put the below inside, and save the file.

EVEREST_NEW_KEYBOARD_INPUT=1

• Open Everest.

[lucid falcon]

Thank you for the help but the problem persists. Adding --use-scancodes as a new line at the bottom of the everest-launch.txt did not allow Everest to detect me pressing the OemBackslash key or let me bind the key press. It did not break any existing binds except that it added two new grab binds (Z and V) for some reason. When I launch vanilla Celeste I can bind/unbind the key without issue. On the Swedish keyboard the OemBackslash key corresponds to the < symbol if that helps.

I also tried updating past Everest 4501 and adding the everest-env.txt document with the text EVEREST_NEW_KEYBOARD_INPUT=1 inside but I was still unable to bind the < key.