Views: 31,786,005 Homepage | Main | Rules/FAQ | Memberlist | Active users | Last posts | Calendar | Stats | Online users | Search 06-15-26 08:55 AM
Guest:

0 users reading Programming my own Turbo Button | 1 bot

Main - Development - Programming my own Turbo Button Hide post layouts | New reply


epicaaron29
Posted on 08-08-25 09:31 PM Link | #7860
Hi everybody!

MelonDS is a pretty fantastic emulator. I personally use a fork created for the Switch, turning my handheld into... another handheld basically.

I use the release by catlover007 from this GBAtemp thread: https://gbatemp.net/threads/melonds-for-switch-continuation.570021/

The thing is, I really need a turbo button to play Pokemon games without going crazy. Mashing A to get through simple battles is so annoying! I just want a simple config to make it so holding down one of the back triggers automatically inputs the A button a couple times a second.

Unless someone here would be willing to program that for me (and I'd pay $$ too!), I figure I need to get into the muck myself and code the functionality myself.

So, does anyone have advice on where to begin? Is there a Discord/IRC to chat with developer minded people about this? I've only ever programmed in Java and JS before, so I'd need to learn how to set up the dev environment and recompile the code etc from scratch.

Thank you for your time and consideration.

(I'm serious about the payment thing btw, I'd pay like $50 for a mappable set of turbo buttons for the switch fork, so many hours of gameplay)

Arisotura
Posted on 08-23-25 03:07 PM Link | #7897
hey, sorry to respond late

you'd want to look in EmuInstanceInput.cpp, in EmuInstance::inputProcess()

would be the best place to implement a turbo button imo

____________________
Kuribo64


Main - Development - Programming my own Turbo Button Hide post layouts | New reply

Page rendered in 0.085 seconds. (2048KB of memory used)
MySQL - queries: 29, rows: 82/82, time: 0.072 seconds.
[powered by Acmlm] Acmlmboard 2.064 (2018-07-20)
© 2005-2008 Acmlm, Xkeeper, blackhole89 et al.