Not to sound harsh, lol, it's just that not being able to map my buttons was the only thing bugging me and wanted it working prior to an official release, but I'd rather see improvements to the sound/vsync than to custom configs. If I hadn't shared here, I probably wouldn't develop it any further. It actually was even before when keymapping was broken. So where does a developer begin their plan of attack whilst retaining features? Oh, and as a user, I want a unicorn splash screen tooįor me, the program is pretty awesome. At least maybe I'm jumping to conclusions because I'm constantly jumping between systems, I don't know if everyone else is, and I believe Rgui has the ability to save configs per core, but Cascades looks to have been programmed to handle and perhaps override that with one user-friendly solution. My Playstation's layout is different than my Game Boy's layout.
Snes's Y and B are where I want Nes's B and A to be. when I play Sega, I want three buttons in a row. I'm like, sweet, this is perfect! Then I'm going to say, well wait a minute. Now,as a user of the program myself, suddenly I'm imagining the next release brings out the ability to save my custom keymap. Thankfully it can be changed now after however much time went by without it working, albeit with a bit of a workaround on this developing program, having to do it each time. Azerty by default is going to appear irregular for the directional buttons based on that keypad layout, but I didn't edit anything special for any particular device it was put in programming by someone else. I felt bad that azerty and qwertz couldn't use their keypads after I announced button mapping was working on my device, but unfortunately none of us, qwerty included, can save their mapping.
#SNES EMULATORS CUSTOM KEYBINDS UPDATE#
Yes but you can edit it as you did for the qwerties!The last update I posted was to put us on the same page. I didn't change the bindings as everyone's going to have their own preference and I imagine there are some that have been using and are accustomed to that pre-programmed map with it being the standard until key-mapping could be changed. It sets the button map to the one that is actually written into the program. I think what it's doing is discovering all controllers, rescanning, and re-setting the button map on each open. It will not remember custom input button mappings and is not something that bothers me really enough to want to change but I'll probably take a look at it. All BB10 RetroArch versions that I've tried have had problems with official 10.3.0.x os on my Passport and crashing on launch, some less than others, but running fine after that. The program is built, I didn't make it, for the 10.2 os. If anyone's wondering, "BlackBerry Q Keypad" is just the name that was put into the program when the Q devices were likely the only BB10 phones with physical keypads.