Maximus Arcade / MAME Issue

[VegasD]

Hello,

I recently purchased a MAME cabinet, not really knowing a clue about MAME.  Over the past 3 days since it has arrived I've had a crash course learning as much as possible - but I'm still n00b.

My cab runs MAME (v118), NEOMAME, VNES, FUSION, Project64 and so on.  Because of all of these different programs I found Maximus Arcade to be a nice solution - but I'm having an issue.

I realize that MA has it's own forums, and I have posted there as well, but the traffic and knowledge of this crowd seems much more capable of helping me out - so I'm looking for your assistance if possible.

So, after a string of various issues I was finally able to get MAME 118 up and running using all the key/button configs that I needed.  Finally once I was able to do that I starting working on Maximus Arcade.  Currently I have two problems.

Problem #1
Run a game through MAME 118 and all buttons work fine.  Run the same game through Maximus Arcade and suddenly MOUSE0, MOUSE1 and MOUSE2 do not fire when hit.

This happend all of a sudden as it was working fine for a few hours this afternoon.  Here's what I've tried so far:

• Using default MA controller settings
• Deleting MA altogether and reinstalling
• Running the same game(s) outside of MA through MAME and buttons work as desired

Any idea what is causing this and how to fix it?



Problem #2
My SNES games (using VNES) don't show up on the MA (or any other) front end list.

Ever run into this before? They run fine out of VNES. Someone suggested that I check to make sure file extensions are showing in the ROM folder. I clicked all of the appropriate boxes in Windows but never actually see a .xxx extension name anywhere.

I had this exact same problem with MAME v61, which is what prompted me to update to v118.

It sounds like other people are running VNES out of a front end just fine though, so I'm assuming that program is OK.  How do I get these to show in a front end like MA?


Thanks in advance for any advice you have to offer.

[gonzo90017]

I've never heard of vnes. You should try Zsnes http://www.zsnes.com/index.php?page=files

Most frontends expect roms to be zipped. You might have to tell them what extensions the roms are.

[TheDriver]

Problem #1
Run a game through MAME 118 and all buttons work fine.  Run the same game through Maximus Arcade and suddenly MOUSE0, MOUSE1 and MOUSE2 do not fire when hit.[/b]

This happend all of a sudden as it was working fine for a few hours this afternoon.  Here's what I've tried so far:

• Using default MA controller settings
• Deleting MA altogether and reinstalling
• Running the same game(s) outside of MA through MAME and buttons work as desired

Any idea what is causing this and how to fix it?

I'm sure maximus need's the command line flag's to work mame properly.

-joy name (default: none)
              Allows joystick input. 'name' can be:
              none         - no joystick
              auto         - attempts auto detection
              standard     - normal 2 button joystick
              dual         - dual joysticks
              4button      - Stick/Pad with 4 buttons
              6button      - Stick/Pad with 6 buttons
              8button      - Stick/Pad with 8 buttons
              fspro        - CH Flightstick Pro
              wingex       - Wingman Extreme
              wingwarrior  - Wingman Warrior
              sidewinder   - Microsoft Sidewinder (up to 4)
              gamepadpro   - Gravis GamePad Pro
              grip         - Gravis GrIP
              grip4        - Gravis GrIP constrained to move only along the
                          x and y axes
              sneslpt1     - SNES pad on LPT1 (needs special hardware)
              sneslpt2     - SNES pad on LPT2 (needs special hardware)
              sneslpt3     - SNES pad on LPT3 (needs special hardware)
              psxlpt1      - PSX pad on LPT1 (needs special hardware)
              psxlpt2      - PSX pad on LPT2 (needs special hardware)
              psxlpt3      - PSX pad on LPT3 (needs special hardware)
              n64lpt1      - N64 pad on LPT1 (needs special hardware)
              n64lpt2      - N64 pad on LPT2 (needs special hardware)
              n64lpt3      - N64 pad on LPT3 (needs special hardware)
              db9lpt1      - C64/Atari/Sinclair joy via DB9 interface on LPT1
              db9lpt2      - C64/Atari/Sinclair joy via DB9 interface on LPT2
              db9lpt3      - C64/Atari/Sinclair joy via DB9 interface on LPT3
              tgxlpt1      - digital joystick via Turbografix if on LPT1
              tgxlpt2      - digital joystick via Turbografix if on LPT2
              tgxlpt3      - digital joystick via Turbografix if on LPT3

