Bezel Project .lay files for MAME vertical games have incorrect "settings" when downloaded on 31 MARCH 2025

[nicolainuke]

Today I installed MAME0.276 merged set and downloaded bezels through the Import MAME Full Set wizard. The .lay files for vertical games (ie. 1942 and A.P.B.) contain incorrect settings which affects the aspect ratio and position on the screen. See below;

<mamelayout version="2">
  <element name="bezel">
    <image file="bezel.png" />
  </element>
  <view name="Bezel Artwork">
    <bezel element="bezel">
      <bounds left="0" top="0" right="16" bottom="9" />
    </bezel>
    <screen index="0">
      <bounds left="2" top="0" right="14" bottom="9" />
    </screen>
  </view>
</mamelayout>

 

I reverted to the bezel files from my back-up dated 15 FEB 2025 and now the games display the correct aspect ratio and position. See below for correct info;

<mamelayout version="2">
  <element name="bezel">
    <image file="bezel.png" />
  </element>
  <view name="Bezel Artwork">
    <element ref="bezel">
      <bounds left="0" top="0" right="16" bottom="9" />
    </element>
    <screen index="0">
      <bounds left="4.625" top="0" right="11.375" bottom="9" />
    </screen>
  </view>
</mamelayout>

 

I have not verified all vertical game .lay files, but I imagine there is an issue at the source (github) ?

 

[dragon57]

Not at the source. The Bezel Project doesn't pull lay files for MAME roms itself, but calculates those on the fly as native MAME bezels are installed. There must be a glitch in LB somewhere.

[C-Beats]

10 hours ago, dragon57 said:

Not at the source. The Bezel Project doesn't pull lay files for MAME roms itself, but calculates those on the fly as native MAME bezels are installed. There must be a glitch in LB somewhere.

This is related to a change made by the Bezel Project. We used a file they had to determine which games were vertical vs horizontal and file the lay file appropriately. Last month they moved to a new file system to determine those things and removed the file we utilized in the process. Next beta release has a correction to this.