faeran

It's possible it's always been like this. Hard to say, but we'll look into it. For your first one there, it's possible that's how it's always worked. If your list doesn't contain a game with the letter you have landed on, the game it remains on is the one that came before it. It's also possible you may be experiencing some lag with it, causing some errors with where you are landing, but I just did a quick test on my slow mechanical hard drive build across a number of themes, but things seem to be working as expected. Your second point is also as expected. It populates itself first with either recently added games or recently modified (I can't remember which one at this moment), to make sure something appears there right away. Then your recently played games will quickly take over. Thanks for the reports.

Thanks for the report. I know we have one dev that has the original Odin Pro, and the Odin 2 Pro, but hasn't experienced this issue. What happens if, while inside of a game's view, you click on the top-right menu option and download all missing media? Do you still see crashing when you navigate around that view?

Interesting that you are receiving these crashes on a Samsung device. Although I've never used the Fold, I've used about 4-5 different Samsung phones and tablets and have never experienced a crash like this before using them. Leads me to rhetorically ask what could be different with the Fold in their software. It's definitely not the images or the performance loading them into the app, your device is more than enough for that. For example, I also heavily test with a Retroid Pocket 2 plus and haven't experienced a crash on that either. I'm hoping that the next beta will shed some light on this issue. Once the next beta comes out (ETA yet to be determined), the next time you crash with it, we'll receive the crash report and see if there's anything in there that may explain what you are seeing. In the meantime, can you use a theme like Pure and see if you get a crash while navigating around?

Thanks for the input. The next beta will include some better backend tools for us to hopefully track this stuff better. Let's wait for that to come out and then the next time you crash we'll get a report for it that will hopefully clue us into what's going on.

Can you give us more details about your display, the resolution, the scaling, or anything else you can think of that might be out of the ordinary with your setup. Thanks. We were able to reproduce that navigation bug and we'll get it fixed up. As far as why you are not seeing any Achievement information, that's still unclear. You could potentially try and reset your RetroAchievement webAPI, then update it in LaunchBox and see if that changes anything for you. I did a few tests but aren't seeing anything out of the ordinary with regards to the auto-pop system. We also haven't touched this system in a very long time. Can you open up a separate thread and show your exact playlist rules, what games you are expecting to see, and what games you are seeing instead. I believe this is something that's always been the case when it comes to missing folder locations. Can you add your 2 cents to this ticket so we can keep track of it: https://bitbucket.org/jasondavidcarr/launchbox/issues/8030/hard-crash-while-using-platform-edit Interesting feedback. Between the two betas nothing was actually changed code-wise when it comes to the RetroAchievement integration, so my best guess is that their API may have been getting hit harder the second time you tested with beta 5. Good to hear about the Discovery Center.

Just tested this on the latest experimental build, using the default settings in LaunchBox, but the emulator paused just fine. In LaunchBox, you can edit the CEMU emulator, navigate to the Pause Screen section and make sure you have "Suspend Emulator Process While Paused" and see if that helps. I'm also not sure if CEMU itself has an option to suspend gameplay when not in focus or another setting like that. Maybe they do. I've never had Big Box continue to operate after launching an emulator, so unfortunately, can't help you there at the moment.

Beta 5 is out with some further fixes to this morning's beta: Improvement: The new Xbox login will now automatically attempt to re-authenticate you when your token has expired Fixed: Button mappings not working when navigating a manuals from the Pause Menu Fixed: Incorrect RetroAchievement header in LaunchBox's Default theme's expanded overlay Fixed: Crash caused in Big Box's Platform Categories section, when entering into a category using certain themes We are hoping that this brings us close to a release candidate here, with an official release pending shortly after. All feedback with this beta is greatly appreciated.

Thanks. There will be a huge change with Beta 2, although not related to scrapping. Curious, when it crashes for you, are you letting LaunchBox handle scrapping while you navigate, or did you run the "Download All Missing Media" option?

Thanks @Jackdefjam. We'll look into these. Good news on RetroAchievements, and glad you are enjoying the Game Discovery Center.

Thanks @Sbaby. While it's not related to this thread, it looks like the reason you are seeing this is due to a recent update of Chromium inside of LaunchBox we did in 13.9 beta 1. We'll have this fixed before official release of 13.9.

Hi Everyone, Beta 4 is out now with the final changes to the Game Discovery Center, including more dynamic lists and the last edits to the theme files (including video support). The theme files are now ready for any curious theme dev to explore. We also turned back on RetroAchievements and so far things look good with it. It would be beneficial for any RetroAchievement enthusiast to test this beta and make sure things are working well on their end. Changelog: Improvement: A myriad of changes to the Game Discovery Center to make it even better, including video support Fixed: RetroAchievements API is back up and the existing functionality has been re-enabled within LaunchBox and Big Box Fixed: (No-SubGenre) Genre Sidebar filter now shows the correct counts in LaunchBox Fixed: Added more logic to help with those pesky Xbox auto-import errors Fixed: In the Big Box Default theme, the "View Game Details" text binding will no longer show if already in the Game Details menu

Thanks. I tried to recreate your issue with Watara Supervision, but in my tests they imported and played just fine. I'm also glad scrapping was better for you, however, that's interesting since we haven't changed anything with that in this beta. Love the requests, but if you don't want them getting lost in a beta feedback thread, you may want to open up an official request, top menu here under HELP & SUPPORT > REQUEST A FEATURE Nothing was adjusted in this beta with regards to importing or scraping games. You may want to open a separate thread where you can get proper support with more information about your device and circumstances. We were unable to recreate this internally. What device are you using? This beta hasn't changed any of this code, so that's a curious thing. You'll want to open a separate thread where proper troubleshooting can take place. Don't forget to list your device, Android version, and anything else about LaunchBox that may be useful. I'll try and reply in that thread when I get some time. Thanks for reaching out to the Redream team. It's true that Scoped Storage complicates matters. It requires a Frontend to use a very specific file manager by Google that's not really controller friendly (the emulator itself also has to use it). Since scoped storage became a thing, a lot of emulators have built in frontend support into their emulators, essentially bypassing all those complicated steps for Frontends to go through to make launching into the emulators a possibility. Some emulators haven't yet done that. I'm guessing Redream is one of them, although I haven't tested it in a while. It's not out of the realm of possibility that we go through the process and get that file manager working inside of LaunchBox. It wouldn't be the most ideal solution for the user with the navigation challenges inherent with it, but unless the emulators themselves introduce specific frontend support, it may be our only option. We will have internal discussions about it, but it may take some time before a decision is made on this. The best I can do here with more transparency is explain what we do. Whenever there's a report of a bug, we go through a lot of testing across our many devices to see if anything can be recreated. If not, there's little we can do to move forward. There's nothing that has been reported that we haven't internally tested ourselves. The issue comes with the amount of different devices and flavors of Android that could potentially make things difficult to solve. At this stage, there's no global bugs that need to be reported (bugs that affect everyone), but there could be many device specific bugs that few people experience or user specific issues. If a user has a specific bug, we ask that they click on the HELP & SUPPORT > REPORT A BUG menu items at the top of this page, and open up a ticket for that particular crash. This allows us to keep track of them all more easily, and keeps things organized for our small team. We will also be expanding our internal crash reporting tools in the next update, which should help things a lot, especially for device specific issues that users may come across. Something to keep in mind, just because we don't answer everyone's messages, we are always reading them, testing everything we can, pushing forward everything we can, along with everything else we do behind the scenes. We are sorry if we can't get to a particular thread or message in a good amount of time, or if a particular message looks to be ignored. They are most definitely not. In general though, this beta thread should mostly be used for beta specific feedback on features and changes that get introduced based on our changelog. Sometimes, it's hard to know the difference, so if you don't know, it's better to post. However, hopefully this post helps provide some better places for things like feature requests and user specific issues. Thanks to everyone who has provided feedback up to this point. We are hoping to have a beta 2 out, but an ETA on that is still undetermined as there's a lot of work left to do on it.

The only thing I see mentioned is that the RetroAchievement's full API was brought back online recently and CBeats will now need to do a review of any API changes before any decisions will be made for LaunchBox.

It depends on the type of set you have, but overall some are required and some aren't.

I'm not really saying this is your specific issue, and yeah, it's been a long time since I took my computer networking 101 class. I'm just trying to provide you with some basic knowledge of how Windows works in the hopes that it may point you in the right direction. It could be something entirely different that you are running into but it may be worth a few tests. One way you could test this (based on your scenario), is by sharing the folders to UserX and seeing if that solves your issue. If it doesn't, then you may very well be running into another issue.

So, again. LaunchBox doesn't require any permissions, Windows does. You just happened to open LaunchBox using a specific user and in Windows that user comes with it's own permissions. To highlight that point, if you hold down SHIFT and right click any application, you'll notice a new option that allows you to "Run as a different user", which allows you to open that application using another user and take on that user's permissions within that application.

LaunchBox doesn't make any file requests, it's Windows that does. I'm not really sure that this is your specific issue, but imagine this scenario: You are logged into Windows with User1. Within a file explorer you authenticate to your network drive using User2 who is the only account that has permission to access those files. You open LaunchBox and you drag and drop files from your network drive into LaunchBox. LaunchBox tries to gain access to those files based on User1's permission access (since that is the user who opened LaunchBox), and Windows denies it because User1 is not authenticated to access those files, only User2 is.

Going to lock this thread since this thread is referring to an old issue that was resolved over a year and a half ago, and I see you already opened up a separate topic with your current user issue, which is a better place to continue the discussion.

Yes, it's because you unchecked the skip unplayable games filter during import. I would keep that checked so you don't import files that are unplayable.

Just to let you know the issue in this thread is not the same as what is reported by you here. This was an issue where new uploads to the database weren't being reflected in the app due to a failed scheduled process on the server, which was then quickly fixed shortly after.

It's hard to say, but it sounds like you may have imported your MAME ROMs incorrectly. If you are seeing bios files and other non-games in LaunchBox, then something definitely went wrong with your import. What were the steps that you used for your arcade import?

I've been running ROMs from a network location for about 5 years and haven't run run into the issues you've talked about. It does read more like some kind of permissions mismatch. Like the user you used to open LaunchBox doesn't have the necessary read/write permissions to those files on the network drive.

Hi Everyone, Beta 3 has been released that fixes the changes made by Microsoft with their Xbox / Microsoft Store authentication. At this point, Xbox / Microsoft Store integration should be fixed. We've also progressed with the Game Discovery Center, but it should be noted that it's still heavily a work in progress. The main change to this view is that the placeholder lists have now been replaced with a dynamically generated one that will refresh upon each load of this view. New lists will keep generating as you scroll down. We still have some ways to go here, and there's still a lot of placeholders in the view that will be worked on. We are still exploring adding videos, more list types, and we've got a number of other fixes and theme related items that we have to get to. Here's the full changelog: Improvement: Adjusted download timeout windows to help reduce download errors when grabbing media Improvement: The Fullset MAME Import Wizard is now more performant on lower end hardware Fixed: Rare dictionary error when using an Arrange By setting in LaunchBox's Grid View Fixed: Sidebar counts for genres with subgenres weren't being displayed correctly until clicked within LaunchBox (introduced in 13.8) Fixed: Various errors related to the automated import process Fixed: Corrected changes to the Additional App selection in Big Box (introduced in beta 2)

There would be nothing in the code that rotates images in this theme, so I could only guess that you may want to look at the images you are using and see if you can fix them up.

One issue I see right there is that the core is not pointing to the mame 2003 core. You can select it from the core list. You'll also want to make sure Extract ROM Archives is turned off.