Jason Carr

That makes sense. I don't believe marquees are configured properly currently for videos, which is why they're not being disposed. At this point I don't think we can do videos in the marquees, but I do believe that was on the poll, so hopefully soon enough.

The development team has actually grown to two people at this point; I haven't announced it but it we have another developer named Jaron Davis helping out. We'd like to be able to hire him full time as soon as we can, but he's currently part time because we need a little bit more income before we can afford it. I'm a firm believer (now more than ever) that all development needs to come from paid work. That said, if you'd like us to keep you in mind for the future @FlightRisk, go ahead and send me your resume. jason@unbrokensoftware.com

These have not been integrated yet. No, unfortunately these will not likely be implemented before the official release, though of course they will eventually make their way in. There's no proper way to do this; it's confusing no matter what we do. I also have to keep performance in mind; it's not worth combining all the games together and removing all the duplicates just to get the perfect count on the platform categories, as that is a major performance hit. We may still tweak it, but it's not something that can ever really be perfect due to the complications of playlists and duplicate games.

I see. Perhaps I should fix that lol. I had previously added CenterVideos and StretchVideos but they weren't doing anything. But perhaps I should add those back in just so things don't break?

It's that time again folks; we're hoping to put out the 8.2 official release mid-next week. I've added LaunchBox.Next for this release, of course, so there may be slightly more to translate than the last few releases (though it shouldn't be too bad either). All the new stuff for LaunchBox.Next is in the Strings file, just like all the Big Box stuff. Keep in mind that for the new LaunchBox.Next translations, there are a number of them that look like this: _Edit or Co_nfiguration Just like the ampersands work in LaunchBox, LaunchBox.Next uses the underscore character to specify which key on the keyboard can be used as a shortcut for the menus. In the top two examples, the E key and N keys would be used. When translating these items, you can either just remove the underscores for the translated text (which would also remove the shortcut keys), or you can put in your own underscores to add your own shortcut keys. The only issue is that you'd then need to test to make sure you haven't used any duplicate shortcut keys for a certain menu. It's probably fine and easiest just to remove them, but you can certainly go through that extra effort if you'd like. Thank you all very, very much. @CliveBarker @AFaustini @Wattoo @Opak @dukeemu @cyanjiang @Bardock @MajKSA

Beta 10 is out now guys with the following: - Improvement: A new "RotationAmount" property has been added to the Big Box FlowControl (for theme developers styling the wheels). This allows theme developers to create a more cohesive-feeling wheel with items that rotate as the wheel turns. I added that by request for @CriticalCid's new Unified theme and just felt like tinkering with it this morning, so I figured why not. It does add a lot more flexibility and styling options to the wheels. I also added a StretchVideo property to the video transition presenters for the theme as well. Keep an eye out for a theme update from Cid.

Wow, okay. I guess I'll have to circle back to it. Maybe it just has to do with a setting of mine. I may or may not get to this before the next official release, but I'll do my best.

@subatomic09 That's pretty weird. We're going all-in on LaunchBox.Next at this point, so I'm hesitant to spend significant time on the previous rendering engine that won't be used going forward. I've honestly never seen that before so it must not be a common issue; LaunchBox.Next is available in the latest beta.

I think the only difference is that Hyperspin slants the logos, while Big Box currently does not, though it could probably be done via a plugin. I can look to see if I can build that in at some point here soon.

It's been swapped out for the regular Snes9x core.

I can't replicate that issue no matter how hard I try, so I'm guessing it's a one-off issue with certain video card drivers or something similar. Has anyone else ever seen the below issue?

Beta 9 is out now guys. I've been mainly patching holes and fixing minor issues with LaunchBox.Next. But also: - Improvement: The default platforms and settings for the Retroarch emulator have been updated with more platforms and more modern core choices - Improvement: RetroHumanoid's amazing theme videos have been added as an option to the Platform/Playlist theme video downloads We're looking to put out the official release early/mid next week.

The 3D engine is still in limbo; I haven't been back to it since Vlansix was working on it. Unfortunately Vlansix has disappeared, which is the reason it's in limbo. I may or may not get back to it, but surprisingly it hasn't really been a popular request. Regardless, Big Box *does* offload and use the GPU significantly. WPF does that automatically via DirectX. It's certainly not as optimized as a AAA game, but that's the cost you pay for rapid development, the theming engine, etc.

Big Box performance is more due to the fancy display/graphics than anything else. LaunchBox.Next and Big Box use the same underlying code and engines, so it's not like I can overhaul Big Box like we're overhauling LaunchBox. That said, we will continue to focus on improving performance.

Yup ^

Hey all, a new beta is out with the rest of the LaunchBox.Next system menu working. See here for more details:

Alright, beta 8 is out. We finally have the rest of the LaunchBox.Next system menu working properly, though there are still a few items that will just say "Coming soon" due to missing LaunchBox.Next features (such as the game details sidebar, image groups, etc.). From here I'm planning to focus on fixing any obvious glitches and adding a few housekeeping things like automatic updates, and then we'll look to put out the official release early next week. I believe the issues with the Options screen are fixed in this beta; let me know if not.

LaunchBox.Next is still beta, so you must use a beta release. We'll release it officially when it's ready (and we're confident it's not going to mess up people's data, for instance). You can always install another copy of LaunchBox, update to the beta, and play with it that way.

The options menu is what screwed everything up, including the language. I'm looking into that bug.

Odd. It sounds like somehow your XML files got corrupted @We1Dont7Die when LaunchBox.Next crashed. I guess this is why we always emphasize that people need backups if they use the betas especially. Regardless, I'm sorry that happened. Your best bet to get things back the way they were is to try and restore XML files from the LaunchBox\Backups folder. Let us know if you need help with that. If you have a complete separate backup, all the better.

As mentioned above, beta 7 is out now with a bit more implemented in LaunchBox.Next:

As best I can tell, this seems to be a one-off, as I haven't heard this from anyone else. If you can zip up and send me your Data folder in a PM @Drybonz I'll see if I can figure out what's going on. The options will apply to Big Box (they'll actually have separate settings for Big Box hopefully), but that's not quite implemented yet. Let me know if you're still seeing this in beta 7, which just came out.

One more thing; please let me know if games are still not populating on first launch in beta 7.