sundogak

If you have auto import on (see snap below) then my suggestion is to delete the PS3 platform and re-add as there were changes in how PS3 and Vita games were imported a few versions back. LB now uses the emulator itself to tell what games are to be imported assuming auto import is on. If auto import is not on or you do not use it then I would delete only the game entry that is having issues and re-add manually. Assuming you have auto import on then do as follows: Create backup of your data just in case. Right click on platform and select delete. Most of the time, if you wait a few minutes, LB will reimport the platform and games. Note it takes the game names directly from RPCS3 so can get some titles you may have to fix to match to LB DB. If for some reason auto import doesn't re-add the platform then can add by going to Tools, Manage, Platforms, and selecting add For PS3 and Vita you need to make sure your roms folder for that platform is pointing to an empty directory (not where you eboot.bin files are) as LB uses the emulator entries. If point to your PS3 folder with files it will duplicate and add things again in addition to auto import. In my case below my "Games\Sony Playstation 3" folder has nothing in it (I use separate drive/folder) but auto import did its thing and added whatever was in RPCS3 outside LB. For the folks at beginning of thread who had the issue with the decryption error that is coming directly from RPCS3 and not LB. Likely that means LB is pointing to wrong eboot file that wasn't decrypted so double check via RPCS3 directly the path to the file that is working. This is especially the case if you had a PS3 setup prior to the auto import feature being added and then turned auto import on as it can create some odd errors with PS3 prior setups. Thus, the re-adding platform and letting LB auto import do its stuff may fix issues there. LB has nothing to do with decryption otherwise.

As long as USB 3.0 or higher and speaking about a spinning HDD at 7,200 or 5,400 rpm then your internal and external HDD will be (roughly) the same speed. The HDD becomes the choke point for speed, not the USB 3.0 or SATA III interface. If go to SSD then which interface you use for full throughput matters. For USB connection just make sure using a good USB 3.0 cable that is certified as such.

Atom cassettes are not supported by MAME at this point. You can look at the HASH directory and look at the atom.xml and says "<software name="GAME NAME" supported="no">" in entries in the list. Also can use this site: http://adb.arcadeitalia.net/dettaglio_mess.php?software_name=backgamm&software_list=atom_cass&search_id=2 Also this thread is useful for cass usage (MAME standalone not RA):

@BigBearPoetThis is an issue across all emulation for CD-i as the digital video cartridge hardware has not been emulated. Not likely to be resolved anytime soon as specs for DVC are sparse. List of CD-i programs that need DVC to run.

Glad figured issue. But also in the "Ugh nothing ever simple" ..........the use of %romfilename% will break RA's "Content Directory" overrides if using them. As RA doesn't seem to be "smart" enough to parse the MAME.ini it used to launch the program (odd). Will have to do a bit more playing around but if use Content level overrides you have to stick with the %romfile% variable. You can see how RA sees it if go to Information and once running will revert to Core Overrides.

@coliver33 My guess at this point is that spacing in path is causing issues when LB parses command. Particularly because it is double space and likely some escaping issue and LB missing a "space" so from RA view doesn't know what to launch. Although I know you said it works outside of LB, we are now dealing with 4 levels of stuff to deal with 1) LB command, RA, MAME, and MAME Software List all of which have their oddities and make difficult to troubleshoot where things are going wrong. With SL, simple is best on paths. At any rate could try two things to check above with particular focus on that "(Merged)" path being double space. Under your MAME SL level directory make a simple directory name (say software) and copy the ..software\archimedes\3dtanks.zip, point LB to it and see if that works. If so then that double space is issue and likely good to know for future as may cause other glitches. Likely "better" solution. LB added new variables within last several months (which haven't bothered to try as don't mess with RA if works!). The %romfilename% strips out path and extension which for MAME SL is actually the preferred way even within MAME standalone as MAME only needs to know the game name not anything else (as takes from XML/INI data). You also get advantage of MAME using the XML data. If do it this way then SHOULD take care of any spacing issues as you are not sending anything from LB to RA other than file name (no extension or path). As you said RA works fine out side of LB then in theory the double space aspect should not come into play from LB view. "aa310 -bios 200 -flop \"%romfilename%\"" In example above with zip you used it would then look like this to RA incoming: aa310 -bios 200 -flop 3dtanks You keep the RA setup as before as far as check boxes as still need quotes stripped other than what we explicitly put in. I tried this and works as well on my setup with %romfilename% and launches 3dtanks. Note: edited slightly to delete the "-flop1" to "flop" as if using this method the XML will parse to correct drive.

