Jason Carr

Images from one region should never replace an image from another region (we want to keep both images instead). So if a user submitted an image replacement that replaces a European image with a US one, or vice versa, it should be refused. Instead, users should be adding a new image with the correct region listed on it, and if necessary, they can update the old image to be the correct region as well. Sooner or later I will be adding notes text blocks to the moderation and submissions so that we can explain this to people in the moderation process. Also, I think it'd be nice to have an option to keep both images in this situation. So that'll be coming eventually as well.

Thank you @billyc999. The metadata all looks great; got your email as well. I should be able to merge the data into the LaunchBox Games Database.

Thank you guys for getting this conversation started. Hopefully we can get it all figured out.

Great, thank you both. Planning to put out the new 5.10 official tomorrow. :)

Hi @graf, if you want a custom library with MAME, unfortunately the only good way to do it is to build it manually. Although favorites do work well too if you want to have everything and just show favorites at the top of the list. The other thing you can do is mark the games that you don't want as hidden. And then set LaunchBox/Big Box to not show hidden games.

Yes, "Accept Delete" means to approve the deletion and actually delete the image (if there have been enough approvals). "Reject Delete" means to keep the image. One issue we're seeing with the images right now is that some users are deleting existing images and then adding new ones instead of replacing them, which gives us no visibility as to why they're deleting an image. Really, images should only be deleted if they don't meet the quality requirements or are misplaced. If in doubt, you can reject image deletions. I'd rather not get rid of images unless they really are incorrect.

Wow! Very cool @AHmedia, you've got some great ideas there. Very pretty too. :)

Hehehe, thank you @Cebion and everyone else who's helping moderate. :)

Yes, should be pretty kosher now with the latest betas.

For starters, in order to keep us out of hot water and largely because we don't yet have any age restriction stuff in place (not to mention that all data is always accessible whether you're logged in or not), we need to enforce the "no nudity" rule. In the future once the more important things are taken care of, we can add safeguards in for that stuff and perhaps eventually allow those games in a restricted state. For now, though, we don't have that stuff in place, so unfortunately this means we do need to block nudity for the time being.

New beta is out with the Brazilian Portuguese translation update. I think we're pretty much ready for the official release. @AFaustini, can you translate these release notes? Thanks! Also, @CliveBarker and @Wattoo, the last line is a new one so if you guys can translate just that last line, that'd be awesome. Thank you all! Here are the biggest changes for the latest releases: - New optional VLC video playback engine - 7-zip, RAR, and Zip archive support for ROMs - XInput support for controllers - My Collection syncing to the cloud - Significant improvements to the MAME importer

@DR9, @DOS76, @jking3 I think I have the Big Box stability issues fixed (at least the ones that were related to VLC). See the beta testing post: https://www.launchbox-app.com/forum/features/launchbox-beta-testing/page-76#p15467 Please let me know if you are seeing any more stability issues with the latest 5.10-beta-6. Thanks! :)

It didn't use to do that, but I had to enable it because if I don't then people are constantly getting errors related to missing runtimes, sigh. So that's the trick...I'd rather just force the DirectX install every time and not have people getting crashes because of their machines not having it all. Sorry for that.

Alright, new beta 6 is out, and for me at least, it has fixed the VLC-related Big Box stability issues. Hooray! This was driving me nuts for like 2 weeks, not even kidding. Nothing seemed to work. So I literally prayed about it and 10 minutes later an answer popped into my head. Turns out, all I needed to do to was update the VLC libraries. Lo and behold, no crashes. Wish I would have asked the Lord for help 2 weeks ago. I'm also hoping this fixes the errors with 32-bit Windows installations as well. The Brazilian Portuguese translation is also updated thanks to @AFaustini. I believe we're ready for the official 5.10 now; I'll give it a couple days though to make sure nothing else pops up. Thanks! :)

Thanks @SagaXIV. Yes, that is a known issue that I do plan to solve here soon. There is a general issue where if you want to name a platform differently than the official names or one of our alternate names, then there are issues scraping. I think I'm going to take the community's advice and add a field called "platform to scrape" or similar on platforms, which will let you override this stuff.

Hi @SagaXIV, by chance are you using the latest beta? @muppets4 is having an odd issue with controllers here: https://www.launchbox-app.com/forum/troubleshooting/strange-behaviour-with-big-box-and-steam-in-home-streaming#p15464 Was curious if you had ever seen that or if you happened to know how to solve it, since I don't have a Steam Link. Thanks!

Okay, hrm. It does seem that there are other people using beta 5 with Steam Link streaming without issues, so my guess is that it would be some sort of odd configuration with the Steam Link. Unfortunately I don't have one to test with to confirm either way. I'll see if I can get some other people with Steam Links in on the conversation.

Wow, thank you guys for all the support. There's a heavy emphasis on the community here, and that's because *you guys* are such a huge part of making this all successful. Thanks again and thanks for being such a great community.

No worries! Glad it's sorted. :)

Thank you @AFaustini. I have this integrated so it'll be out with the next beta. :)

Hmm. Just to note, the Controller Automation configuration is different in both LaunchBox and Big Box, so you have to configure them separately. So for starters, you can compare the configuration between LaunchBox and Big Box to see if anything is different. Also check to see if Use All Controllers is checked for either of them. If LaunchBox or Big Box isn't configured to use the particular controller you're trying to use, it won't work for controller automation. Let me know if any of that helps. Thanks @niglurion.

Weird. Beta 5 introduced the controller automation replacement of the old controller AutoHotkey. What happens if you turn off controller automation in the settings?

In all honesty, LaunchBox kind of sucks; you should probably stick with Hyperspin. Just kidding lol. I'm the developer. :) The biggest reason why most people give it a shot at first is just because you don't have to tinker with stuff so much. For the most part, it just works. Then people stick around because of the community, the new features coming out all the time, the ease of managing your games, etc. Just my guesses/observations as to why most people choose LaunchBox. Some people prefer it visually too if they prefer a cleaner and less flashy/less in-your-face look over Hyperspin.

Thanks, Brad. Yes, let's everyone move conversations over to new forum posts on the new forums (this is getting a bit unwieldy).

I've had the same thought, Scott. I think ideally we'll want to support multiple release dates (one for each region). It'll probably be a while before we get there, though.