radio5

@Astrobob Wow! Thank you for the thoughtful, detailed response! You didn't have to go the extra mile, but you certainly did with that explanation, and it makes perfect sense. You guys are always super helpful and friendly when it comes to helping out the users, while most companies would just shrug their shoulders and tell you to Google it. It's one of the many reasons I'm always telling my friends and family about LaunchBox. Buying a premium license was one of the best purchases I've ever made. With all the updates and progress, there are bound to be a few hiccups along the way. I've been looking to get away from Google Drive for a while anyway, so no worries. Thanks, again

I spoke too soon. The issue persists, unfortunately.

I believe you are correct. I paused syncing in the Google Drive app, deleted the plugins folder in my local and online builds, and continued to leave syncing paused for a few days. I then resumed syncing in the Google Drive app and haven't had any issues for the last several days.

@AstroBob, @faeran Sorry for the delay in getting this log. Life got in the way. Anyway, I've attached it. Thanks Debug 2024-10-08 10-54-51 AM.log

@faeran As soon as I get home I'll post the crash report. Thanks

@AstroBob It's always the Plugins folder. If I delete one plugin and relaunch, the very next one will be the culprit. My LaunchBox directory is hosted on Google Drive. It's on a local drive and mirrored in the cloud.

Hello @AstroBob. Thanks for asking. I'm currently running the lastest version 13.16, but it's been ongoing since 13.15.

I'm experiencing this same issue. I'll uncheck "Read-only" and hit "Apply", but when I open properties, it's still checked. The only way I can get around this is to delete my Plugins folder every time I start LaunchBox. I'd be very grateful if someone knows how to fix this once and for all.

When I try to update to 13.15 or 13.16, I get the following error message. The only way I'm able to use the program again is to revert to 13.14. I reported this on bitbucket, but I thought some of the knowledgeable folks on this forum may know what's going on. Clearly it has something to do with permissions on the "Plugins" folder, and I've tried editing the permissions, but they keep reverting to "read only". Thanks *UPDATE* After looking at the "Plugins" folder more closely, I noticed none of the folders actually contained any files. I moved the folder to my desktop and ran the 13.16 update. LaunchBox started up like a champ once again. Leaving this here in case someone encounters a similar issue.

For what it's worth, this post helped me out. I couldn't figure out how to make my mouse cursor visible but disabling "Use Game startup Screen" fixed everything. Sorry nobody responded.

I'm having an issue that I've been unable to crack for a few days. Thanks to Google's complicated new Drive for Desktop app, I lost my Launchbox collection and I'm currently in the process of rebuilding it. Anyway, the mupen64plus next core launches Nintendo 64 titles just fine when using standalone Retroarch. But I only get a black screen with sound when launching from Launchbox. The correct core is designated in "Manage Emulators", so I'm at a loss as to what's happening. I suspect Retroarch is starting with the vulkan driver instead of gl, but since Retroarch now let's cores switch video drivers as needed, I don't know why it's not happening. But that's just my current theory.

Jason, this updated beta fixed the issue for me. Thanks for being johnny-on-the-spot! I'm so pumped about this feature.

Man, that was a while back... I don't have the issue anymore, but I can't remember exactly what fixed it. I think it was making sure Steam was completely closed before starting LaunchBox, which I now do religiously. Hope this helps.

Thanks, but I tried disabling automation and problem persists.

Lately I've been getting some odd notifications when starting retroarch via launchbox. Here's what happens: I'll select a game while in BigBox mode. Then, when I press the guide button on my xbox one controller, I get the following notifications in retroarch: "Waiting for client" "Joined as Player 1" (then after about 25 seconds) "port remap failed" It's only after I receive the final message that I can do anything such as save/load state. Now, I realize LaunchBox has nothing to do with retroarch from a development standpoint, but when I start retroarch directly, I don't get any of these odd notifications. I would also like to point out that I'm not using any special launch parameters. Does anyone have an idea as to what could be causing this? Thank you in advance for your help!