Retro808

Been quite a few posts about it. Take a look here for one.

We did not specifically say don't, we just recommended not to do so. Thing about doing it piece by piece is you do not know what version Mame that rom is for, most will work fine over the versions, but still can be an issue. Then you have to hunt down a bios or other supporting file that you many times do not know you need until you try to play the game. Also all these random sites that house roms, you never know what else they inject into the file. Getting a full Mame set from some place well known is always the best. You said you found a .202 set and downloaded it. Well if it is a full set you would have all you need for most games (roms and bios) with the exception of those games that need a CHD. Those are usually not in a romset. What games are still grayed out for example?

It does not have to be done in VS. Many theme makers code strictly in NotePad ++. It can be coded like I said and yes a plugin could do it. It likely would still be theme specific. If Jason did create a control built into BigBox the designers code could still override it. Since that piece you want to hide can vary in location (grid, column, grid span, column span) it would be hard to know what needs to be hidden. It is not named a specific piece in the code.

You cannot hide the side panel on demand. It can be auto hidden if the theme creator chooses to code it that way. I am not sure if it would be possible for Jason to make that a feature since it is how the designer coded the view in his theme.

Most Startup themes use Background images to fill the screen. So make sure in your image priorities for Background you have Fanart at the top. I would then put other full screen type images in line like Screenshots. Other smaller type images like clear logos if they get displayed tend to get blown up like you are seeing.

If all is working fine then you probably have the bios where they need to be unless I misunderstand what you mean by that. If you downloaded a full romset normally all the bios are in that set. Mame bios files can get dumped into the same folder as Mame roms. If you choose to put them elsewhere you just need to point Mame to that folder location. Launchbox only needs to know where the roms are. Unless you used the full Mame romset import option then it does not care as long as you have a full romset and Mame is already pointing to it.

Threads merged. No need for two of the same issues. In a platform you can CTRL+Click as many games as you need and then got to >Tools>Download Metadata and Media to update. You can also select a platform and go to >Tools>Audit [Platform Name] and then sort by missing media if you want (say by those games missing video) , then highlight all those games and right click then choose to run the media update option.

If you are talking about during the Startup screen that would be theme dependent (Same is usually the case with BigBox themes). What theme are you using?

Should not take much to get it working. These are the settings I have for Xenia and it runs with no issues in Launchbox. Please share the same images on yours to see if we can spot anything. Also right click a game and edit. Share images of the emulation and launcher tabs.

Yes, there are quite a few topics already on this. Here is one in particular.

There have been a few posts on this. Are you on Win7 or Win10?

Just edit a game and see. Right click a game and edit. Check the path there and check to make sure it is using the correct emulator. Also go to >Tools>Manage Emulators and confirm the emulator of choice is pointed to the correct path just to be sure.

1st and always most important question: Do your games work directly in Retroarch (without Launchbox)? If they do then we know the disconnect is in Launchbox somewhere.

Drag and Drop still works. Just do not select the option to import as Rom. Use the "None of the Above" option.

Make sure you have the box checked for "Use file name only..." in the details tab of the edit emulator screen for Final Burn Alpha setup in Launchbox. Just tested removing that check and it gives that error you mentioned.

There have been a few threads about this. Are you on Windows 7 or 10? A couple things could be the issue. Users have either needed a .Net Framework update (Win 7 mostly) and others have seen 3rd party software such as antivirus or things like Riva Tuner/MSI Afterburner causing issue with Launchbox not opening.

@Geminii23 Yeah, I would recommend not piecemeal roms. Will it work? Yes. Can it cause more issues than needed? Yes. You can easily find yourself hunting down random file after random file and nowadays getting roms from random sites means easily getting something in a file you may not want. Just look at the fact that trying to update you already are having issue. PD and the Archive work well. PD requires you to sign up and maintain a good upload-to-download ratio, but the good thing is the Mame sets usually do not count against it. Archive is just download and go. Recommendation get a full set and be done with hunting and searching.

We cannot link to sites but can recommend places like Pleasure Dome (there are some rules you need to follow to download from their site) and the Archive contains relatively new romsets. It is best to use a romset that matches the mame version, but as long as they are close you will typically be ok. I am using .209 romset with the current Mame version.

Newer Mame version will need the updated qsound file which contains that file. It is qsound_hle.zip. If you have a new full romset that file should be in there. If you are using roms pieced together than that would be your biggest issue.

Make sure the logos are named exactly as the PS1 and PS2 platforms are named in your Launchbox platform list and that they are located in the correct folder. Example: (If you named it Sony Playstation2) Folder and file name would be: \Launchbox\Images\Platforms\Sony Playstation 2\Clear Logo\Sony Playstation 2.png If those are correct and images still do not show. Go into BigBox and in the settings menu go to Options>Image Cache and then choose Refresh All Images. Your image cache may just need updating.

Edited: Looks like Neil has you covered on RA. Doubt it is a bug. It works fine on all my cabinets with RA FBA core. Nothing changed in 10.1 that should have broke the emulator. Even in the standalone FBA it works fine still. These are the same settings from last year I had that.

Always test your games first directly in the emulator before you import anything into Launchbox. That way you eliminate it either being a rom issue or an emulator one. Even if you are using an older romset and older emulator version it can still work in Launchbox. Using updated versions is always best. The roms you have now do they run directly in the emulator you are using? For Launchbox you have to make sure the emulator is setup correctly and the games run in them. Launchbox does not do any of that.

You downloaded Mame Rom's but didnt work.....Did not work how? In Launchbox? In Mame? You have to be a bit more specific than this.

This has happened before and I believe Jason fixed. So looks like it is not working again. We will let him know.

I have not added to FBA but have added to many other platforms without issue. Did you check the path to confirm it is correct? Do the roms run ok directly in the emulator?