Project Key Mapping

WheezyE

New member
RL Member
Thanks. :)

I agree that the final keymap should encompass even emu's that RetroArch runs, so that RocketLauncher wouldn't be dependent on RetroArch for its final universal keymap. But for the time-being, it would be nice to eliminate 22 of the 125 emulators we need to map by letting RetroArch handle keys for its 22 emu's.

Yeah, those function key examples were just to illustrate the concept. In reality, I believe there's weirder key combo's that cause issues in some emu's (can't think of them off the top of my head though).
 
Last edited:

solipsist1234

New member
RL Member
Perhaps i'm thinking all of this wrong, but as far as i understand this thread, we are now testing every emulator, and every key possible to see which keys can be used universally on every emulator.

Isn't it easier to do the following.
You just let every emulator keep the default keybindings. No changes there.
You remap these keybindings with an Autohotkey Script. (like, A::H), to a universal profile. The emulator won't know the difference, and since we are using default keybindings there's no compatibility issue.
Then with Xpadder, you map the buttons to the universal profile.
 

IceLancer

New member
RL Member
Guys u could just cut all keybinds from project profile and start from scratch
Project64.sc3
that is the file ,just empty it and u can make ur binds they way u see fit.
I have escape working properly even

4003,123,0,0,0,4,1,0
4003,123,0,0,0,2,1,0
4006,27,0,0,0,4,1,0
4006,27,0,0,0,2,1,0
4006,27,0,0,0,1,1,0
4156,120,0,0,0,4,1,0
4156,120,0,0,0,2,1,0
4158,116,0,0,0,4,1,0
4158,116,0,0,0,2,1,0
4172,115,0,0,0,4,1,0
4172,115,0,0,0,2,1,0
4173,13,0,1,0,4,1,0
4173,13,0,1,0,2,1,0
4184,9,0,0,0,4,1,0
4184,9,0,0,0,2,1,0
4185,9,1,0,0,4,1,0
4185,9,1,0,0,2,1,0
 
Top