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: mame0148 not using cfg game input  (Read 954 times)

0 Members and 1 Guest are viewing this topic.

zanna5910

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 181
  • Last login:August 05, 2024, 10:37:36 am
  • I want to build my own arcade controls!
mame0148 not using cfg game input
« on: September 25, 2013, 10:12:07 am »
I compiled a version of mame 0148 last night and upgraded to it.  I copied all my 0144 folders to my new 148 folder, including my cfg directory.  It seems mame is not using my custom game key input though.  It does show bezels from the cfgs, but all the game input seems to be reverted to default.  LEDBlinky correctly shows the correct buttons as defined by the cfg.

Has anyone experienced this?  I have always been able to copy the cfg directory over and have it read the cfg files.  Anyone know how to get mame to read my cfg inputs so I dont have to remap all the games?
« Last Edit: September 25, 2013, 08:54:06 pm by zanna5910 »

zanna5910

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 181
  • Last login:August 05, 2024, 10:37:36 am
  • I want to build my own arcade controls!
Re: mame0148 not using cfg game input
« Reply #1 on: September 26, 2013, 12:26:32 am »
Well, turns out mame wasn't happy with the input --> port --> tag parameter in my CFG's that 0144 was creating and was stripping out all game input data in 0148.

To fix this, you have to add a colon character in the tag field, see the example below:

You will see a line like this:
Code: [Select]
<port tag="IN0" type="P1_BUTTON1" mask="16" defvalue="0">
Change it to this:
Code: [Select]
<port tag=":IN0" type="P1_BUTTON1" mask="16" defvalue="0">
All these tags will be different in your files, you just have to add the : where necessary.

Notice the colon character in the tag parameter.  I have no clue why this is required now.  Can anyone shed any light on this?