Jason Carr

Custom spacing has not yet been implemented in LaunchBox.Next, but it is coming.

I appreciate the offer @Lahma but these days I make it a point to pay for all development that goes into LaunchBox, for quite a few reasons. Feel free to send me your resume though if you're interested in a position for the future.

@Lahma All makes sense. I'm not likely to revamp the entire plugin system any time soon, but I should be able to add what you need for your plugin at least. It may take me a bit though because I need to focus on finishing up .Next here for a bit.

Yes, as I add more of the missing features, more RAM is going to end up being used. Half of the application was basically missing in the 8.2 release lol.

The LaunchBox Games Database is designed very differently than the Hyperspin XMLs, for example, as there is no guarantee that the LaunchBox Games Database has every single game for a particular platform. It's more flexible than that, and allows for game hacks, etc. It's not meant to be a de facto standard for what games are available for a particular platform, so such functionality would be moot.

Per the thumbnails, I will see what I can do to improve it. But it's not a battle that I'm going to win, because on the one hand I will get complaints that the "CPU is spiking every few seconds" if I cache stuff in the background, and on the other hand I'll get complaints that they're not popping in fast enough. There will have to be a tradeoff. In .Next, the tradeoff is leaning more towards less CPU usage currently. @Rod That CPU must be pretty low-powered for it to spike to 14%. I know what's causing it; it's the controller automation and the controller input processing shell. That's unavoidable unless you want to turn that stuff off.

I see. Currently the LaunchBox Games Database doesn't support country-specific release dates. So it just grabs whatever release date is listed there. Unfortunately there's not currently any way to change that.

In most cases where possible, I believe LaunchBox will prioritize the media that matches the ROM file automatically, though it will still download everything first. It just prioritizes it when it displays it on your games.

Trying to figure out what's going on there, but I'm coming up empty. Where are you selecting the image group? In the top right menu or from the hamburger icon? Are the items disabled or are they just not able to be checked? Everything seems to be working on my end and I'm not seeing this reported elsewhere so I'm confused. Unfortunately there's no way to hide the title text at current, though we'll probably provide an option at some point in the future. The publisher names will be displayed instead if you arrange by publishers; however, there's currently no way to set a different default.

This is already possible, and should happen by default when you switch between various platforms and switch image types in LaunchBox or LaunchBox.Next.

Thanks all for the feedback so far. We've definitely identified some stuff that I wouldn't have been able to find on my own.

Gotcha, noted. This is a known issue and I don't think it has anything to do with .Next. It happens because the original bat/exe/etc. file closes before the game actually closes. All LaunchBox does is wait for that original process to close. I see, makes sense. Yeah, those menus in the top right are not traditional menus, so they won't necessarily behave in the same way. Unfortunately I think getting that functionality to be exactly the same is more trouble than it's worth. That looks to be an error with the Ao.BigBox plugin.

I will be looking to possibly improve this at some point, but what you are referring to is WPF's optimization to not use too many hardware resources, and to load and dispose images as needed. This has nothing to do with the cache. .Next uses much less resources and is much quicker to navigate than the previous version, and there are and will be some tradeoffs to that, no matter what we do. I will look to speed all that stuff up, but there may still end up being split-second image pop-in as you scroll. I'm guessing you guys are interpreting the shadows that are around the text in the upper right as blurry. It's a challenge to make that text visible against any backgrounds, light or dark, hence the shadows. There's not really much of a better solution there. I assume this is in .Next? It's working for the majority of people so it's apparently machine or collection specific. Have you checked your image priority settings?

Spacing settings are still on the to-do list (see the first post of this topic). Wasn't aware about manual playlist sorting though; I'll take a look.

I actually purposefully didn't implement clear logo backgrounds this time around because I just don't think they look all that great so small behind all the boxes. I can look into adding it in though; I didn't figure many people were using it. I'm not fully following here; can you explain? Are you comparing LaunchBox.Next to the original LaunchBox version (8.2)? Gotcha, I'll look into both.

This is odd. Can you PM me an image that isn't working? That way I can do some testing. It's possible that WPF just isn't handling broken/weirdly-encoded images as well, so we may or may not be able to fully fix it. We will be adding box customization options, yes (per the first post in this topic). The vertical height issue bugs me as well, so we will be addressing it here at some point, though vanilla LaunchBox has the exact same problem. We'll need to wait until .Next is feature complete before tackling things like that. I had tried to do this but I never found a good place for it that wasn't ugly (I was trying to include the icon as well). I could just make it as another menu item in the top right, without the icon.

So weird. Maybe it's related to hiding and showing the sidebar? I'm guessing these are probably EmuMovies errors that have been there all along. I know this was happening with a previous beta, but it should have been fixed, and I've looked at the code and it's the same as regular LaunchBox now. Are you sure you're on beta 16? Also, check your image priority settings for screenshots. I'm gonna go ahead with the release I think, though we'll definitely get these issues fixed soon enough.

I don't think that's likely a beta issue; I will review but probably not before tomorrow's release. That makes sense because we're repopulating the list view looking for changes. Sounds like we just need to save that setting before repopulating. I'll add it to the .Next to-do list. Glad to hear it's resolved and it's not an issue with .Next. Sounds like we'll be releasing tomorrow morning.

So odd. So that suggests that the up arrow key isn't being pressed. Does the white outline show up on the selected side bar items like below?

This looks like it must have happened in regular LaunchBox. It's a random error that has been around for ages that very rarely ever happens, but I've never been able to pin it down. Since it doesn't apply to .Next at all, I'll probably just abandon it at this point. So in other words, it's unrelated.

Also, have you tried the latest beta @dragon57? Beta 16? Just in case there was some kind of fluke in a previous beta.

So weird. How fast is it moving? I'm trying to rule out what could be causing it.

Gotcha, so somehow this is simulating the up arrow key being pressed, either inside of LaunchBox or by another application. Another thing to check would be if you have any applications running that would cause keyboard presses (like controller software).

Just put out beta 16 to update some more translations and fix some remaining issues with editing Retroarch emulators that are not named "Retroarch". Any testing you guys can do for that situation would be appreciated.

Awesome, thanks Claudio. I'll get both of these translations into a beta shortly.