C-Beats

That you need to stop deleting content and then reposting it. I restored the old thread and moved it to the new location the new one you made was. In the future if you want a topic moved, simply ask.

Can you post a screenshot of what you're seeing in that window?

@The Papaw I changed the call a bit that was giving you the out of resource error so that should be resolved @sundogak I adjusted the logic to prioritize virtual hard drive paths for a given game id Those reporting the plugin popup. Can you guys zip up your plugin folder and send it to me via PM? Faeran and I can't seem to replicate this one at all.

There is a binding in our marquee's that is called "IsActive" (without quotes). If Big Box has focus that is true, if not it's false. You can use this to drive your logic since the primary reason Big Box is not focused is because a game is being ran.

No, we don't play music AND video. You'd have to add the song to the video file you're playing.

This is resolved in the beta already.

It's that time again! 13.15 should be ready for translations. Let us know if you run into any issues. @Opak @Kondorito @Cauptain @Nyny77 @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock @Soomin papa @thewhite

Can let @superrob3000 take the credit for this victory. There is some logic in the startup screen that places our window in front of the window we just launched. Sometimes MAME windows have their window flags set to be "topmost" and when you swap your window to be in front of a "topmost" window YOUR window becomes top most in order for the OS to accurately place it in front. This was happening to our main view and since we weren't really planning for it we never checked the flag and cleared it. We removed the logic that needlessly moved the primary window (since startup window is still being moved to top anyway) and it should correct the issue.

Believe we found the culprit and should be correct in the next beta release.

Thanks for this, I understood what you meant from your initial post. @faeran is now able to produce on his end, but still unable to really see in the code why this would even happen. If we can't work through why we may have to put something like this in place. Really hate just covering up the problem with code like that though. Prefer to take care of the root cause itself. I'll do my best to remember to update this thread when any changes make it's way into a beta.

All games are loaded into the app regardless if they are visible in the app. A hidden app takes just as much time to process as the visible ones on the data side. On the UI not having those images to fetch obviously stops you from wasting CPU cycles grabbing the extra stuff for that game. Overall though I doubt you'd see any performance improvement by hiding a game.

Changing size of both the sidebar (left side) and game details (right side) works in free version. I just tried it myself to verify there were no issues in the theme and all appears to be working.

Looked in the codebase and we do use something similar to this in the startup/pause windows, but not Big Box. Is it possible that another plugin is setting that flag incorrectly on the main application window? I know we have several plugins in the community that do various things regarding where/how the application windows are displayed. I'll keep looking but right now coming up dry unfortunately.

It's because the first game had 3 playable goblins, the 2nd had two, and the third had one. All solid games I used to love playing growing up. Nice to see them getting some love. Never even realized there WAS a 4 or 5

Caching is done off thread, UI operations have to be done on the primary. The two shouldn't really affect each other much. The only "bog down" you should notice is it takes longer to see grid images that don't have the cache already built.

It'd be helpful if you could post the error you are seeing.

It's likely caused by image caching. I took a quick look at Steamy and I didn't actually put the caching progress bar in that theme (like I admittedly should have). In that theme there is no way to see visually in the UI that LaunchBox is caching images.

Tools > Manage > Platforms. Select the platform who's media you want to move and press Edit. In the folders tab point the images to the new location and then press OK to save. LaunchBox will ask if you want us to move the images you already have to the new location. Press yes.

If you tell it to. If you want to just update that one field then use bulk edit to clear it on all the games and then select the "don't overwrite" option

Not related to beta. Was an issue on the web database side of things that has been resolved. You will have to force update your games database to see the new data.

Some emulators have files that are required to emulate your games properly. Most of the time these are what are known as BIOS files. BIOS files are like ROMs of the hardware that are used to emulate the system. That error is telling you that LaunchBox doesn't see the file it believes the emulator requires to emulate your game properly. You should be able to click on the indicator to get the MD5 hash of the file in question and Google it and come up with results as to what it is and why it's needed.

Error is cut off but I assume this is the error you normally would get in Win7. CefSharp is the dependency we have that no longer works on Win7 because of a security patch that was required didn't work in that OS.

I understood what you wanted. Remove the command line argument and reap the rewards. What that command is saying is "hey cut the artwork if you need to in order to make the gameplay area bigger". Without it MAME uses the lay file of the overlay which will show all the artwork but will also make your gameplay area smaller.

Yeah, MAME ROMs need to be launched with the matching MAME version. There are sets out there to correspond to the version of MAME/RA MAME core you're trying to use but all of it is a bigger pain than simply having a set and emulator of the same version. Outside of that you'll be just chasing issues left and right.

The answer to your issue depends on how the theme you're using was created, and how your marquee monitor is built. The first is easy, try moving to default theme and see if it appears better. Second will take a bit more to figure out. Some marquee monitors are just cut monitors that still act like the full size and so the marquee has to be treated slightly differently to make those work. We have compatibility settings in Big Box to assist with those if that's the case.