Main Restorations Software Audio/Jukebox/MP3 Everything Else Buy/Sell/Trade
Project Announcements Monitor/Video GroovyMAME Merit/JVL Touchscreen Meet Up Retail Vendors
Driving & Racing Woodworking Software Support Forums Consoles Project Arcade Reviews
Automated Projects Artwork Frontend Support Forums Pinball Forum Discussion Old Boards
Raspberry Pi & Dev Board controls.dat Linux Miscellaneous Arcade Wiki Discussion Old Archives
Lightguns Arcade1Up Try the site in https mode Site News

Unread posts | New Replies | Recent posts | Rules | Chatroom | Wiki | File Repository | RSS | Submit news

  

Author Topic: Pop'n Bounce spinner configuration  (Read 1581 times)

0 Members and 1 Guest are viewing this topic.

b3atmania

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 209
  • Last login:November 25, 2005, 09:48:57 am
Pop'n Bounce spinner configuration
« on: May 13, 2003, 07:24:14 am »
I am trying to get my spinner to work with Pop'n Bounce using MAME. The game runs on NeoGeo hardware which normally only use joysticks.

If you enter the NeoGeo service menu (press F2) and go to you can find an option to set the controls to SETTING UP THE SOFT DIP -> SLOT 1 POP N BOUNCE -> CONTROLLER you will find the setting that can change JOYSTICK to PADDLE. When set to PADDLE, the bat moves irradically when pressing buttons. Maybe the game is expecting analogue (pot) spinners instead of optical spinners? My spinner works with Arkanoid and Tempest, so that can't be it.

Has anyone experienced this problem or know how to fix it?
I could just leave it configured to use joystick, but we all know ball & bat games have better playability using a spinner.

BTW, another NeoGeo game, "The Irritating Maze / Ultra Denryu Iraira Bou" supports trackball and works fine.
« Last Edit: May 13, 2003, 09:33:00 am by b3atmania »

b3atmania

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 209
  • Last login:November 25, 2005, 09:48:57 am
Re:Pop'n Bounce spinner configuration
« Reply #1 on: May 15, 2003, 11:26:16 am »

A quick follow up to my own message. The problem I described is acknowledged in the sourcecode of the NeoGeo driver. I have fixed it and have submitted the patches to the MAME development team. Hopefully it will get accepted for inclusion in a future release.