Lordmonkus

@MorningStarGG are you downloading fanart when you scrape ? Fanart can sometimes be quite large and the more popular systems with the more popular games and characters often have a lot of fanart, Mario and Final Fantasy for example have large and rabid fanbases and in turn large amounts of fanart. Also the more popular systems and games have more screenshots and other media to go along with it.

Scraping times vary from system to system and what art you choose to download. Something like the SNES for example if will take longer than most, especially if you tell it to download all the fanart. Also keep in mind that high speed internet and downloading a big file does not translate directly to scraping, every game and image type is a new call to the server which is what ends up being the choke point. It's like the difference of you telling someone one time to do one large task or having to tell someone to do a million little tasks but having to stop and tell them what the next task is once the previous one is done.

Whatever happened it's a simple fix at least and not a big deal.

Yeah, this is a weird one because it's something that changed in MameUI at some point but not sure when. I have used an older version (154 i think it was) and it was perfectly fine without moving the mame.ini file. I have long since switched to the command line version and manually generate my mame.ini file in the main folder where the executable is located.

They don't unfortunately.

My advice would be to just get a new and updated rom set and Mame build to go along with it, that would be the simplest.

I have never seen that error and a quick Google search turns up nothing. My first and only guess at this point in time would be something with the version of Mame you are using not liking the idea of launching a rom via command line. That is purely a guess though.

Double check your Associated Platforms window of your Retroarch emulator, I just checked mine and the Sega Dreamcast platform was missing though I am not sure if it was there or not. I have been messing around with a fresh and clean install so it is quite possible I didn't have it setup to use RA. It could be a bug though that removed the Sega Dreamcast Associated Platform for Retroarch, it would be strange if it was but I have seen weirder.

This is your analog stick on the controller not being centered. Works perfectly fine for me. Check your settings in LB, make sure your associated platform is correct and you have the proper core selected.

Hiya PittStone and welcome to the forums, I saw the name and remembered you did some PCM tracks for some games.

Not at the moment.

Captain Commando MSU has been released and Sunset Riders is coming so here is some covers for them. https://www.zeldix.net/t1749-captain-commando

In the edit emulator window for an emulator check the Associated Platforms tab and make sure your platform names match there. Honestly, you used a 3rd party program that makes changes to the xml files, any number of things could have been changed or broken.

Without knowing what sort of errors you are getting or if you are getting any at all check your rom paths, emulators, platform names and all the other usuals.

Yeah the old way of doing it was the way you described it but it has since been changed so you can have multiple videos and if you have more than 1 video in the folder it will pick a random one at startup.

Make a folder in your /launchbox/videos folder called Startup and put your video in there, it can be called whatever you want.

You can try restoring your xml files from the backups folder. Anytime you use a 3rd party program you should make backups or test it out on a tester install of LB so if anything does go wrong it won't hurt.

Assault Suit Valken released. https://www.zeldix.net/t1747-assault-suits-valken

It just depends on what you want to emulate, I find Retroarch and its cores to cover the mainstream 8,16 and 32 bit systems pretty much perfectly. Once you get outside of that into the later generations and some of the more off the beaten path systems things can get a bit more tricky.

If you set your /system folder path yourself then you may have to re-point it after moving but if you didn't set it and it's just the default it should be fine. Videos and themes are fine in the folder. Fonts though I am not sure at all. For PS1 the Beetle PSX core is a great emulator and highly recommended. Beetle PSX HW is worth trying out but I don't use it myself, I find it can be a bit glitchy with some games. For Dreamcast the Reicast core has come a long ways but still not at the top or worth using over Redream or Demul yet. Don't get too hung up on having "only one emulator" installed, there are times when a stand alone is superior enough to the RA core that it makes the RA not quite worth using. Not sure what you mean here, if you have working bios don't update them unless you have to. Nothing I can think of other than making sure that if your paths change you may have to make some changes in LB or your emulator settings, it just depends on a case by case basis. I would only suggest that you have a backup good working setup while you make the migration and test things out. That way if something goes horribly wrong you got something to fall back on.

As of beta 10, which just came out, we now have game controller features in .Next. There's only two items left, which should go fairly quickly: Custom spacing options (with # of text lines too) Mouse cursor popup options I should be able to implement these this week, and then we'll look to put out the next official release. Assuming all goes as expected, the 8.4 release will be the last official release to contain OG LaunchBox.

Nope, cause it works for me.

I don't know, if your roms aren't changing location it should just work, puNES doesn't require any special command line parameters.

Load it once, Alt + Enter once to make it fullscreen it, close it with Alt + F4, the next time you run it through LB it will load it in fullscreen. You will want to use this AHK script to close it out though: $Esc:: { Process, Close, {{{StartupEXE}}} }

The answer to this was on the first page, 3rd post.