faeran

After you run through your organization of your files, go into LaunchBox, select all games on a platform by platform basis and run Tools > File Management > Change ROMs Folder Path for Selected Games for each platform that needs it.

So, here's an example of what I'm referring to, just know that this is not a completed code, but it gets you a bit closer. Then you can edit it and style and position things the way you want. <coverFlow:FlowControl.FlowTemplate> <DataTemplate> <coverFlow:FlowContext> <Grid Background="Transparent" Height="300" Width="600"> <Grid.ColumnDefinitions> <ColumnDefinition Width="1*"/> <ColumnDefinition Width="1*"/> </Grid.ColumnDefinitions> <coverFlow:FlowImage Grid.Column="0" ImageType="Backgrounds" /> <TextBlock Grid.Column="1" Text="{Binding RelativeSource={RelativeSource FindAncestor, AncestorType={x:Type coverFlow:FlowContext}}, Path=DataContext.Title}" /> </Grid> </coverFlow:FlowContext> </DataTemplate> </coverFlow:FlowControl.FlowTemplate>

Well, it doesn't look like you wrapped the items in a Grid, or set up the Grid Columns to get what you are after. I'm also going to guess you'll need to wrap the image in a container that's a static size, or else you'll end up with results you were not expecting. You may also want to format the TextBlock. If you need some help on how to utilize a Grid, there should be lots of examples in different themes. Also since it's basic WPF, google would definitely have a wealth of information.

It would be more like this: <coverFlow:FlowImage />

I feel like there was some attempts to make this work back in the day that didn't pan out. Intellisense should inform you if something in the code looks out of place and needs fixing, it's one of the reasons I use VS. I really only provided the textblock code that can be used inside of the template, since it requires some extra stuff in it to make it functional. You'll need to use a FlowImage to get the clear logo back, and use a Grid with two Columns to get them next to each other.

Don't think this has ever been possible unfortunately, although I still like to use Visual Studio for its intelliSense. This is possible using a FlowControl item template. I feel like you can see an example of this inside of the Documentation.pdf which is in your LaunchBox\Themes folder. You can add a textblock that looks something like this: <TextBlock Text="{Binding RelativeSource={RelativeSource FindAncestor, AncestorType={x:Type coverFlow:FlowContext}}, Path=DataContext.Title}" />

Each game inside of a playlist would take on the default properties of its platform. For example, if you had a NES game and a SNES game inside of the same playlist, the NES game would show the NES default box while the SNES game would show the SNES default box.

Not at the moment. The next beta will include a way to see long names where the title games trimmed, when you mouse over the title.

https://forums.launchbox-app.com/files/file/2467-platform-boot-videos-theme/

Something to note. If you are using videos from EmuMovies, the fade is in the video itself.

If I'm reading this right, I don't think you had to do anything as elaborate as this (although it's fine if you want to keep it this way). Instead, you could go into your main RetroArch's Associated Platforms tab, type in the name of your Neo Geo platform, choose the core, and uncheck the Extract ROMs option. That should work as well.

Yeah, you'll need to do this. You can essentially delete all the folders inside of the theme's Views folder. That should solve it for you with the custom theme. Basically these 3 folders, delete theme: LaunchBox\themes\[custom theme name]\Views\Wall2GamesView LaunchBox\themes\[custom theme name]\Views\Wall4GamesView LaunchBox\themes\[custom theme name]\Views\WallGamesView The theme is created in a way to utilize the original box artwork and you are seeing what you are seeing because you are chosen to use the artwork from SteamGridDb.

There are things you can do to help you get started with Big Box theming, like reading the documentation that's in your themes folder: LaunchBox\themes\Documentation.pdf The documentation will give you all the available bindings you can use to add to themes. The file you are looking to add bindings to is called GameDetailsView.xaml (most likely), and can be edited in any text editor. That will hopefully give you a good place to start. Good luck.

@Thunderbird1400. Couple things it could be related to: You have a symbol in one of the folder names that leads to the LaunchBox folder. You have LaunchBox installed in the root of a drive. Something to note is that this is happening due to something very specific going on on your machine. One thing you can try and install LaunchBox 13.6 in a new location and see if it gives the same errors. That could help narrow things down based on the results of that test. If you can start a new thread with your findings under the Troubleshooting section that would be much appreciated.

RetroArch usually has good defaults, especially when dealing with x-input. It's one of its strengths. So, most likely you won't have to alter anything unless you dislike any of the defaults they've set up for you. But yes, you can go through this process with the controller you have right now and see how well you do.

No matter what theme you are referring to, you need to turn on View > Media > Auto-Play Videos

And you've done this multiple times? If you have the ability can you post the full crash report? Most of it is being obstructed.

Under Options, in both LaunchBox and Big Box, there's a controllers section with an option that allows you to enable/disable this. Yes. Not sure about all emulators, but they normally adhere to how Windows does things. Like in RetroArch, you aren't configuring a specific physical controller, but configuring the controls for "player 1", then that gets applied to whatever physically controller is currently registered as player 1 at any given time. That's a good idea, it will definitely make things easier on you.

Sounds like your computer may have blocked some important app files during the install of 13.6. If you run the 13.6 installer overtop your current build, do you still see that error again?

The way Windows works by default (and most consoles for that matter) is that the first controller that turns on gets marked at player 1, then the second controller that turns on gets marked as controller 2, and so on. So, if you just happen to turn on your 8bitdo controller first, it becomes player 1 for that session. LaunchBox and Big Box allow you to pick a specific controller to navigate or make all your controllers have that ability. Windows likes x-input devices (which I'm pretty sure most current 8bitdo controllers have support for). I feel like the PS4 controller needs a third party program in order to get it to run in x-input mode, something like DS4Windows. If you are looking to purchase a controller in the future, it becomes a lot easier if you purchase one that has support for x-input out of the box. There are also third party programs that can force a specific controller to always be a specific player, or to make many controllers all the same player (something like x360ce).

A few things to note: LaunchBox will only import supported storefront games that you have currently installed If you delete one of these games from LaunchBox, it won't ever be automatically imported again There's the option to turn this feature off, like C-Beats mentioned Anyone who upgraded to 13.6 will have this option off by default

What you are running into here is due to MAME and how their romsets function. LaunchBox has no way of knowing which type of romset you have imported, and there's a 66% chance (actually probably more) that the game you are exporting will be missing dependency files that allow the game to run. MAME is not essentially always 1 game = 1 file. Depending on the game, and romset type, it could range from 1 file = many games, to 1 game = many files. To get around this, your entire set is exported to make sure all games function. An exception here is your CHD files. Depending on where you have your CHD files located, it's possible that LaunchBox will not pull those over, and you'll need to manually place them in the correct location on your Android device. Something to note is that current romset versions of MAME on Android devices is hit and miss as there's no official MAME app on that platform. Export/copy ROM files will run into similar issues, however I'm pretty sure it will allow you to move files from it, but judging by your romset size, it will break a lot of the games by doing so due to missing dependency files, so I would watch out there.

This was changed before release. The tooltip will now only appear if you have View > Show / Hide > Text on All Games disabled.

Steam games have undergone a foundational change to the way they are matched to our database. We have a number of phases planned to get it all deployed, and at the moment we have deployed phase 1 which stopped incorrect matches from happening. More work is needed to get through the remaining phases, which will solve what you are seeing here. Most of the remaining work is database related, so best I can say is, it's coming

Thanks. Looks like I missed a visibility binding there. I'll have that corrected when the next beta comes out.