Jason Carr

Sure, that makes sense. It's currently getting the EXE path from the Windows shortcut in the Start menu, so I guess it was assumed that it would be correct. There are numerous issues with the Windows import for sure (due to the difficulty of it all), but the biggest issues are more along the lines of trying to identify what is and is not a game, and what is relevant to import.

Forgive me for my a bit harsher than normal words, @DR9; I was not calling you garbage, but we all know that garbage does come out of all of our mouths from time to time. I appreciate everyone in this community and especially all of our Patrons, but I do tire of the negativity, especially negativity with zero redeeming qualities and that simply didn't need to be said. I didn't find any purpose to the post.

Agreed that would be a win. Hopefully I can get that added in soon. That's actually fairly high up on the poll so it's still planned for soon. Agreed. Should be relatively easy to implement since we already have the settings, so that's planned as well. The reason the DOS importer works so well is because there's a static list of DOS games available that we use as a database in order to find them properly. Unfortunately nothing like that exists for Windows, which makes such a process a million times more difficult. Here's a tip, if your post starts with "I'm gonna get flamed" then don't say it. Save us all the cancerous negativity. Development is indeed ramping back up, but it's not any fun to read garbage comments like this in the process.

I actually haven't heard of the clr.dll file causing any issues (at least not recently that I can remember), but it makes a whole lot of sense because clr.dll is a crucial part of .NET. Really it just suggests that .NET crashed. That exception code is an Access Violation, which basically means the same thing. At least that narrows it down to .NET crashing and not DirectX or something similar though.

Hey all, the first 7.12 beta is here with the work from the live stream this morning (and my work to wrap things up). I've also re-upgraded to the .NET Framework 4.7, so we should get those performance improvements back. Here's the change log: - Improvement: Checkboxes on the import wizard now remember their settings for each import (where relevant). Selected image types are also remembered. - Improvement: Upgraded once again to the .NET Framework 4.7 (had previously reverted due to some minor end user issues with .NET 4.7). Hopefully all issues are ironed out by now; if necessary, you will be prompted to install the latest .NET Framework when upgrading. Going forward, @Vlansix is working on adding retro achievements, so that is planned for this release. I'll be going through the rest of the poll items next to see what's next for me to tackle.

@cleverest I'm sorry to hear about those issues. I think @lordmonkus has probably done as good of a job as possible trying to troubleshoot it; seems like a really nasty issue. The error message that I saw a page or two back is indeed an error that I have on my list to fix, but it doesn't crash LaunchBox; it just comes up on very rare occasions for certain people, so it's most likely unrelated. As best as I can tell, we're probably dealing with one of the following: - A .NET bug that is somehow specific to your hardware or drivers - A hardware issue - A driver issue Or something similar to the above. Unfortunately that doesn't really help us solve this, especially since I'm not going to be able to ever replicate it without having your specific hardware. So we're pretty much up a creek here, sadly. I wish I had a solution but I'm not sure what we could do to solve it.

@Smannesman That looks to be some sort of odd data issue; currently looking into it. Can you zip up your data folder and PM it to me? That way I should be able to replicate it. Thanks!

The three lines button in the top left guys, then Manage Folders. Just put out an update that makes it more obvious.

Lolololol. Close guys. Sort of. I hope everyone is as excited about it when it hits as I am.

@tayda112 I just deleted your post because we don't want to share licenses publicly. I'm confused as to what you need, but please email us at support@unbrokensoftware.com and we can help you out.

Just sent you an email.

@ItchyProphet I assume you've been taken care of now? Let me know if you still need help.

Responded in the thread.

Yupppppp.

The release is out folks! Let me know if anything blows up.

Wow! Congratulations @AFaustini. Thank you both; I'll get these both in before the official release goes out this morning.

@rrichter We'll need a lot more information in order to resolve the issue, such as the exact error message that you see.

Yup, this was fixed on a previous beta. I have heard about some issues with full screen VLC video playback recently, but was unable to reproduce. It makes sense that it might have something to do with webm though, since I don't have any in my collection. I won't delay the release over this, but that is good to know, at least.

And beta 21 is out lol with fixed Gif support.

On second thought, I looked into it and it was really easy fix. So yet *another* new beta is coming lol.

Yes, this is a known issue. Gif images will not show up in Big Box unless used as animations for themes. I might come back to this soon, but I don't consider it to be a major issue in the mean time, as gifs are not commonly used for anything but animations (and it doesn't really make sense to do so as compared to png or jpg images).

Alright lol, one last new beta is out that finally fixes the video issue that @LukeArio was having; it was apparently related to gif images, believe it or not. We're good to go for release tomorrow as far as I can tell.

So! Thanks to @LukeArio sending me his folders, I got this figured out finally! Believe it or not it had to do with having a gif image for certain games. I had re-built the image loading mechanisms for 7.11 to make them a lot more performant, but the new mechanism does not support gifs for the main images, which was in turn causing the videos to never load. I'll have a final beta out to fix this shortly.

Sure, that makes sense. If you can send me your data folder in a PM, I'll give it a test. I'm not quite sure how data could be affecting video playback, but it's worth a shot.

Thank you all; I have all of these updates into the latest beta (including @Opak's update from after the last release). Still planning on releasing the official 7.11 tomorrow morning.