-mouse/-nomouse (default: -mouse)
              Enables/disables mouse support

Regards.

[VegasD]

Problem #1
Run a game through MAME 118 and all buttons work fine.  Run the same game through Maximus Arcade and suddenly MOUSE0, MOUSE1 and MOUSE2 do not fire when hit.[/b]

This happend all of a sudden as it was working fine for a few hours this afternoon.  Here's what I've tried so far:

• Using default MA controller settings
• Deleting MA altogether and reinstalling
• Running the same game(s) outside of MA through MAME and buttons work as desired

Any idea what is causing this and how to fix it?

I'm sure maximus need's the command line flag's to work mame properly.

-joy name (default: none)
              Allows joystick input. 'name' can be:
              none         - no joystick
              auto         - attempts auto detection
              standard     - normal 2 button joystick
              dual         - dual joysticks
              4button      - Stick/Pad with 4 buttons
              6button      - Stick/Pad with 6 buttons
              8button      - Stick/Pad with 8 buttons
              fspro        - CH Flightstick Pro
              wingex       - Wingman Extreme
              wingwarrior  - Wingman Warrior
              sidewinder   - Microsoft Sidewinder (up to 4)
              gamepadpro   - Gravis GamePad Pro
              grip         - Gravis GrIP
              grip4        - Gravis GrIP constrained to move only along the
                          x and y axes
              sneslpt1     - SNES pad on LPT1 (needs special hardware)
              sneslpt2     - SNES pad on LPT2 (needs special hardware)
              sneslpt3     - SNES pad on LPT3 (needs special hardware)
              psxlpt1      - PSX pad on LPT1 (needs special hardware)
              psxlpt2      - PSX pad on LPT2 (needs special hardware)
              psxlpt3      - PSX pad on LPT3 (needs special hardware)
              n64lpt1      - N64 pad on LPT1 (needs special hardware)
              n64lpt2      - N64 pad on LPT2 (needs special hardware)
              n64lpt3      - N64 pad on LPT3 (needs special hardware)
              db9lpt1      - C64/Atari/Sinclair joy via DB9 interface on LPT1
              db9lpt2      - C64/Atari/Sinclair joy via DB9 interface on LPT2
              db9lpt3      - C64/Atari/Sinclair joy via DB9 interface on LPT3
              tgxlpt1      - digital joystick via Turbografix if on LPT1
              tgxlpt2      - digital joystick via Turbografix if on LPT2
              tgxlpt3      - digital joystick via Turbografix if on LPT3

-mouse/-nomouse (default: -mouse)
              Enables/disables mouse support

Regards.

Thanks for the info.  I'm afraid to admit that I don't exactly understand what to do with it.  Am I supposed to copy and paste ALL of that into the command line section of MAME in Maximus Arcade?

Also, to the above poster I am in fact using ZSNES - I typo'd in my original post.  So, you are able to see ZSNES games listed in front ends?  Wonder what I'm doing wrong for that not to work?

[VegasD]

bump.  Lookin' for help if you have it please.

[VegasD]

Figured out my MAME issue - now just stuck on my SNES issue.

I'm using ZSNESw151

[VegasD]

Fixed that too!  Needed to zip the roms.

[TheDriver]

Hi, glad you got the mame issue sorted. Sorry for the late reply I have a habit of forgetting about threads I have answered in (even with reply notifications!!!)

Regards.