Neric Posted March 17 Posted March 17 Hello, I just installed Launchbox (v. 13.20) for MAME v. 275 and imported the roms and the bezels. This is what I get on my Windows 11 with 1920x1080 screen. What exactly do I have to do it fix this? Quote
dragon57 Posted March 17 Posted March 17 While the TV surround can cause a very slight clipping if you don't use a shader to match the round corners like CRT-GEOM (the intent of that TV surround), what you are seeing is way more than you should have. What does your lay file look like for this game? Here is mine. <!-- bezel.lay --> <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> Quote
EJS83616 Posted Tuesday at 12:14 PM Posted Tuesday at 12:14 PM I am having the same issue, running the same version of LaunchBox (13.20). As I look at it, I think the problem is not with the bezel/overlay, but with the game screen itself because it appears stretched beneath the bezel/overlay. When I launch the game directly from MAME without a bezel/overlay, it’s not stretched. This also seems to be the case in the screenshots provided by Neric and dragon57. Is there a way to turn off the game screen stretching when using the bezel/overlays in LaunchBox? Thanks in advance for any help with this. Quote
JoeViking245 Posted Tuesday at 12:40 PM Posted Tuesday at 12:40 PM 19 minutes ago, EJS83616 said: I am having the same issue, running the same version of LaunchBox (13.20). As I look at it, I think the problem is not with the bezel/overlay, but with the game screen itself because it appears stretched beneath the bezel/overlay. When I launch the game directly from MAME without a bezel/overlay, it’s not stretched. This also seems to be the case in the screenshots provided by Neric and dragon57. Is there a way to turn off the game screen stretching when using the bezel/overlays in LaunchBox? Thanks in advance for any help with this. They lay file does affect the games' screen size within the bezel. When you're not using the bezel/overlay, the lay file isn't being read, thus [it's] not adjusting the game-screen size. That said, when you have LaunchBox install MAME for you, it adds into the Command-line Parameters -artwork_crop. You can try removing that (if it's in there) and see if it fixes it. Also, did you compare your lay file contents with what @dragon57 showed [for vertical games only]? 1 Quote
EJS83616 Posted Tuesday at 07:12 PM Posted Tuesday at 07:12 PM Deleting the command-line parameter didn’t solve the problem. I can check the lay file, but I have no idea where to find it. Can you please point me to it? I appreciate your help with this. Thank you! Quote
JoeViking245 Posted Tuesday at 07:52 PM Posted Tuesday at 07:52 PM 37 minutes ago, EJS83616 said: Deleting the command-line parameter didn’t solve the problem. I can check the lay file, but I have no idea where to find it. Can you please point me to it? I appreciate your help with this. Thank you! ../MAME/artwork/[rom_name]/default.lay i.e. D:\MAME\artwork\dkong\Default.lay 1 Quote
EJS83616 Posted Tuesday at 11:13 PM Posted Tuesday at 11:13 PM I was able to compare the lay parameters and they differ. Unlike dragon57’s, bounds left=“2” and right=“14”. I’m not sure how this happened because I imported the full MAME romper using the LaunchBox wizard, which then imported and set up MAME and all the artwork, videos, bezels, etc. Quote
JoeViking245 Posted Tuesday at 11:23 PM Posted Tuesday at 11:23 PM 9 minutes ago, EJS83616 said: I was able to compare the lay parameters and they differ. Unlike dragon57’s, bounds left=“2” and right=“14”. I’m not sure how this happened because I imported the full MAME romper using the LaunchBox wizard, which then imported and set up MAME and all the artwork, videos, bezels, etc. aka: 13.21-beta 1 Quote
EJS83616 Posted Wednesday at 03:42 PM Posted Wednesday at 03:42 PM Bingo! It now works just fine. Thanks for your help with this; I didn’t realize this was a bug that needed to be fixed (and instead thought I somehow wasn’t configuring this correctly). 1 Quote
Maxpower1509 Posted 8 hours ago Posted 8 hours ago Mine still has it after putting on 13.21beta3. Quote
CalmDown Posted 4 hours ago Posted 4 hours ago I have the same issue. As a temp workaround, I use the Bezel Project Windows installer. Works a treat > https://github.com/thebezelproject/BezelProject-Windows Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.