C-Beats

Thanks for the heads up. I believe you can use the files in the latest beta installer. I let the team know the links are down in the meantime. I honestly didn't even know they were they I just was continuing the trend of pinging everyone wasn't really sure how Jason had it set up before then. If you have problems with the one in the installer or it doesn't work with the process flow let me know and I can manually get ya all the files.

Tried to give ya all a well needed rest between releases, but alas we need you all to once again rise from your slumber and heed the call. Translations are ready! @Opak @Kondorito @Cauptain @Nyny77 @dukeemu @cyanjiang @Just001Kim @MajKSA @gamehacker @alexposad @k_kutsugi @Bardock @Soomin papa @thewhite Once again a big thanks to ya all as well for coming to our aid.

Hey now! We just do what you tell us!

It's likely you're changing the global setting and not theme specific setting so it isn't actually changing anything. It's easier to bind a key/button to "Change View" and then you just go to that view and press it and select another one. If you have default settings set it'll remember that view for that platform moving forward so you should only need to do it the one time.

Would help others to answer your question if you showed the syntax the BAT files are using to launch the emulator/rom

This is saying we can't save the dolphin integration plugin to the plugins folder correctly. Path tells me your running thing over a network drive and is likely causing the problem. I believe we have this resolved in the 13.22 beta but I'd have to double check.

What binding did you use and what view file were you messing with?

No I've never had the desire to use it as I don't really like/use most of Steams features. Is why I said if there is something I'm missing in the equation feel free to let us know and add feature requests for the bits you really hoping get into the mainline application. Some of what you mentioned I didn't even know Steam had at all let alone for non-steam games. This is why the feature request system is so vital. You can school us devs (something I'm not ashamed I need fairly regularly) and get us the information we need to figure out how important this is to the community and why.

Yeah, I feel pretty confident that isn't going to work anywhere. My plugin I use on my own personal build does this so let me check how I hooked it up. I admit I may have use some undocumented stuff to make it happen so I wouldn't get my hopes up too much just yet.

Yeah you had the right call but if that's what your file looks like you don't have any parent relationships. Need both a parent and a child identifier for valid parent relationships. You data file only shows the parent in each. I thought we had a way to manipulate parents via plugin code but not seeing the call to do so.

In app you'd just check the check box for everyone parent you want. In the plugin you have to add a parent relationship to every model you want it applied. I'd have to look at remember what the interface is called.

It'd be a rewrite, there would be similarities to our current offerings but we'd use it as a way to fix some core issues in the codebase and app processes. It'd have all the things people love about the software but be done in a way we move forward with it a bit easier than we often can in the current apps. Because of this I doubt it'd look like a 1:1 exactly to anything we currently have and more like a mix between all 3.

Even if we come to Linux it won't be as a distro. It'll be as an app. You'll have to settle for close enough I'm afraid ;D

To my knowledge there isn't a stable way to get the app working on Linux. There are too many Windows only third party dependencies.

Typically you just let LaunchBox download/install it for you via the import. If you're using the Add emulator you pick the emulator in question via the drop down and all that information should fill in for you. There is also a download button in that window that appears for emulators that are supported and it'll dl and then check that the default settings are in there.

https://forums.launchbox-app.com/files/category/4-game-media/

Yeah, isn't really a zip issue, it's that your files are named poorly and you have a double extension on them. If you'd like I can give you steps on how to import them as in and then clean up your data files so that you can run the download metadata/media tools. I can also say with most certainty no code changes are coming down the pipe in the foreseeable future to really address this.

I made sure the team was aware. Thanks for the report

Things like what the file name is of the zip vs the file you see working. When importing the zip the file if you go to the game and enter the Edit Game window in the upper right do you see a GamesDb number/link showing that it's associated? What image are you seeing show? What options are you using in the media select page? Do you have the media limit set?

Yeah in Big Box settings view there is an image cache section of the menu. In there should be a button lets you clear platform images from the cache and regrab them. It'd be the first thing on the list of things to try.

I was referring more to the global setting or "Desktop Layout". Regarding per game you're likely right in that you'd have to do that. Not really sure I understand why you'd use Steam though and not the emulator. For standalone games there are several tools out there that can remap controller inputs and have it detect games to change the layout. I use x360ce in my cab but I'm sure there are other/newer contenders.

Not even sure how you'd get the code as is to compile. Where do you define "dataManager" variable at you are using in the for loop? Also if you want the code to wait and not release until the save is complete you need to pass true to the save function. You also only need to do it once after the for loop has completed, not after every game.

Scraping tool doesn't even look at the file or file path to determine what to grab so I'm not entirely sure how you came to this conclusion. If you have solid repo steps using the Help & Support > Report a Bug link at the top of the page with steps on how to get this bug to show and the team can look into. As of right now I suspect the cause is something else entirely though.

I can't speak for the rest of the team but I generally have the forums activity feed up and refresh it whenever I'm waiting on a build to finish. There's very little on the threads I don't at least know is being talked about. I saw the discussion on this thread but don't have much to really add. We made the plugin system so that requests that sit pretty far away from our development path can still be completed by dedicated individuals willing to take the task on for themselves. This plugin is one such use case. I don't make decisions about what does or doesn't make it into the app so don't take the following as "set in stone" This plugin fills a niche that sits well outside of anything I could ever see us adding into the application. I'm not sure why we would build a feature into our front end to inject our data into another front end / storefront so that you can use that instead. You can utilize Steam controls without adding games into Steam so I'm not really sure what we'd be helping you with regarding that setup/configuration either. Also as the plugin dev has found third parties change crap often so we wouldn't be able to consistently give a quality service related to it with the way the product is currently built. As we move to make more and more things tied to plugins we can update outside of the normal release schedule that may deaden some. Even now EA imports are broken and took me over a week to find a way to get them working again (be on the look out in next beta) and that's a function integral to OUR front end. Having to do that all for a niche use case in another frontend/game library software just doesn't sound like the best use of time and would greatly distract from features and improvements to OUR product directly. I do admit though this plugin has grown quite a bit since it first broke on the scene so I may not be understanding the full desire of the people using it, which is why we often suggest you put it in a feature request that does a good job condensing the 44 PAGE thread into something a bit more easily digestible format to work as a TLDR for those deciding what to build and when. This is why we love our plugin dev's. No one wants to be told "NO!" and these fine folks do a great job delivering a lot of more niche features and functionality our small team just can't really justify the time on (whether we want to or not). It's always nice to see the community banding together and helping each other out in ways we just don't have the bandwidth to do ourselves.