faeran

Locking this topic, as it's old, showing out-of-date windows and your comment doesn't look to be related to the OP. I will say that if you click on core and there's nothing in that dropdown, it means that you either don't have your application path set properly to point to your RetroArch program, or that you have yet to download any cores inside of RetroArch. If you need help with your specific issue, I'd suggest opening up a new post with as much detailed info about it as possible.

If your not up on the latest beta, can you update and let me know if you are still seeing this?

I'm not 100% certain, but it's likely caused by the way we are parsing the RetroArch config file to determine your save file location. We will look into this and see if there's anything we can do here for a future update.

Thanks for the list. PC Games, make sure the scrape as value is set to Windows. The system is designed to not auto-import any Windows games. MS-DOS - set the scrape as value to MS-DOS. The system is designed to not auto-import any MS-DOS games. TeknoParrot, American Laser Games, Daphne, Singe2, MESiCAxLive, MAME, set the scrape as value to Arcade. The system is designed to not auto-import any Arcade games. Future Pinball - make sure you set the scrape as value to Pinball. The system is designed to not auto-import any Pinball games. Out of your list, I believe WoW Action Max is the only platform we'd have to exclude automatically, so thanks for that. In the meantime, if you are up on the latest beta, you can exclude this platform under its Edit Platform window.

Thanks for the input. We already have support for Emulation Station type bulk imports as mentioned in my first post. You just drop your ROMS for all your platforms into the LaunchBox\Games folder and you are good to go. Advanced users can use symlinks and other methods as I listed in my first post to utilize this system for files in their custom locations, but it would be much better to have our own UI for bulk imports. This is why we want to provide an interface inside of LaunchBox to handle this eventually, where you point to a root folder and we attempt to identify what platforms you have. As you mentioned, with people being able to organize their ROMs into any folders and folder names as they like, this can pose complications. Like all apps, including the ones you mentioned, things become a heck of a lot easier when you follow their naming structures, and falls apart when you want to go against the apps programming. Therefore, the UI would have to provide feedback for which platforms we automatically identify and which ones that we don't, and then provide users per-platform solutions to correct them. There are many ways people are organizing their ROMs, you are following one, we've had our own for the last 10 years or so, another app will do it different, and every individual person will also do it slightly different. Whatever UI bulk solution we come up with, we want to make sure it's as seamless as possible for as many people as possible, knowing full well we can't appease everyone.

Thanks for the feedback. Things to note: PC Games are already excluded automatically from this system (Arcade games are too as well) Most Xbox 360 games are simply iso files, which are recommended. We know about GoD format, and we are still working through what to do about these types which obviously complicates matters In the meantime, the beta (and subsequently version 13.17) has a way to disable the auto-import feature on a per-platform basis. We are going through every problematic platform that we know about, and at the moment that list is fairly small at this point. If anyone know about any other problematic platforms, we'd love to hear about them so we can take a stab at making them work with our automated system.

If you would like to go through some configuration discussion send me a PM and I'll see what I can do for you.

The manual scan does not work with PS Vita, at least not well. The only current method of importing your PS Vita games is through the auto scan option, which does work well. I just ran a test on Atari 7800, and that seemed fine. If your still running your ROMs across a network, I'm guessing that might be the cause of what you are seeing.

The error points to your account maxing out the RetroAchievement API endpoint. Basically RetroAchievement's API saying "stop bugging us already!". Beta 5 should help with this scenario. If you can confirm that would be nice.

Beta 5 is out with the following changes: Improvement: Save Management support added for .MCR save files with RetroArch's supported Sony PlayStation cores Fixed: Adjusted download priorities from the Edit Game window for more accurate regional media selection from the LaunchBox Games Database Fixed: Resolved potential crashes associated with RetroAchievement when your account's API usage reaches its limit on the RetroAchievement endpoint

Only time we've ever seen this is due to some kind of permissions issue with that folder. Can you delete the contents plugins folder while LaunchBox is closed and open LaunchBox again and see if that helps.

See if this works for you. Edit a game, go into the Emulation section, click on "Use Custom Command-line Parameters", and input the command line parameters that point to the specific game id you'd like to launch. This command line should overwrite the emulator one.

