Jason Carr

We may add further controller options in the future, but the new implementation provides a lot more flexibility, as the old custom pointer solution only allowed navigation within the boxes and did not allow navigation on any of the popup windows.We could add a custom cursor, but honestly I don't think that custom cursor that we had would work very well outside of the boxes view, since it's so big. I agree about scrolling with the right stick though; hopefully I can add that soon.

@japespin I will take a look at this soon; are you using the LaunchBox.Next interface? It's possible that this is a bug that is unique to LaunchBox.Next.

I will be looking at this very soon. I do want to note, however, that while this issue apparently does affect a number of people, it is not a global issue. It seems to be either system-specific or it may have to do with lower-end specs. The reason why it was not addressed a long time ago is simply because the issue was never detailed out in a way that I was able to understand or replicate. I've since been able to replicate the issue on one of my lower-end machines though, so I can look into a fix. Now that LaunchBox.Next is out, I plan to tackle it very soon.

Yes, certainly. It's on my list.

Hi Mark, unfortunately it's not yet possible to bind multiple keys to the same command in Big Box. It was actually an item on the latest community poll, but it came out third from the bottom because it didn't get very many votes. So hopefully we can add that eventually, but it hasn't been a popular request.

Makes sense guys; I can see adding an option to prevent switching views without the pin, and combining the view menu items as well. It's on my list, though it might be a while.

I'll take a look (though I assume you don't mean animated gifs). I expect this was some sort of a fluke, or unrelated to the LaunchBox 8.5 version. Let me know if you're still experiencing it. If you could create separate posts for these, I'd appreciate it. They will probably all need further troubleshooting and more details before they can be addressed (especially since I'm not able to replicate them).

@johnnyskullhead You can manually set your default background in the options. CPU usage is only high while background caching (see the small progress bar at the top of the window). Once that's done, it should settle down to near zero.

This was fixed in 8.5, which came out yesterday.

Much appreciated.

Sorry for the road block @nietzsche666. The visual customization options in LaunchBox have always been premium-only, so we plan to keep them that way. The point is to make it work out of the box for everyone, but require the premium version if you want to do special customizations.

Great to hear.

Thanks for figuring that out. Yes, the ' character has always been an issue, but it should be telling you that. I'll take a look. I'm confused; are you still seeing any of these issues with 8.4?

@klownk Already spoke with you on Bitbucket about this here: https://bitbucket.org/jasondavidcarr/launchbox/issues/4431/vertical-spacing-not-working I will be allowing for larger aspect ratios at some point here soon, which will solve your problem. It seems that you're not understanding the concept of how aspect ratio works in LaunchBox. Regardless, I get it. You don't need to keep ranting about it.

Thank you James; very much appreciated.

Just a quick reminder that this thread is not for general feature requests; it's only for pointing out features that are missing from LaunchBox.Next, but are included in the original LaunchBox interface. @LuismaSP89 LaunchBox.Next will support custom themes very soon, which will allow changing that fairly easily. We may also add custom spacing settings for the sidebar in the default theme at some point as well.

Wow, well thank you very much James. I would honestly discourage you from donating money to us at this point, because we are definitely a money-making business. There's always our Patreon page though if you still feel the need: https://www.patreon.com/launchbox

Thanks Bob, good to know. I'll add that to my list.

@ArcadeCab Ah, no one's brought that up. I suspect that not many people use LEDBlinky with LaunchBox (mostly only with Big Box I would imagine). I'll take a look.

Yes, it should be fairly simple. Look for the "KeyTime" properties; they set the lengths of time. I'm not sure; I think you might need a plugin of sorts since I'm not sure if you can bind directly to a custom field from the XAML. So unfortunately, it may not be as easy as it should be at this point. Someone may have done that already though; at this point, the amazing theme developers tend to know way more than I do in the XAML.

I'm lost on this, but I'm guessing the games are just being filtered out somehow, or are not where you expect. Will need specific details in order to help further. Yup, we will look into that soon, though not before the next official release.

@nathanddrews You can retrieve the code by going here and recovering your license email: https://www.launchbox-app.com/premium/lost-license

@jayjay I know this is confusing; sorry for that, but VideoPath is only used when the video has been set to a custom path (isn't automatically picked up from the file system). Instead, you can just use selectedGame.GetVideoPath(), which will include the default paths as well.

Thanks for the details, @MadK9. I think we'll go ahead with the release though, since those don't seem to be deal breakers, at least. I can look at those issues here soon though. Yes, we can update 7-zip at some point here. I don't want to do it before the next release though, just because it's too late before the release. Wow, pretty crazy. So apparently VLC just has some bugs with Ogg Vorbis. Good to know. Thank you much @kmoney.

Hi Claudio, I don't have a solution for this currently. I'm sure something out there can do it, but I've never done it so I don't really have any good ideas.