Jason Carr

Great to hear @CliveBarker. Just put out a new beta that I'm hoping will resolve that error for you. Let me know. :) This beta also includes @cyanjiang's latest fixes for Simplified Chinese.

Thanks guys, those are two different errors (@CliveBarker's and @GatoSoft's). @GatoSoft, unfortunately that error is a hard one to resolve, but it's usually associated with video hardware or driver problems, according to Microsoft. So first things first, try updating your video drivers. Also, remind me what version of Windows you're running? Supposedly the issue most likely has to do with the hardware acceleration required for the animations, and for whatever reason your system is tripping up on them. We'll see if anyone else has that issue. I'll be adding options to disable the animations, so worst case scenario, you can disable them and at least be able to use Big Box. It looks like I might be able to add an option to disable hardware acceleration as well, which might resolve the problem for you. @CliveBarker, I'll get that fixed. :)

Just put out another beta with some Big Box animations; I didn't want to be adding things this late in the game before 5.0, but I can't leave well enough alone. I'm pretty pleased with how it all turned out. I have a pretty killer animation engine behind it all, so the possibilities are pretty much endless. I left it relatively toned down because I haven't gotten around to adding settings for transitions yet, but if you can envision it, I can add settings for 10 or more different transition options for everything separately. So I think that is gonna be pretty awesome. I'm curious how well it all performs for everyone, especially on older machines. Obviously, we will provide the option to turn all animations off before the final release (in case your machine doesn't measure up or you just like to keep things simple).

Makes sense @Xananax. Scripting/plugin support is something I keep getting reminded about, but still haven't yet been able to focus on. What scripting engine would you want to use?

Ah, thanks @scree. Good to know.

Bil said This may have been mentioned before, but when I adjust the details sidebar position, it never saves. Instead, it reverts back to its default position the next time I run LB. Hmm, that's strange. I've actually never heard that before, and of course I can't reproduce it. Can you upload or send me your LaunchBox.xml file to jasondavidcarr at gmail dot com? Thanks.

scree said Hi Jason I just installed this beta via BigBox. Installed perfectly, although I couldn't get the BigBox Yes button to accept mouse click. No sign of the db files issue that Martin had. I assume you have the mouse enabled in Big Box?

Thanks @AFaustini; I have that fixed, so it'll be in the next beta.

I couldn't sleep, so here, have another one. I added an option to emulators to "attempt to hide console window on startup/shutdown". This works great for emulators like Retroarch and MAME/MESS. It makes for a much cleaner experience, especially for Big Box. I also added some new default emulator settings for VisualBoyAdvance-M (Game Boy, Game Boy Color, Game Boy Advance) and Kega Fusion SG-1000.

Just put out another new beta. This has all the new updated platform metadata and platform images, proper language for Brazilian Portuguese and Spanish in the setup, a fix for mouse clicks in the Big Box updater, and fixes for the links in the About box for Brazilian Portuguese and Simplified Chinese. 5.0 is starting to feel real...

After adding Martin's platform metadata, here's what's left: Android Atari 800 Atari Jaguar CD iOS Mac OS Microsoft Xbox 360 Microsoft Xbox One Nintendo Wii Nintendo Wii U Ouya Sega CD Sega Mega-CD Sega Model 1 Sega Pico Sony Playstation 3 Sony Playstation 4

Thank you Martin! Got the XML. I'll get it added. :)

Hi Brad, I'd rather just include them all to make people happy. That way it's easiest for the user (and I don't have to develop a whole customized system to choose which platform name you'd like displayed).

Thanks Martin. For now though I'm keeping the default images included to be for true game platforms only. When we open it up to other types of media officially, we'll look to add images like those. For now, it should work fine to add it manually through Manage Platforms, of course. :)

FYI guys, I added all the new platform banners and clear logos from @bd00's repository to Big Box. The new beta should be out tonight.

That'd be awesome @Maddoc1007. I added some to the list: Android Atari 800 Atari Jaguar CD Capcom CPS1 Capcom CPS2 Capcom CPS3 Capcom CPS Dash Crystal System iOS Mac OS Microsoft Xbox 360 Microsoft Xbox One MTX Namco System 22 Nintendo Wii Nintendo Wii U Ouya Sammy Atomiswave Sega 32X Sega CD Sega Mega Drive Sega Mega-CD Sega Model 1 Sega Model 2 Sega Model 3 Sega Naomi Sega Pico Sega System 16 Sega System 32 Sony Playstation 3 Sony Playstation 4 Go ahead and upload the file here @Maddoc1007 or email it to jasondavidcarr at gmail dot com and I can add them. :)

