C-Beats

Simply stating that we don't have much control over what is being used. To be honest I've never looked. It would also greatly depend on hardware and so my experience probably wouldn't line up with yours. Some things you could try are to use bigger grid images to see if it lessens the load. Could also swap to List View and see if it decreases. One thing to note is that any resource sitting on the GPU I'm fairly certain is released or offloaded once the app is no longer active and so shouldn't have much impact on your ability to play games launched from it.

We have been actively developing a process that automatically imports and manages this connection. It isn't complete just yet but we are very close. Once implemented the process will handle this automatically.

Norton is far closer to malware than it is a valid antivirus software. Windows Defender anymore is far more accurate than Norton without all the spyware and adware that Norton embeds in their software. I'd seriously consider removing it.

We don't have any code we run on the GPU. WPF does utilize DirectX to render the app which will use the GPU when possible. How much really depends on what all you have visible. We really don't have much control over how the runtime utilizes that as it's all managed by the .NET runtime and isn't called explicitly by us.

Nothing has changed regarding views in Big Box in a very long while

I've not used the MAME core but from what I've seen reported on the forums in the past certain controller issues are a known issue with that core as the core was a bit of a rush job done by some one outside of the MAME team and the RetroArch control scheme tends to clash with the MAME control scheme quite a bit.

A code change is required to correct this issue. It's already been made internally and should be in the next release which we hope to have out fairly soon with some other bug corrections.

@Orionsangel If you select the game you're seeing this issue with and press F5 does the image re-appear?

@Jabb3rJaw I'd verify you don't have any auto-hide features enabled in Big Box like "Hide Games Missing Box Front" that may be making it so all the "games" in that platform are hidden.

@CriticalCid @Krakerman I was able to find a bug in the code that could cause a threading issue loading the MAME.xml metadata file that could be potentially causing your reported issue. The code has been in this state for over a year though and so I'd assume some changes in 13.6+ caused the threading to execute on different cores and brought this issue to light. I have the code corrected internally and we should have a beta out fairly soon that you can test against the change. A work around for now would be to go to Tools > Download > Force Update Database Metadata and run that before running your MAME import. If you run it manually before the import the potential thread clash shouldn't be possible and you should be able to import as you would before.

There is a Manage Installations section of the context menu within LaunchBox that should let you pick which version you wish to install. I believe we also added that functionality to GameDetails in the Default theme of LaunchBox with a drop down next to the Play/Install button.

I'd verify on the first page of the Edit Platform window you don't have that platform hidden in Big Box platforms view.

Are you still seeing this issue in LaunchBox 13.7? Iff so could you provide an updated error print out from that window?

I'm going to assume not given the description, but are you running Big Box as shell? Is about the only reason I could think of for any difference. LaunchBox and Big Box fire the exact same code when launching a game so there being a difference between the two doesn't make a ton of sense to me.

@RavenDarhk Sounds like you may have had an overzealous AV get in the way of the 13.7 install. First step I'd take is to run the installer again over your existing install (making sure you aren't pointing it to the \\LaunchBox\LaunchBox folder @Retro808 is referring to) and see if that corrects the issue. I'd take a look in the \\LaunchBox\Core\ and make sure that you have both a LaunchBox and BigBox .exe and .dll file. The error reads like one of those 4 files are missing which typically happens when an AV quarantines the files.

Do you have multiple games with the exact same name in MS-DOS?

You need to leave those extra characters in as it tells LaunchBox which of your "Super Mario World" games that image actually belongs to. Without it they will all attempt to use it.

Moved this post from beta thread as it's unrelated and should be it's own post

Thanks for confirming. Bout to give some one an early AM panic attack! lol

Eclipse theme has a lot going on in it regarding plugin use and out of the box solutions. I'd first revert to default theme and see if you still encounter the issue or not. Where the error stack trace is pointing is that something isn't able to load correctly on startup. If you don't already I'd also enable debug logging via LaunchBox's Option menu. Then see if there is anything in that log that would help explain what is going on. COMPLETELY unrelated, but how did you get your error form to look like that?

This should be corrected in the beta already. Are you still seeing this error pop up in the beta build?

LaunchBox doesn't really care about what files you hand it, so should

This is intended behavior at this time. The idea being that we want the app to get you up and running as quick as possible with the artwork actually used in the app by default without bloating out the hard drive space required for a lot of media you may never even see or look at.

Beta should correct this issue for you. To get the app to open correctly open the file \\LaunchBox\Data\Settings.xml in a text editor. Look for a line that starts with "<EnableAutomatedImports>" (without quotes) and set the value to false. Save and close the file, then open LaunchBox.

Could you update to beta and let us know if you are still having the error? It is related to arrange by settings, but no one on the team can replicate. There have been other changes related to similar issues in the beta build and I'm curious if that corrects things for you.