Jason Carr

I don't currently plan to add a bunch more image types, at least not for this release. I can see that being a great opportunity going forward though, for sure. For now, one of the existing image types can be adapted.

Yes, that is the plan. I plan to use the same theming engine as the rest of Big Box.

Beta 2 is out now with the following: - New Premium Feature: Big Box now has "Keyboard Automation" features similar to the existing Controller Automation features, primarily for keyboard-based arcade boards that are lacking in buttons. You can enable and configure the keys in the Big Box options under Keyboard Automation; this will allow you to use key combinations instead of individual keys for closing games, focusing Big Box, or turning the volume up or down. - Improvement: LaunchBox screenshots in the game details sidebar are now in order based on your screenshot priority settings

If/when we do tackle bezels, they will require Retroarch or MAME, and will tie into those emulators, as that is the only proper way to do bezels without horrible hacks (they need to be handled by the emulator itself). There is a bezel project out there right now (simply called "The Bezel Project") that is basically doing everything already though, so I don't look at it as a high priority. It may still end up on the next community poll. The plan is for pause screens to jump to a Big Box-type interface with options, similar to the way that Rocket Launcher currently works. Not promising all Rocket Launcher features, however. I'm not sure what you mean by "scrapper options".

Thanks Aleksey; I have this integrated for the next beta, which should be out shortly.

Yeah, I agree. That is something that we should add. The easiest thing to do currently is just to delete the BigBoxSettings.xml file, but users don't tend to know that.

Glad to hear you got it fixed. That's certainly interesting; I'll keep an eye out for that if anyone else has similar issues.

Awesome, I look forward to getting those in the themes manager as well. I'm guessing the font issue is somehow because of eatkinola's styling plugins? It should in theory work in pretty much every situation, except I guess of course if the styles are being loaded differently due to a plugin. Either way, I think you should be able to just include a separate style file and reference it in your XAML files and that should work fine. Otherwise, you can use the DLL solution which is somewhere around here on these forums. Thanks @SNAK3ATER.

The first 9.8 beta is out now. Details here:

I haven't specifically set out to implement that feature, but there may still be a way to do it with XAML (probably with MediaElement at least, assuming Windows Media Player is installed).

If you think it's data related, feel free to zip up and PM me your current data folder and I'll investigate. It does not appear to be a widespread issue though, as I haven't heard anything else like this since the official release.

Hey all, the first 9.8 beta is out. I do plan to tackle pause screens for this release, but I wanted to get at least one thing out of the way first. This first beta adds the ability to bind up to four different keys to each function in Big Box, primarily so that up to four players can control Big Box at once from keyboard-based arcade controller boards.

Hmm, this is pretty strange. What versions of Windows 10 are you running on those two machines? Are they up to date? I guess the next thing I would try is closing out any and all applications that you have running in the background, including anything that starts up on boot, to see if one of those apps is somehow conflicting. We have seen some issues with some badly coded background apps over the years.

One thing to make sure of is that LaunchBox isn't currently running in the Task Manager. If it's currently running in the background for some reason, then LaunchBox and Big Box won't start up. The easiest thing to do is just reboot, but you can kill all instances of LaunchBox.exe and BigBox.exe in the Task Manager instead. If that's not the issue, it looks like it may be game controller-related, looking at the log file that @neil9000 sent me. What game controllers are you using? Can you try unplugging them to see if that's the issue?

Hi Daz, sorry to hear that you're having trouble. Unfortunately I'll need more information in order to help, or if you'd rather, I can just offer you a refund. What error messages are you getting? Have you tried rebooting?

Sure, okay. It's still connection issues of some kind, though who knows if it has to do with your ISP slowing down LaunchBox traffic. Sometimes overseas the connection can just be slightly unstable or slower than usual. You could still try a VPN to see if that helps.

Unfortunately this is due to connection issues. I know for a fact at this point that some crappy ISPs are heavily blocking/slowing down LaunchBox traffic. I know at least Comcast does it at this point, and I'm guessing they're not the only ones. I'm not quite sure what we're gonna do about it, but for now, the only real solution is to use a VPN. Comcast seems to slow down LaunchBox traffic at peak times of the day, and I know they're specifically focusing on us because it's not the server and when I connect to the VPN it gets more than ten times faster. I believe this is all due to the FCC's horrible decision to get rid of net neutrality. Anyways, I'm not sure if changing our IP address or domain will make any difference, but I'm going to give that a shot here soon. For now, I would highly recommend ExpressVPN or another VPN solution. That way, your ISP can't slow down your traffic based on what you're doing.

Thank you guys; I just put out 9.7 to fix that controller issue.

Startup Themes vs. Themes.

@Artik We have it confirmed working for several people, so there has to be some kind of discrepancy somewhere. Where did you get that Blazed font? Did you rename the font file from something else? Hold up, nevermind. You have the file path wrong.

I'm guessing that setting the FontFamily on that control just doesn't work, as it specified somewhere further up the XAML tree.

Thank you @spycat; I was not aware of that. Turns out it was an issue with an old plugin that I just removed. Hopefully we'll be good to go now.

Nothing changed for launching games, so I'm pretty sure that's not the issue. Most likely it's some kind of conflict with the game startup screens. Try disabling those to see if that fixes it.

Oic. Depending on the view, the font sizes are almost always set via the name of the TextBlock, or whatever element you're working with. So generally, if you change the name, then the font size will not be overridden.

Beta 12 is out now with culture fixes for the themes manager version numbers, and an updated pt-BR translation.