Jason Carr

@ArcadeCab Ah, no one's brought that up. I suspect that not many people use LEDBlinky with LaunchBox (mostly only with Big Box I would imagine). I'll take a look.

Yes, it should be fairly simple. Look for the "KeyTime" properties; they set the lengths of time. I'm not sure; I think you might need a plugin of sorts since I'm not sure if you can bind directly to a custom field from the XAML. So unfortunately, it may not be as easy as it should be at this point. Someone may have done that already though; at this point, the amazing theme developers tend to know way more than I do in the XAML.

I'm lost on this, but I'm guessing the games are just being filtered out somehow, or are not where you expect. Will need specific details in order to help further. Yup, we will look into that soon, though not before the next official release.

@nathanddrews You can retrieve the code by going here and recovering your license email: https://www.launchbox-app.com/premium/lost-license

@jayjay I know this is confusing; sorry for that, but VideoPath is only used when the video has been set to a custom path (isn't automatically picked up from the file system). Instead, you can just use selectedGame.GetVideoPath(), which will include the default paths as well.

Thanks for the details, @MadK9. I think we'll go ahead with the release though, since those don't seem to be deal breakers, at least. I can look at those issues here soon though. Yes, we can update 7-zip at some point here. I don't want to do it before the next release though, just because it's too late before the release. Wow, pretty crazy. So apparently VLC just has some bugs with Ogg Vorbis. Good to know. Thank you much @kmoney.

Hi Claudio, I don't have a solution for this currently. I'm sure something out there can do it, but I've never done it so I don't really have any good ideas.

Wow, that's crazy. I never would have expected an issue to be caused by the Education Edition, but good to know. Maybe there's a security policy or something that's changed, odd. Still, glad you're up and running.

Hi @Bageena, I'm sorry to hear about the issues. I have heard about this happening once before to one other person, but I apologize that I can't remember the specifics of what solved it. You may be able to find the answer on the forums however, if you can search and manage to find it. If I recall correctly though, I think it had to do with some sort of badly-written software that typically runs in the background that was causing it. It might have been video recording software for AMD or nVidia video cards, or keyboard software from Corsair, or something else that I can't recall. So what I would do is literally get rid of all software running in the background, first by going through the system tray and closing everything, and then by killing anything remaining using Task Manager. If that doesn't work you can try disabling everything in the Task Manager Startup tab, and rebooting. Hopefully that will help you to narrow it down. The only other thing that I can think of that it could be is bad drivers, so if it started happening recently, you could try downgrading or upgrading your drivers.

Heard from @kmoney that on rare occasions, auto-played videos in .Next were still playing while games were running. Beta 21 is out with some added brute force methods to make sure that video playback is paused. Let me know if anyone still experiences this issue, as I'd like to make sure it's fixed before the official release, planned for Monday or Tuesday.

Wow, turns out I *can* replicate it with your data. Unexpected, but may be related to using All Games as your startup view. I've noticed that it works fine if you go to View All Games from the menu. I'm surprised no one has ever reported that before though lol; there may be something else involved with your data that causes it. Anyways, sorry for the trouble, and thanks for following through with all of this. Now that I can replicate it, I'll figure out exactly what's causing it and get a fix in place for it, hopefully early next week.

Hmm, the image you uploaded is 960x540. Is that the actual resolution you're running? That is a bit of an odd resolution, so I suppose it could be related to that somehow. Did you change resolutions recently? Can you try upping the resolution?

I thought about that, but the font is the same font that is used elsewhere, so that doesn't make much sense either. Then again nothing makes sense. Did a Windows update just install or something? Are you on the Windows 10 accelerated updates for beta testers? I just tested on my system with the Default theme and same startup video, and I can't replicate it either. Just wanted to make sure I wasn't going insane. How long have you been using Big Box without this issue? Just in case it is somehow data or settings-related, feel free to zip up and PM me your LaunchBox\Data folder. I can test with that to rule it out.

Try deleting the LaunchBox\Themes folder, and restart Big Box, just in case somehow something got messed up with the theme.

Also try rebooting, though I have no explanation as to why anything would have happened on both machines.

Wow, that's really strange. Idk, maybe it could be the particular startup video? What startup video is it? I have to admit I'm pretty baffled.

Also, what version of LaunchBox are you using? What version of Windows are you running? What are the specs of both machines?

No, I can't duplicate unless it's a brand new issue or something (haven't tested that in particular with the latest betas). Most people use a startup video so we'd have people screaming left and right if it was a common issue. Are you using the same LaunchBox collection on both machines?

Hi @shakex, I've never seen that before, unfortunately. Does it work properly if you remove the startup video? I can't imagine the startup video would be related, but it's worth a shot. Are you using the Default theme?

Nice! Congrats and thanks for the update. If you do end up figuring out which one (or combination) it was, let us know.

I'm guessing either "None" or "Exists" is set to "All" for some reason. What does your Options screen look like here?

Yes, I will look into this soon hopefully; it's on my shortlist, but yes, it's unrelated to .Next. I don't believe this is in OG LaunchBox either, yet; let me know if I'm wrong. I did address the issue with LaunchBox.Next by increasing the horizontal deadzone, which was set to a smaller value in .Next than it was in OG.

Ah, I figured I would miss something with the boxes changes. Beta 20 is out now with a fix for the dividers. The plan is to let this beta simmer today and over the weekend, and assuming we don't find anything major, we'll make it official on Monday or Tuesday. Thanks all for your testing and feedback. Let me know if anyone experiences any crashes or bugs.

Beta 19 is out now with the following: Fairly massive performance improvements when scrolling boxes, especially with a large amount of games. I managed to eliminate the bloat from the theming engine completely by simply combining all of the boxes into a single view, amongst other performance improvements. The double-click glitch on focus should be fixed now; I had to resort to a hack because of what seems to be a .NET glitch, but as long as it works, we should be good from that front. The white line for the keyboard focus has been moved to the correct location on the boxes. Various issues with video and music sound conflicts have been fixed. Let me know if anyone experiences any further issues with this beta. The performance improvements were somewhat major changes, so hopefully they don't cause any new issues. Testing is appreciated.

I just realized that the line is in a strange spot with the default spacing settings (doh). I changed the default spacing settings and forgot to fix the line. So nevermind on figuring that out; I'll fix it. Thanks for pointing it out.