@coliver33A couple additional things. It looks like they deprecated that Mame.opt option of "boot from CLI" so wouldn't worry about that line (used to need that so not sure what they did there). One thing I noticed is you are pointing LB to Retroarch two folder layers deep. Was that intended to have Retroarch inside another RA folder? LB needs to point to same setup EXE as what you are using outside of LB. In your MAME RA INI above you show RA path one level down (as normal) so you should be pointing to that exe. Likely that is part of problem as the MAME system files in RA don't match.

2) allows rom paths outside RA System directory, specifically to a normal MAME install path.

1) Yes, it works for me. RA with MAME standard core: 2) Using the base MAME core you don't need to move anything around from standard install of MAME arcade and MAME software lists. Bios files remain as for normal MAME. So you don't need to move the bios into System folder for RA. 3) MAME.ini for RA in system directory doesn't looks consistent. Should just point to standard MAME arcade ROMs folder and standard MAME software list set. If have CHDs separate then those as well. Example: 4) Then on your MAME options file for RA should have this which for SL the red boxes are key: Using above you can keep a normal MAME set and also use for RA. Because of the an issue/coding glitch you have to have updated copies of HASH XMLs and Samples within the MAME RA system folder (won't work pointing to MAME install) even though the intent of the RA "MAME_PATHS_ENABLE" was to be able to use all MAME normal paths. But at least for ROM MAME paths they can reside outside RA folder structure.

Shows in the database and shows in local LB DB as well. Make sure your local DB copy is current. Force an update via Tools, Download, Force Update Games DB. Note there is lag from time accepted and posted in online version and packaged up for local DB copies.

No, it is only within LB as it is just an additional launcher from LB view. The actual RA install is not modified (nor should be). Edit with snap: both point to same install only difference is what LB is told to send as commands.

The main issue is doesn't appear you added the variable to append the rom file. For MAME and RA the following setup works. Note I make a separate RA core entry specifically for anything in the former MESS (or Software List ) category as they are treated differently than arcade and avoids messing up your arcade setup. This also assumes you have copied your MAME XML files and they correspond to the core version. Make sure entry has "remove quotes" checked. Append the %romfile% variable to your command which tells LB to take whatever was imported as the rom file and append to command line. It will also follow the check boxes above as to how parses command line. Note double quotes like this example for Atari 5200. "a5200 -cart \"%romfile%\""

What does your Changes Status in Moderation panel show? If accepted then likely just lag on approval to packaging into DB. If denied (or still pending review) then that is your answer as to why not in DB. You don't say what platform but there is a "Universe" game in Windows platform.

No, don't move anything around. Your MAME setup and Software List sets need to all be working before using the scripts. You can test your MAME setup outside LB which helps identify issues as can see the command window as shown below: Assumptions on using below test line: 1) you are launching command window in MAME root directory outside of LB 2) using Gold Mine as a test game 3) your LUA file is in directory ...\MAME\scripts\mtx_cass.lua mame mtx512 goldmine -autoboot_delay 1 -autoboot_script scripts/mtx_cass.lua If doesn't work in command line won't work in LB. The command errors will likely give you insight on issue. A few possible reasons to double check if errors in command above (see snaps below): If the command above works and launched game then likely means you had setup MAME within LB using auto setup so you will need to alter the path in LB to include your Software List directory rompath or there is some specific issue with naming in LB. Helpful then if you have screen shots of your LB setup to help troubleshoot (MAME emulator settings, example game entry settings). If command doesn't work then likely one of these: your MAME.ini isn't pointing to your directory where your Software List files are located and set in the "rompath" entry in the INI file. This should point to the root Software folder. It will be the folder that contains: ...\MAME\software\mtx_cass\goldmine.zip for purpose of test above. you don't have a complete MAME roms Arcade set and/or the MAME files are not named properly as they will have the bios and needed files to run the MTX emulation you do not have a correct/current set of XML files in your MAME Hash directory: ..\MAME\hash\mtx_cass.xml you haven't downloaded the Software List Mame set which is separate and an addon to the MAME rom arcade files set (need both sets).