C-Beats

Believe the CTC lets you choose between "Active Game" binding and "Selected Game" binding. Selected is updated instantly, Active is delayed. Any additional elements displaying information about the game being hovered over should be using the Active binding to help reduce the delay you're seeing. There could be other factors affecting you that I'm not aware of, but this typically is the most egregious cause for the delay you're showing in the video.

There a reason you're wanting them in search instead of using the quick-filter?

Also worth noting that Windows itself will push any RAM usage the app (or any other app) is using to the page file if it isn't the active application and the OS needs the memory the app is sitting on. This act of moving it to the page file the first time IS slower but after that first time the memory stays in the page file until you return to the app and so wouldn't affect performance after that.

Biggest difference between the two themes you see are the use of the "Active" and "Selected" game bindings. First theme is using the one that is updated immediately and so every time you move it updates every element in the theme. The second one is using the delayed one that only gets updated after you've stayed on the game for a second. Because the second isn't trying to load a bunch of images/videos instantly every time you move in the list it works faster.

Just so you are aware @Madhead there is both a side bar filter AND a quick filter for custom tags and so you can use either when trying to navigate to games with a specific tag

Can disable the icons via the View menu

Thanks for that additional information. I was having a hard time replicating because we already have it corrected internally and I hadn't realized. This will be fixed in the next beta release which we are planning to get out today. Thanks for the detailed report, made tracking it pretty easy.

What theme are you using when you see this behavior?

Are any error messages provided or does the app just close? I'd have to grab my Odin and play around to vet, but I'm fairly certain we have debug logging in the Android app as well, could make sure it's on and then navigate to \\LaunchBox\Logs\ and see if anything is generated in there that could help shed some light on what's going on.

Yeah, there is currently a bug in image view using those image types. It's been corrected internally and will be fixed for next release. Right now the only work arounds are to use list view or use a taller image type

What model do you have? How much memory? I personally have never ran into the issues you're having but I know Android does like to kill apps if they are hitting any resource "too hard". I don't dev on the Android side as much so not sure I can offer much help with what to try to better your experience unfortunately.

Can also use the sidebar filter labeled "Games Missing Media" and then select the image group that you are wanting to look at. Typically if that's all you care about it's the faster option

You can do this by setting your image group priorities and adding more image types to the group in question. For example you could add "Clear Logo" to the "Box Front" group and if then if all the other image types aren't found it'll fallback to the clear logo. You also can set platform level fallbacks but then any item missing media in that platform would have the same image drawn.

No need. We've identified that the issue is caused by using certain image types and have it resolved internally. Thanks for the report!

@idolfun @dreamy Are you seeing the memory consumption issue in LaunchBox or Big Box? What theme are you running when you see this behavior?

Should just resume when you start up LaunchBox again. If it doesn't just run the download wizard again and on the last page select the middle option (Do not replace) and you'll only grab media for items that don't already have it.

4) Use the current MAME core

Version 13.4 Beta 3 has been released. This updates finishes cleaning up several issues regarding the image view not behaving correctly. This version addresses the following: Fixed: Several arrange by groups of a single item were causing the rows to render on top of each other Fixed: Last item in a row wasn't always resizing the row correctly Fixed: Pressing a string of keys to jump to a game (pressing M to jump to first game starting with M for example) wasn't scrolling to the correct position Fixed: After manually adding a new game the grid wasn't jumping to that game Fixed: Crashes related to using an arrange by setting other than title that some themes were having Fixed: Issue related to deleting the last item in the Game Details carousel preview This version should correct any reported issues with image view rendering and behaving as it was in 13.3 (or better). If you still are seeing any of the reported issues, please let us know!

Yeah, we manually unzip 7z files ourselves but don't ZIP files because they are supposed to work in the hasher program, but it appears it isn't doing so correctly for some file formats so we may need to look into changing the process a bit for disc based systems

1) APK available via our website (much like the PC app) 2) Not typically. Android has it's own structure for how/where app's are installed typically 3) I find external storage the easiest on my Odin Pro, but it isn't required 4) MAME core for RetroArch is what I use (and is default in the app)

We've seen this before when people have corrupted media in their collection. Typically a file that got saved incorrectly and can no longer be opened.

The app only downloads images that are for the region your game is set to. If you have the JAP region set on your game and the game has JAP images in the DB you will only get the JAP images for it.

I have a tool available in the download section that sounds like it can probably do what you want. I haven't used the tool since I posted it and not even sure if I still have the codebase for it though so if it doesn't pull through for you in it's current state I wouldn't hold much hope for it to be revised. Can find the tool here:

We've had some reported issues of Steam controller data not always coming in correctly but I haven't had a chance to look into. They probably changed something in their API return that we need to compensate for. You can edit the games (or bulk edit) them to add the information in the meantime. It's definitely more manual and time consuming than we'd like, but gives you a work around while you wait for a fix.