neil9000

Retroarch MAME is terrible and should never be used for current romsets. Open the mame.exe, and double click the "save config" or similar and it should create it.

You are not using retroarch, you are using mame standalone if you allowed the mame import wizard to set everything up for you.

You need to save it in two places. First when applying the shader select the "Apply shader" option, then go to save and select "Save Content Directory Preset" then back out of the shader menu and down to "Overrides" go in there and save a "Content Directory Override". I believe this is a Retroarch bug that has been around for a long time.

You also have to save a normal override too. Also you should save a "content directory override" instead, otherwise you will also have piss green game boy colour also.

Updates do not touch any of your data.

Display 2 is the TV, both are set to 1440p, both scaling at 100%, monitor is at 144Hz, TV at 120Hz, monitor is left, display is right.

Unfortunately not fixed for me, in fact the behaviour is very strange. I have a 4K OLED TV and a 1440p monitor, i have the TV as the primary monitor as that is where I want games opening, but I want Launchbox on the monitor. With the last version and this new beta it doesn't matter which display Launchbox was on when closed it always opens on the TV (primary). However if I change my primary display to the monitor then it opens there as expected, but when I move it to the TV and then close it and re-open it opens on the TV, so is remembering the display it was last on when the monitor is the primary display, but not when the TV is???????

are you using the mame.exe directly from the mamedev website as your emulator?

Nothing was broken in Launchbox to be "fixed" this was all on the retro achievements end.

A very quick google.

New release does not remember which monitor it was on when closed, it always opens on the primary display despite me always using it on my second display.

Pretty sure its them, there have been people complaining about it on the Batocera discord today too.

I have to say that i cant see any difference either, and i am on a desktop, and on a 55inch OLED to boot. It is a little darker, so i guess there could me something over the "TV" part of the image that isnt 100% transparent, but your images are so similar it really is difficult to spot any differences at all. And yeah as Headrush69 said there is dithering in the image, but thats intentional from the game artists and it will very per sprite as its "drawn" into the sprite itself usually.

Sounds like your PC is not running at at least 60Hz.

Looking at the naming id assume these are data points that theme creators can now incorporate into their themes.

There is a dedicated neogeocd retroarch core these days.

just use the latest romset with the latest version of the mame emulator 0.253 from the mame website, just delete the older romsets there is zero reason to have three different versions.

I saw these posts this morning so i tested, i have had Launchbox open for about 3 hours at this point, and RAM has been stable the whole time.

You might need to update assets in retroarch. This is a retroarch issue and not a Launchbox one though, so you would be better off asking the devs of that program for help.

As i see you are using the 13.4 beta, you would get much more eyes on your issue if you post it in the 13.4 beta thread, where all beta issues are tracked. Thanks.

Yup, the 1% agrees.

Sorry but Launchpass is nothing to do with us, in fact its the first i have even heard of it. I suggest you reach out to the developer of that program for any support.

Hmm, good eye, yeah that does seem to be the case. However here is mame, whith a missing right image and its displaying fine. I did have a scan through all platforms, but admittedly not the whole lists as some are rather large, but it was only N64 and Atomiswave that i see it with, which doesnt make a lot of sense to me.

Display issues seem mostly fixed, but i have some outlier platforms that are behaving differently for some reason. N64 still has some underlapping issues. Sammy Atomiswave too. All other systems, including my snes whhich previously had both issues are fine, so not sure why N64 and Atomiswave are behaving differently.