Bezels and Overlays
Posted: Fri Aug 10, 2018 2:27 am
I am not able to get Bezels and/or Overlays to work with Mame 078 or Advmame 106. I know that in 106 and prior, it uses a combination of PNG and .art file to tell it how to work with the overlays and bezels and screen coordinates. I know I am using the right .art and PNG file for the older 106 and prior versions of Mame. However, whenever I start a game using Advmame 106, I get a screen that looks like a series of horizontal lines. I can't really see the game and it certainly is not playable. If I remove the corresponding .art and PNG artwork, the horizontal lines are gone and the game displays and plays fine. At the minimum, I know it is reading the artwork for the game and the .art file is telling it where to find the bezel and/or overlay, screen coordinates, etc. I think it has more to do with a resolution mismatch or perhaps wrong PNG file size? If anyone has done this and can provide a step by step instruction, that would be greatly appreciated.
In Mame 078, it would appear that it is using a different format using PNG for the overlay and/or bezel and cfg files which provide instructions for how to handle the artwork and where to find the PNG file. For example, game abc.zip has a corresponding abc.zip.cfg file in the same rom directory. My problem is I think I am not pointing to the right artwork location for the PNG file. I may also be putting the .cfg file in the wrong directory. It is currently residing in the same directory as the rom file. When I start a game in Mame 078, nothing changes. No overlay, no bezel, etc. If anyone has done this and can provide a step by step instruction, that would be greatly appreciated.
I haven't tried it with FBA. Anyone have experience with this? Which format does it use .art, LAY, CFG or some other configuration?
I was successful in getting Bezels and Overlays to work with Mame 172/192 (uses LAY files). Once the game artwork is in a zip file and is in the artwork folder and you tell it where the artwork folder is in mame.ini for both 172/192, then the game loads with the Bezel/Overlay automatically and you can change the settings via the in game video control. Works as expected with one glaring problem, in games that flip (set to cocktail mode in dip switches) for sit-down cabinets with a monitor in vertical position, the game flips for the other player, however the Bezel/Overlay does not flip so while the game is oriented correctly for the second player, the bezel/overlay is upside down! Does anyone have a fix for that?
In Mame 078, it would appear that it is using a different format using PNG for the overlay and/or bezel and cfg files which provide instructions for how to handle the artwork and where to find the PNG file. For example, game abc.zip has a corresponding abc.zip.cfg file in the same rom directory. My problem is I think I am not pointing to the right artwork location for the PNG file. I may also be putting the .cfg file in the wrong directory. It is currently residing in the same directory as the rom file. When I start a game in Mame 078, nothing changes. No overlay, no bezel, etc. If anyone has done this and can provide a step by step instruction, that would be greatly appreciated.
I haven't tried it with FBA. Anyone have experience with this? Which format does it use .art, LAY, CFG or some other configuration?
I was successful in getting Bezels and Overlays to work with Mame 172/192 (uses LAY files). Once the game artwork is in a zip file and is in the artwork folder and you tell it where the artwork folder is in mame.ini for both 172/192, then the game loads with the Bezel/Overlay automatically and you can change the settings via the in game video control. Works as expected with one glaring problem, in games that flip (set to cocktail mode in dip switches) for sit-down cabinets with a monitor in vertical position, the game flips for the other player, however the Bezel/Overlay does not flip so while the game is oriented correctly for the second player, the bezel/overlay is upside down! Does anyone have a fix for that?