tepid oasis
I've recently changed to "Core" version since I was getting to many OutOfMemory errors, but in Core the keybinds I use for TASing seem to be interpretated differently. I use the 2 keys after "0", and in the stable vers it detects them fine (photo 1), but in Core, the first one works fine (although is interpretated as another key), but the second one is directly not registered when I try to use it (photo 2). What could be the solution here?
sand scarab
That's an FNA issue, by default it doesn't pick up some keys
You can add --use-scancodes to everest-launch.txt to change that, however that might screw up old bindings
sand scarab
Yeah, that should fix it
You'll probably have to rebind your keys though
tepid oasis
You can add `--use-scancodes` to everest-launch.txt to change that, however that...
where's the txt located?
sand scarab
In the same folder as the Celeste executable
simple island
where's the txt located?
it's where your celeste is insta- 🐌
tepid oasis
it worked :)
It's registers them differently, but luckily it didn't screw up anything
simple island
i'l mark this as resolved 
tepid oasis
ok no wait sorry
I've just noticed
it's super buggy
It changes the keybinds randomly
huh...
nvm I think I can live with it lol
slate plover
It changes the keybinds randomly
can you be more specific about that?
tepid oasis
Yeah wait me one second
So, to sum up:
Keybinds work fine. However, as soon as I put a breakpoint or a savestate anywhere, frame advance stops working, and "Start/Stop" and "Pause/Resume" swap keybinds. This only seems to go back to normal when I minimize Celeste and open it again, but it breaks every time I put a new breakpoint.
In the video, at the start everything works fine until I put a breakpoint