faeran

This would more likely be caused by a change to Windows, Acrobat, or another program that adjusted your PDF file launching settings.

The first two things that pop into my head is: Make sure the manual still exists. Edit the game and check the manual path. Check file explore that the manual file is still there. If it is, then it could be your default PDF viewer. LaunchBox just tries to open the file and it lets Windows choose what to do with it. It's essentially the equivalent of trying to open a pdf file directly. Check your Windows pdf default app setting.

Make sure you went through the registration process here first: https://gamesdb.launchbox-app.com/account/register It's a different registration process than the forums. If you did and you still don't receive a verification email, hit the Contact Us link at the bottom of this page and reach out to support.

It's a bit unclear what your issue is here. Are you having issues registering for an account somewhere?

That's the text games view. If you were hoping for a different view for Game Gear it probably means you have turned on in your options the ability to have separate views per-platform. Set a mapping to switch views (if you don't have one already), then when you are on the game gear view, press the switch view mapping and choose the view you are wanting to use for Sega Game Gear.

Do you have a screenshot of what that view looks like to you?

Yeah, we've talked about it internally, but that requires a good amount of dev time, and then time to brew and see how it plays out. Then probably a good amount of tweaking. That may be one direction we want to get to eventually and is definitely on the table for future revisions of the database.

Yeah, one game one platform. Could just manually duplicate the games between them, since it's correct for them to be in both platforms, but I don't think that's the smartest answer, but it's one the community could do in the meantime. We'll discuss internally how we can more handle this situation better so things don't just break down due to a decision made by the community.

At first glance it looks like something may have happened to the Metal Slug game entry that used to be under the Arcade Platform. The one you are linking to @neil9000 seems to be under the SNK Neo Geo MVS platform, which would break future scraping of this game for anyone importing into the Arcade platform. It's possible someone moved the game to the different platform at some point, which would break scraping in this way. We'll investigate this and see what the best way moving forward will be. In the meantime, @Zodiark12, you'll need to switch the Platform to SNK Neo Geo MVS, then do the Title lookup. Once you link the game up with the ID, switch the Platform back to Arcade, and press OK.

Based on what we are seeing with those, it looks like it's just taken that long for your change to get enough approvals. Maybe a slower month than normal, or potentially more skips than normal.

For inside of the wheel, check out CustomImageType inside of documentation.pdf For outside of a wheel, you would use a binding like the game's title or the game database ID, and use that inside of an image binding, combined with stringformat to point towards the location of your images. something like this: <coverFlow:FlowImage ImagePath="{Binding ActiveGame.Title, StringFormat='LAUNCHBOX_THEME_FOLDER/Images/Games/3D Cart/{0}.png'}" />

It's not. At the time this theme was created, it wasn't possible to create themes like this inside of the CTC. You'd have to dive into the code to edit it.

It depends on what you want to use the image for. Do you want them inside of a wheel, or just displayed somewhere on the screen?

Are you able to provide specific examples of changes you feel are stuck in the system? We'll take a look and see what's up.

If your files are marked with a region, LaunchBox will import that data into your library, and you can filter by it in a number of ways.

No ETA at this time, but it's on a long list of items to internally discuss and eventually tackle.

Not quite again. It's still on our long list to tackle, along with other database related items to clean up. Just know that it's not as simple as removing it. Work will have to be done to make sure there's no unexpected consequences.

In your specific scenario, you would want to set up Steam in LaunchBox and make it import installed games. Then take your Windows shortcuts, or the game exes from other sources and drag/drop them into LaunchBox. Just make sure the files are named in a way LaunchBox can consume them: Game Name (other information)

It's an error. You'll end up getting the full year.

If I remember correctly, then the difference is mostly seen in the Platform Categories section. Imagine you have the following tree: Sega Genesis Action Platform Name would read: Sega Genesis Action Nested Name would show: Action

Check inside of BoxesContentView.xaml. It should all be in there somewhere.

This is not currently possible in the Android version.

We'd love to make this happen, but after investing a bunch of time into this emulator, there were a number of key factors that would stop this from happening. Cult lists out some of them in his post. We'll definitely try again if anything significant happens with this emulator that could potentially solve them. If anyone knows a dev there, we'd love to talk to them to see if something can be done. Thanks for the feedback. Going back directly to LaunchBox usually requires the emulator itself to have some kind of exit hotkey or exit option. I haven't checked yuzu specifically, so you'd have to dig around their settings and see if they have one. Thanks for the feedback. We will definitely look into some of this for future updates. We'd love to better support custom emulators and allow users more freedom with setting them up. For RetroArch in-particular, we'd just simply love to provide users a way to type in or somehow choose their own core that we may not have gotten around to adding yet. Good news about Citra, we have that on our list to take a look at.

Beta 2 is out with the following: Various fixes to the theme engine (introduced in beta 1) have been made The theme document located in LaunchBox\Themes\Documentation.pdf will now always update to the latest version on app startup