C-Beats

@Timber-eXoProjects Correction was pushed to the first beta build of 13.15

Thanks, it does appear to be the same issue I had corrected, you're using the middle configuration where I usually use the first step one. Sounds like I need to track down what I did and see if I can get it to work on that setup as well. Thanks for the video, very helpful.

You can change your sidebar filter to "Region" and then select by the region you aren't wanting to include. Then click a game in the grid and press Ctrl-A to select all and then delete to remove them.

You can start a shut down directly from the Big Box interface via the System Menu

Can you describe what issue you're still seeing? I've not seen any of the previous details stutter I saw in the past before the change and I use this theme almost daily both in test and production environments.

It'd be your AV not your firewall. They tend to block that DLL sometimes because it contains chrome which they determine is dangerous. Once it's off run the installer again over the same location and you should be good to go.

Just NEVER satisfied are ya.... Thanks for the heads up. I'll take a look and see what we can do to smooth out these edges.

@sundogak Requested RPCS3 changes are in this push. Can you confirm you're seeing better imports?

Thanks for the heads up. We identified an issue on the server that made the new DB files not generate. I manually fired the process to rebuild these and so should be able to update your DB file and see it now. We've also repaired the issue that caused it to stop generating those files automatically so you shouldn't run into this moving forward.

It'd be nice to get to that point eventually, we're still considering how best to do that in the UI without it getting out of hand. Especially for users with a large number of platforms.

Currently there is no way to push auto-imported games to any other platform.

Can you share what entry you're seeing this with?

yeah, really auto-import should probably be turned off for that platform in general. I'll take a look but no guarantees it gets changed in this version.

The plugin's needing updated thing was a error in our server data. I've corrected that and you should see that resolved @Buccaneer @sundogak (and others). No need to update to see that change.

We get the version number from the app itself. If you run command line against your app "pcsx2-qt.exe -version" (without quotes) what version does it report itself as?

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.