spycat

You're more than welcome. By the way, you can vote for Bulk Edit Additional Apps in the LaunchBox 2019 New Features Poll.

You need to use a 2nd additional app to close xPadder. Example

@knightCrawler The O2EM Launcher runs games fine for me, and LaunchBox also runs them using the O2EM emulator. I'm using the O2EM emulator recommended bios o2rom.bin which is in the BIOS folder where the emulator expects it, and the Launcher also uses this bios. The images below show my emulator/launcher combined folder, and my Launcher settings.

@knightCrawler Are you talking about the Magnavox Odyssey 2 and it's O2EM emulator? It's been a while since I used the O2EM emulator, but it launched games no problem within LaunchBox. I now use MAME which works fine. Is your LaunchBox Manage Emulators Edit Emulator set to use the O2EM frontend style launcher (o2emlauncher.exe)? If so, then set it to the actual emulator (o2em.exe) instead and see how things go.

LaunchBox does not have a bug. For arcade games and software system software list emulated games, MAME's ini file needs to know their location. For software system games using direct media emulation, MAME doesn't care where the games are as long as LaunchBox knows. MAME, however, needs to know the location of any associated bios/device files.

Hi @andreasrocha both of these systems emulate fine for me via LaunchBox. When emulating software systems using direct media calls as you're doing, the LaunchBox tickbox "Use file name only without file extension or folder path" should be left clear. For software list emulation, it should be ticked. The arcade games side of things doesn't seem to mind whether it's set or not. Also, when emulating using direct media via LaunchBox, the location of the games doesn't matter to MAME once LaunchBox points to them. The games can be zipped or not and actual naming is not critical. What does matter to MAME is that it's ini file must know where the snes.zip and spectrum.zip bios files are. By the way, have you any other MAME software systems working ok via LaunchBox?

The LaunchBox Games Database forbids the uploading of images which have 3rd party watermarks or logos. I don't know if this extends to video urls as I've never seen those available when downloading images. @Jason Carr can clarify this for you.

@RULLUR and the soon to be Mrs. RULLER congratulations and enjoy your special day. LaunchBox will still be here after the honeymoon.

MAME Atari 2600 Software System Artwork File for use with the Bezel Project bezel pack View File MAME Atari 2600 Software System Artwork File for use with the Bezel Project bezel pack. Note that this is for MAME and is not compatible with RetroArch. This custom version of the Atari 2600 software system artwork file, a2600.zip contains a multi-view lay file configured to work with the Bezel Project Atari 2600 bezels pack. Any game associated with the pack can be set to display it's own bezel at launch. Games for which there are no Bezel Project bezels will open with the generic platform one. The bezels themselves are not included, due to permission from the Bezel Project team to distribute them not sought, so you will need to download the pack and drop the bezels into the artwork a2600.zip yourself. You will also need to set LaunchBox Custom Command-line Parameters to allow MAME to select the correct bezel for each game. This is explained in the download. The a2600.zip artwork file will work whether you are emulating using direct media calls (games with the long naming and a26 extension) or emulating using a software list. Once downloaded, unzip the file MAME Atari 2600.zip and read the enclosed text files. Apologies, there is a mistake in the "read me first" text file within the download. The A2600 game aspect ratio should read 8:5 and not the incorrect 5:4. I blame cheap whiskey. The lay file itself is not affected. Submitter spycat Submitted 07/12/2019 Category Platform Bezels/Overlays  

I'm not too sure if the command line parameters are oric -cass or oric1 -cass as the setname is oric1.zip But if you're launching to the BASIC screen, then try typing CLOAD"" and press Return

My computer updated to Windows 10 1903 on June 17th, followed by a Cumulative .NET Framework update for 3.5 and 4.8 for Windows 10 1903 x64 on the 18th and LaunchBox works ok.

MAME GCE Vectrex Software System Custom Artwork File View File The standard issue of the GCE Vectrex software system artwork file, vectrex.zip limits all games to a common, generic bezel. That's how MAME does software system external artwork by default. This is essentially a version of vectrex.zip that will allow each game associated with the Bezel Project GCE Vectrex pack to display it's own bezel at launch. Games that don't have a Bezel Project bezel will use the generic one. Note that this is for use with MAME itself and is not compatible with RetroArch. Once downloaded, the file MAME GCE Vectrex.zip should be unzipped. The artwork file in the download is vectrex.zip and it contains the multi-view lay file. The game bezels themselves are not included, due to permission from the Bezel Project to distribute them not sought, so you will need to download the pack and drop the bezels into the artwork vectrex.zip yourself. You will also need to set LaunchBox Custom Command-line Parameters to allow MAME to match the correct bezel for each game. This is explained in the download. The vectrex.zip artwork file will work whether you are emulating using direct media calls (games with the long naming and vec, bin, gam extensions) or emulating using a software list. Notes: The lay is a single elememt one, as the Bezel Project pngs combine the actual bezel and the vectrex game overlay into one image. Some other vectrex lays use two elements, where separate overlay and bezel images are used. When checking out the Vectrex on-line, I got the impression that the game aspect was not 3:4 but slightly wider. I couldn't come up with an agreed answer so I went with 3:4. So the game area is 810 x 1080 with an offset of 555 to centre it. If you want a wider aspect, then you need to increase the lay screen width (for all views) and reduce the X offset by half the width increase. Submitter spycat Submitted 06/08/2019 Category Platform Bezels/Overlays