...why...?I have a question for you can you use this to disable buttons Id like that option in another update I hate the L2 and R2 buttons on the new3ds
Mind posting that for everyone? my L and R buttons are broken so I'd really appreciate it!ok no need, success making remap button at last, thank for remap button method
Did you download the buildtools? They're needed to make the CIAs.Any help? trying to compile but I get an error
"
injected.s
make[1]: bannertool: Command not found
make[1]: *** [banner.bnr] Error 127
make: *** [build] Error 2
"
Not really sure what I'm doing but I think I have something of a grasp of this.
Mind posting that for everyone? my L and R buttons are broken so I'd really appreciate it!
Your first mapping is correct, but the second mapping is looking for Up+R to press up. It should bethis is the current setting for remap L to Down, and R to Up:
ldr r4, =0x40
ldr r5, =0x100
bl .button
ldr r4, =0x140
ldr r5, =0x40
bl .button
ldr r4, =0x80
ldr r5, =0x200
I found a bug while troubleshooting some other mappings which resulted in the c-pad being moved down-left any time a button was held. Have you downloaded the new codebase from GitHub?but when run the cia, input on 3ds become:
I've thought about adding this, but I just don't know how it would be possible. I would probably have to allocate some memory to keep track of button hold times, but I'm not sure if it could be done.how can i change it into:
Up = Up (when 'press' up button one time)
Up = R (when 'hold' up button)
Down = Down (when 'press' down button one time)
Down = L (when 'hold' down button)
The order in which the buttons are pressed shouldn't matter, but looking at your mappings, it looks like you have it looking for X+Up and X+Down instead of Y+Up and Y+Down.but this setting work differently, such as i have to press Up button first then follow with Y button to become Up button. how can i change it into hold Y button first then Up button to become Up button.
Alright, let's see what's going on.
Your first mapping is correct, but the second mapping is looking for Up+R to press up. It should be
Code:ldr r4, =0x80 ldr r5, =0x200
I found a bug while troubleshooting some other mappings which resulted in the c-pad being moved down-left any time a button was held. Have you downloaded the new codebase from GitHub?
I've thought about adding this, but I just don't know how it would be possible. I would probably have to allocate some memory to keep track of button hold times, but I'm not sure if it could be done.
The order in which the buttons are pressed shouldn't matter, but looking at your mappings, it looks like you have it looking for X+Up and X+Down instead of Y+Up and Y+Down.
Thanks you ! It works perfectlyDid you download the buildtools? They're needed to make the CIAs.
And what do you know, there was a bug in the c-pad code. There's a 0 missing at the end of the value at line 146 in injected.s. The repo has been updated. @Demnyx, I've tested and posted an updated version of what you had requested.
@Wishi, I've made your mapping. Let me know if it's backwards (I think I got it right).
The first file should match @neobahamut1989's build.
With the release of Luma3DS v8.0, the new Rosalina module has the InputRedirection code built in, including C-nub. I'll be trying to see if I can get any sort of mapping to work between the two processes.Is the N3DS C-nub still unmappable? I would like to map the L and R buttons to the nub if possible.
Mode3 is used on O3DS systems for extended memory games like Smash Bros. There is no "extra" functionality other than what is necessary to get it to work in extended memory mode.Which are the differences beetwen the standard mode and the 3 mode?More funcionality maybe?
The standard swap only A with B and the 3 mode?
And there is a way to swap the start/select with other buttons on preference?
Thank you for the explanationSorry for no news on this for a while, I've been super busy with school and work.
With the release of Luma3DS v8.0, the new Rosalina module has the InputRedirection code built in, including C-nub. I'll be trying to see if I can get any sort of mapping to work between the two processes.
In addition to that, I would like to modify the Rosalina module to include input remapping, and in doing so allow for an easier way to customize the mappings. I will be trying to squeeze in some work on this when I can.
Mode3 is used on O3DS systems for extended memory games like Smash Bros. There is no "extra" functionality other than what is necessary to get it to work in extended memory mode.
There is still no easy way to change button mappings without editing the code on your computer and making a new version.
Would zl and zr also be remappable or only the c nub?With the release of Luma3DS v8.0, the new Rosalina module has the InputRedirection code built in, including C-nub. I'll be trying to see if I can get any sort of mapping to work between the two processes.
In addition to that, I would like to modify the Rosalina module to include input remapping, and in doing so allow for an easier way to customize the mappings. I will be trying to squeeze in some work on this when I can.