SentaiBrad

Did you happen to import your games on a Beta recently? There was a bug where newly imported games would not have a path assigned to them, it was a bug. Right click a game and tell me if it has a path.

Or that, but I would love it up so it's easier to download.

Would you mind if I uploaded the intro video to our Download section?

Ah, ok then! GlupeN64 it is. Either way, N64 emulation is not great. I do now recall being some FPS hacks for their games, but for the most part it will be hard to expect 100% speed for any game regardless of the frame rate they originall ran in. If that happens to be 20, 30, 60 FPS then so be it. I assumed it was all 30 / 60, but looking back at even Starfox on SNES which ran at 14FPS, yea... That would also explain why I see N64 speed readings as VI's or Cycles and generally not an FPS reading.

To be honest, the Wikipedia scraper has a lot of issues, and has been debated on being dropped all together. I noticed that it causes issues with scraping if you import your games and have that box checked. It works ok if you edit a game after the fact, and try and choose Wikipedia for that one game, you can get some info there, but it's still not a great solution and something we added a long time ago thinking it would help. It really didn't. So I honestly don't know how much Jason will want to work on the Wikipedia Scraper unless he's removing it, and even then he has been so busy he hasn't even done that.

Yea, Nintendo is the only one I would actually "fear" in that respect. They know the power of their old games and fight that to tooth and nail.

It hasn't been covered before, so thanks for letting us know about this! There is a list of known file extensions to ignore within LaunchBox, and this isn't one of them, so it will need to be added for the next beta / release. I will let Jason know so he can add it to the list!

@Manuel Leiria If you want to take a quick video for free, you could use OBS Studio and use the record function. Record a short video of it happening and upload it to YouTube, at least if you're comfortable doing that stuff.

In the realm of the grey area we live in, this certainly rides that fine line much more than anything else I've seen in a while. In all reality, there's the possibility that we could host roms, or faciltate that connection and nothing bad ever happen to us, or it could also be that we let this slide just slightly once, and suddenly we're being sued. It could go easily in either direction, but we don't want to take that chance, we love this way too much. Jason and I talked about that at length a long time ago, we just love this too much.

Oh, I thought it was ParaLLEI that was along farther than GlupeN64, I might have confused those two. The best bet would be one of those two though.

Yea, this is another reason why I said to just grab the set. All the BIOS you'll need plus more will be in the pack. If you grabbed the games individually and then grabbed a rom pack, they could all be based on different versions or incomplete.

The way you were wanting to do it, update pack by update pack is the best way if you're gonna use CLRMAMEPro.

If LaunchBox is using relative paths (You can edit a game or emulator and if you see ../LaunchBox/, that's a relative path), then it can be moved to a new system easily. LaunchBox is fully portable, and if using relative paths it's just a lot easier. So if anything was using a full path (Which has a drive letter in it), you'd have to put those items on the same drive letter in the same path, or change their path to the new location.

I am sorry though, I do hate to be the bearer of bad news in these situations, I would love to say yes to everything. In a perfect world, we could, but if people want us to keep doing what we do, then we have to be very careful in those situations, which generally means we just can't do them.

I am saying what I said in response to someone who said they should put all of their update packs in to one folder and have CLRMAMEPro parse a single update folder and not all of them individually. My point, was if you're going to do that, it's more or less the same as dropping the update packs in manually. If you're gonna use CLRMAMEPro, might as well do it right.

If the files are named properly, all you need to do is drop them in to the Images folder. I think this tool was written for a sligtly more complicated scenario, and is a 3rd party tool written by a user. Go in to your ../LaunchBox/Images folder, find the system you are looking for, then drop these images in to the proper folders. Arcade games generally use flyers as their front box art. If the image matches the name of the game inside of LB or the name of the rom file, it should attach automatically. You may need to refresh your cache in the options and / or restart LB.

The problem with MAME games is that if you download individual roms, you don't know what version of MAME they were built for. Sometimes that wont matter, sometimes that will. At this rate, it might be easier to download a .181 rom set, MAME .181, run through the importer, then favorite the games you want out of the set, and have everything else as a bonus. Otherwise, I would say to match the same version of MAME your other PC was using, or try a few random versions and see what happens. The roms can all be from various different sets, the BIOS could be from a different set all together, etc. There's no telling. If you carried everything over exactly though... then I am little more confused as to what happened. Maybe @lordmonkus or @DOS76 know something.

Then why not just put the updates in to the main MAME Roms folder 1 by 1 and update your packs that way? That would be the same thing essentially.

A lot of older games were made this way. The standard used to always be 30 or 60, just depends on the developer. The Mupen64 core, or any N64 emulation for that matter, is beyond not perfect. The best bet though might be ParaLLEI in RetroArch. That is coming along very nicely. GLupeN64 is also coming nicely as their full re-write, but it's not there yet. You may be able to tweak your settings enough and / or brute force your way in to good frame rates on some games for a little while, but it's still not great. As for what settings to change, I actually don't know what you can do in RA to change to improve performance... Could take a look at the core settings, which show up after a core is loaded in the quick menu. That is usually where I see settings that I normally see in other emulators or the emulators each core is based on.

No, I'm fine with the emulators part, I mean the games. Even if we're not giving someone the games, we're still facilitating that connection and means we would have to store roms or use the Internet Archive to give the user a game to play. What Monkus is saying is my concern. We can't really do anything with this when copyrighted material is being passed through it. It's one thing for the user to have to supply these, it's another if the application helps in any way. This is cool for users who want this though, something on the go even. Edit: Yea, I re-read my reply and I did leave out some key words Whoops. If we devloped an emulator, that would be fine. If we developed an emulator that performed something like this, or even if we used other emulators for functions like this, that would be a big no no.

This is an extremely grey space, so no. If we developed something that emulated retro games, that would be a big no no.

If one did exist, it would be best to put it in the downloads section really, then that way it's actually backed up on our servers. There could be a thread so that people can contribute, and who ever uploads it just updates the package in our downloads.

But I just did. Move your LaunchBox install to a different location, like a different hard drive. This is a permissions error.

You could just move your LaunchBox install to a different drive, it's completely portable.

You can delete it, but it will re-cache automatically. If you're constantly adding / removing games, it's a good idea to compeltely delete it from time to time to make sure it's still as lean and mean, but the cache will re-cache regardless. There wont be any problems, and sometimes there's a reason to clear the cache, but there are also options to do this in App. Still, ther's no problem deleting the folder, but when you re-run LB, it will automatically come back. It can take a long time depending on your library, cpu and HDD, but if you leave LB open for a while it should re-cache automatically over time. When I re-cache, in a platform im working on I'll scroll through slowly for a little while, wait 5 min, come back, and past where I scrolled comes in.