Auto Fire Support

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Play any game within the emulator obvioulsy
2.
3.

What is the expected output? What do you see instead?

An option for Autofire would be nice

What version of the emulator are you using (official, SVN revision,...)?

v 1.6.0


Please provide any additional information below (Video settings, Console
region,...)

There are quite a few games on the MD that would benefit greatly from having an 
autofire support, I was wondering if this would be something you would consider 
implementing?

Thanks for creating the best Mega Drive emulator I've ever used, it's superbly 
accurate on a CRT in RGB at 240p. Many thanks

Original issue reported on code.google.com by [email protected] on 10 Oct 2011 at 5:06

[GoogleCodeExporter]

Yes, I already thought about that since official controllers with auto-fire 
indeed existed and *should* be emulated. I'm keeping this on the TODO list 
until I find a nice way to implement it, as it requires additional keys to 
switch auto-fire ON/OFF (for up to 6 buttons), maybe configurable speed as well 
if I want to exactly mimic the original ones.

Problem is actually not to figure how this can be emulated but how it can be 
designed in a nice way for end users.

Original comment by [email protected] on 11 Oct 2011 at 8:55

• Changed state: Accepted
• Added labels: InputEmulation, Priority-Medium, Type-Enhancement

[GoogleCodeExporter]

Original comment by [email protected] on 11 Oct 2011 at 8:55

• Changed title: Auto Fire Support
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

That's great news that it's already something you thought of and on the "to do" 
list. I think having the "select" button (on the Classic Controller Pro) turn 
the auto fire on/off would be perfectly useable, just a suggestion. On some 
other emulators elsewhere such as FBA XXX Pro on Xbox it is implemented on the 
right analogue stick (push to the right) to switch between slow/fast/off in 
three cycles. This would also be quite useable I think? 

Anyway thanks again, your hard work on this emulator is really appreciated.

Original comment by [email protected] on 12 Oct 2011 at 4:14

[GoogleCodeExporter]

Of course the suggestion above doesn't take into consideration the possibility 
of autofire for individual buttons, maybe a toggle system from the menu would 
be good? I see how it's difficult deciding which way would be best.

Original comment by [email protected] on 12 Oct 2011 at 4:19

[GoogleCodeExporter]

A lot of Genesis controllers I had all had a turbo switch, A "Normal Control or 
Turbo Control" kind of thing (because having 12 buttons on one controller face 
would be ridiculous) So a mapping option for a turbo switch toggle could work. 

Original comment by cheatfreak47 on 13 Apr 2012 at 7:02

[GoogleCodeExporter]

Original comment by [email protected] on 9 Oct 2012 at 11:30

• Changed state: Standby

[GoogleCodeExporter]

Issue 339 has been merged into this issue.

Original comment by [email protected] on 3 Jun 2013 at 7:12

[GoogleCodeExporter]

The 3 button original arcade stick for Genesis had the ability to enable 
auto-fire for individual buttons as well as adjusting the overall speed for all 
buttons. This came in handy when whipping the crap out of Phelios :)

Original comment by [email protected] on 27 Jul 2013 at 2:59

[GoogleCodeExporter]

If you're still looking into this;

One option is to be able to go to a menu option while in the middle of a game 
and toggle individual autofires. Another is having one button for general 
autofire for all buttons that you would press at the same time as other buttons 
to activate autofire for all button presses for as long as it's being held 
down. You could go down the middle road and have some combination of these two. 
So, it's not really necessary to have rapid fire setups for 6 buttons.

Love your work.

Original comment by [email protected] on 4 Jan 2015 at 5:37