Jason Carr

Alright guys, new beta is out. I spent the majority of the day fixing the errors/freezes with the "prioritize music over video audio" stuff. It was a royal pain to figure out and fix but I think I finally have it all squared away. Those of you who use that feature, please test and let me know if it fixes any stability issues. Also, in yesterday's beta there was an issue with imports where the application/ROM path was not always being set, which has been fixed in this beta as well. Finally, this should fix @kmoney's reported error with the audits above.

Thank you @dukeemu; I keep forgetting to regenerate those new files. I'll get the translation updated!

Exactly. What you'll want to do is open up each set of files separately. So for example, you would open up these two files at once in Zeta: AboutForm.resx AboutForm.nl-NL.resx Then Zeta will put both languages next to each other to make it easy to translate. It's also important to only open up one set of files at a time (instead of all of them at once), because that will cause conflicts as well. Since you already have the translated text in the original files, I think it'll just be a matter of copying that text over to the other file. When you do it in Zeta, it should only copy over the actual text parts and not all the metadata that way, which should fix the issue (it'll just be annoying to copy each field over as I don't think there's a way to copy them all at once). Thanks again Bardock.

@Wattoo @dukeemu @AFaustini Thank you guys very much; I have the translations updated for the next beta.

@Bardock I have some unfortunate news. Somehow, something went wrong with the translations; the translation package has all the translated text in the original resx files instead of the nl-NL resx files. The problem with that is that the files also contain metadata that can't be in the translation files, so it will cause conflicts. Otherwise, I would just rename the files, but unfortunately we're up a creek here. I think what must have happened is that you replaced the text in the original file instead of putting the text in the new files. To fix it I think we'd have to manually move them all over, which is gonna be a huge pain, so I'm not exactly sure what to do. Again, I'm very sorry for overlooking it, and I'm sorry that I'm just now discovering this problem. I understand if you want to forget about it for now, considering the circumstances. Otherwise, let me know if you want to continue with it and we'll figure out how best to fix it (but it will likely be a lot of work, unfortunately).

Wow, my apologies @Bardock. Sometimes it's hard to keep track of everything. Yes, I can certainly still use it. I'll get it integrated today.

Hi @Mandoo, what controllers are you using?

@faeran, can you upload this to the Downloads section? I went looking for it earlier and realized that it's just in the forum post here.

Alright guys, we're down to bug fixes for 7.5, so now is the time to get the translations in. All packages have been updated with the latest. Also, here are the release notes: New auditing tool has been added to help manage games and media Big Box now remembers the last game for every platform and the last platform used Big Box performance has been significantly increased while using VLC I'm hoping to put out the next official release on Thursday, if we can manage it. As always, thank you guys very much for all you do.

Thanks guys; I've noted all feedback and bugs and I'll be working on it all this week. A new beta is out that adds a proper progress bar to the audits, adds two new columns for background images and LaunchBox Games Database ID, and speeds up the audit process by splitting up the operation across all CPU cores. The audit process is by no means forever done, but I don't expect to make any more changes to it until some time after the 7.5 release (sans for bugs of course). I also fixed a number of other bugs: - Fixed: A null reference error was possible during ROM imports of multi-disc games - Fixed: When editing platforms using the Manage Platforms tool, sometimes the video path was automatically getting set to the video path for a particular theme - Fixed: Rare null reference error in Big Box when between views - Fixed: Flip box wasn't always working correctly in Big Box wheel views I do have more bugs on my list to fix, so I'll be taking a look at everything else soon.

Thanks guys. Yes, nested filters are indeed high up there on the priority list. It also makes sense to allow the same types of media for genres, though, too; which is a separate thing (nested filters will allow you to filter by genre when inside of a platform, but won't allow you to navigate primarily by platform with all the visual goodies).

Very impressed with this theme @faeran! Love the simplicity of it. We'll probably feature it in the email this coming Saturday.

Great to hear @AnUnusedMoniker. I was in the same boat basically. I've actually spent the weekend screwing around with it some more and added a bunch of new features (app configuration commands, browse and run, separators, etc.). I should have a new version up soon once I test this a bit more.

@walter10h Called the first one. As far as the source code, I'll think about it. I hadn't planned to release it and I'd have to change the licensing on it and stuff. I've been using it for my personal collection though and I already want some more features, so I'll probably be updating it soon enough.

@creamdonut, that is good to know. I was seeing that at one point as well, so you're probably onto something with the audio. There is actually a logging system implemented already but it does need a bit more fleshing out. If you manually open Settings.xml in a text editor and change DebugLog to "true", that will enable a log file in the LaunchBox folder. It doesn't log everything yet though.

Awesome! Email is out. Honestly, this theme is one of my personal top 3 favorites now, so I really appreciate the work you're doing here.

Hi @eatkinola; this is looking amazing. Gonna feature it in the email this week.

Yes, there are a million reasons to use VLC, including licensing. We couldn't even use MPC if we wanted to because of the restrictive GPL licensing.

Ha, nice. Indeed. Anyone found any of the easter eggs yet?

Exactly. I remember using a really old version of Access way back as well, but it had stupid limitations. I'm guessing I never used the later versions though. It would be neat to figure out the VGA graphics stuff. That said, I'll probably never get that good at DOS development lol.

Also, thanks much for the error reports guys. I'll have a new beta out end of day Monday with as much fixed as possible.

Let me chime in on VLC since it seems to be coming up a lot here. The issues we've had with it have literally nothing to do with VLC itself; they have to do specifically with the difficulty of integrating *any* video player into the app with support for animations, transitions, etc. To be frank, integrating MPC or any other video player at this point would be a horrible idea, simply because we'd be back at square one, and it would do nothing to fix any bugs; we would instead end up with more bugs to fix. Integrating any particular video player requires immense amounts of code; there's no such thing as a way to easily swap them out, because there's no standard way that video players are implemented. The only reason why we've had less issues with the Windows Media Player implementation is because Microsoft already went through all the work for us. That said, even they've had problems getting everything working across all systems, and WMP refuses to work correctly on some systems as a result (not to mention WMP is likely to get dropped in upcoming versions of Windows). It's not easy to integrate a video player into WPF with support for transitions, animating the videos, playing several videos at once, etc. Switching to a new video player would only cause us more work and we'd have to start over from scratch, so it's just not at all a good idea.

I was just kidding, @lordmonkus; I really don't know. Combined that's a lot to implement and I don't want to make any promises that long-term. Also, let's keep this thread lighthearted and focused on the MS-DOS app.

Two weeks.

Hello everyone! Here's to screwing around with the new LaunchBox for MS-DOS Special Edition 1.0! Check out the details in this video here: And download it here: http://bit.ly/LBXDOS11 Let us know if you've figured out any of the Easter Eggs.