Thanks for the reminder here, we've had this on our list for quite a while. We will look into deleting it, however, if I'm remembering correctly, I'm pretty sure deleting the platform is the easy part. How that then effects all version of LaunchBox might be the harder part. We could end up causing unnecessary crashes with the program if we aren't careful.

Based on this response, Google Drive is most likely your issue. See what happens if you completely shut down Google Drive. Do you still receive access denied issues?

I wish there was more I could add to this. I ran some tests and can only confirm that this is not a systemic issue with the app. Based on what you are saying it sounds more like Windows is having a hard time in saving the new file LaunchBox is trying to create. There are many reasons this could happen on a user's computer. The most notable ones would be that you have another program that is fighting for access to the same files/folders as LaunchBox is (eg. something like a cloud sync program, or hard drive backup program), or there's some kind of permission issues going on with your hard drive. That's probably where I would start my investigation if I was having this issue.

Sounds like you changed your view to Text List View. If you have a Change View hotkey, click that and choose a different view. If you don't have a Change View hotkey, go into the options, under either Keyboard or Controller mappings and assign a key.

Not all platforms have media available, but a lot of them come with at least a clear logo. I just checked both Atari ST and Commodore Amiga and they each came with a Clear Logo, and a Platform Icon. If both those platforms came up with nothing, it's possible there's something incorrectly configured in your platform's metadata. Can you Edit these platforms and take screenshots of what you see?

For anyone having this issue on 13.16 that has confirmed that it's related to RetroAchievements, it would be interesting to hear if the beta solves this for you or not.

Sorry to hear you feel that way, and while I don't want to get too into it, based on the usage numbers for this version vs. issues that came out of 13.16, this release probably falls somewhere in the middle. However, I can understand that when something is specifically affecting you, it can definitely be frustrating. Based in our widespread testing, we aren't seeing the numbers you are across many builds, but we are always looking to improve where we can. If you would like to send me your data files through a PM, I can take a look and see if there's anything to gather from them. I believe you are talking about different things here, and I do want to keep this beta thread on topic. We read everything and address everything that we can, triage between client issues, server issues, and user issues, and address the ones that we can control. This happens every round, which I'm sure you are aware, since we do address many of the things you have brought up in the past that are within our control to do so (we've even solved many of your user specific configuration woes as well). Alright, back on topic. We do have another beta coming that will address more issues that have come up in the beta, so expect a beta 5 before the end of the week.

Thanks that helps. It's a MAME specific issue, we'll look into it. This is most likely due to the scan that needs to happen for the save management feature. After a the scan completes CPU usage drops down.

This should be fixed in the beta. If you would like to update to the beta and let us know in the beta thread that confirmation would be helpful. Outside of that, you can wait for the official release.

Thanks, this is fixed internally and will be available in the next update. Tested a bunch of scenarios but we are not seeing this happening. Can you name a few different games for a specific system that this is happening for you? Our first assumption is that this might be more related to your data files, but we can look into it further once you provide some more information here.

Beta 4 is out with the following changes: Improvement: Non-Steam Windows games now have the ability to scrape Steam media Fixed: Updating MAME using the Full Set Import wizard now accurately updates the emulator name and folder to match the imported version Fixed: The "Create Playlist" option in the quick filter now functions correctly when viewing "All" games on the sidebar Fixed: The BIOS window for RetroArch should no longer take Dolphin and PCSX2 cores into consideration Fixed: RetroAchievement scanning now correctly indicates whether achievements are available for a given game (introduced in beta 3) Fixed: The per-platform auto-import disable option now functions as intended (introduced in beta 3) Fixed: Navigation issues within the playlist section of Big Box have been addressed. This should resolve instances where game details were not updating correctly during navigation (introduced in beta 2) This should fix the issue users were seeing with RetroAchievement badges and playlists from the previous beta. The issue ended up being that the new end points we were given to use from the RA team was insufficient to deduce which games had achievements and instead were indicating which games had a game profile on the RetroAchievement website. We are now using the old endpoint for this, but there is a caching improvement that we've left in.

Glad you figured it out. The dev of that theme would have to create a game discovery center view for it. Since it doesn't have one it falls back to the default theme view.

Hey Wolvez. We'll take a look into it. It's quite possible there were changes on the YT side which broke something. Whatever the case, if it's not working, we'll see what we can do about fixing it up for next release.