Auto Fire Support

Issue #191 new
Former user created an issue

Original issue 191 created by tmor81 on 2011-10-10T17:06:05.000Z:

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

Comments (10)

  1. Former user Account Deleted
    • changed status to open

    Comment # 1 originally posted by ekeeke31 on 2011-10-11T08:55:24.000Z:

    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.

  2. Former user Account Deleted

    Comment # 3 originally posted by tmor81 on 2011-10-12T16:14:46.000Z:

    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.

  3. Former user Account Deleted

    Comment # 4 originally posted by tmor81 on 2011-10-12T16:19:44.000Z:

    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.

  4. Former user Account Deleted

    Comment # 5 originally posted by cheatfreak47 on 2012-04-13T07:02:19.000Z:

    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.

  5. Former user Account Deleted

    Comment # 7 originally posted by ekeeke31 on 2013-06-03T19:12:07.000Z:

    issue #339 has been merged into this issue.

  6. Former user Account Deleted

    Comment # 8 originally posted by johnny.teresopolis on 2013-07-27T14:59:07.000Z:

    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 :)

  7. Former user Account Deleted

    Comment # 9 originally posted by pbmysteryforyou on 2015-01-04T05:37:51.000Z:

    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.

  8. Log in to comment