Yeah, I'm just concerned that it might happen again, or to somebody else, or to lots of other people lol. ;)

Hmm, could they possibly be Thumbs.db files? Windows creates those automatically. But looking at the code, I still don't see how that would happen.

Thank you @CliveBarker! I have the setup updated for the next beta. @AFaustini, the trouble with something more simple like INI files is that there's a *lot* more complication involved in the translations than just the text. Every form/window needs adjusted to fix overlapping elements, sizes, etc. for each language. I've used the standard approach for .NET Windows applications in order to allow for all of that without horrible complications. I realize that it's not the easiest thing in the world to work with, but I do think it's a good compromise. Changing it up to use something more simple like INI files would be a ton of work on my part, and the end result would be problematic. So my apologies that it's not easier to work with; I do really appreciate all the work you and everyone else is putting in. :)

Hi @scree and everyone else; I've updated all of the alternate platform names for all of the platforms. We now have 84 platforms with 288 alternate names. I'll get the updated metadata in a new beta sometime today. Thanks to @scree, we have metadata for 70 of the platforms, so the vast majority of the work has been done. However, there's still 14 platforms that could use metadata: Android Atari Jaguar CD iOS Mac OS Microsoft Xbox 360 Microsoft Xbox One Nintendo Wii Nintendo Wii U Ouya Sega 32X Sega CD Sega Mega Drive Sony Playstation 3 Sony Playstation 4 Let me know if anyone is interested in grabbing metadata for those platforms. Keep in mind that some of the above platforms are semi-duplicates (such as a different name for the same machine in different regions), so you might be able to duplicate some of what is already there in some circumstances. I'm just not an expert on it all so without research I don't know the details of all that off the top of my head.

Maddoc1007 said @Jason dont know if this helps you but i went on one of the games right clicked, then edit, i then went to one of the images that wasnt there and tried to save it to desktop. it looked like it was saved but nothing was placed on desktop. however if you look at the name for the non-existant image it finishes with an -01.db see enclosed image Ah, I see. So it looks like LaunchBox is somehow finding ".db" files in your images folders, and for some reason it thinks they're images. Can you confirm and see if those files do actually exist? I'm guessing that something on your system is probably creating them (they are very possibly system/hidden files that only show up if you turn off hiding system files in Folder Options).

Good things to check, @SentaiBrad. The only other thing that comes to mind for me is a possible interrupt conflict, or something of that nature. Those happen very rarely, but I have seen them on modern machines, and they can cause some really weird things to happen. I would try swapping out hardware left and right, to see if you can narrow it down. Try switching between a PS/2 and USB keyboard, removing the game controllers, trying different game controllers, different mice, etc. You probably already know all that stuff though. I'd make sure absolutely everything is disconnected from the back of the computer, and test things one at a time. If that doesn't fix it, then it probably comes down to pulling out all hardware inside of the machine, swapping RAM, video cards, etc. Finally, one thing that always helps me out is booting onto a Linux live CD to see if the issue is hardware or software. If it happens in Linux too, it's probably hardware somehow. If it only happens in Windows, it's probably software- or driver-related.

Lol, one more thing guys. If you have a translation under way (you're in the process of translating and have an outdated set), don't worry about updating it if it gets updated here. You can go ahead and finish that set, and then I can merge in the changes, and then afterwards you can download a new set and fill in the holes. We just need to make sure that once you submit translation files to me, we'll need to wait until I have them integrated and a new download is ready before any further changes are made, to make sure that nothing is lost/overwritten.

Oh, and yes, the links in the main post will be the updated ones. However, the links won't change; I'm only updating the downloads behind them (I set them to never cache so hopefully that won't be a problem). Also @CliveBarker, did you see my post a few back about the new setup? :)

No problem, Clive. Thanks for following up; it's good to provide clarification on that stuff. I just updated all of the translation packages, so they are all currently up to date, with all new translations for 5.0. There's a lot of new stuff this time because it's a rather large release, especially with Big Box. The translation packages will be updated with every new beta, so if you want to, you could update after every new beta. But in general, that's probably *way* too much work and it's mostly unnecessary. I think the best approach will likely be to wait until we're close to ready for the actual release, and then they can be done in batch. Things change quite frequently between betas, so what I will do is notify everyone when we're close to ready for a release, and then we can update the translations. How's that sound? We are indeed close to ready to release 5.0, though, so now would be a good time to go ahead and do the 5.0 translations. I don't think the languages will change much (if at all) before 5.0 hits.