C-Beats

We don't display it in the Edit windows but we do pass a command line parameter to RetroArch that essentially says "Load this core" based on the core you tell LaunchBox to use.

I understand the desire but your examples don't help your case at all. The way the auto-gen playlist boolean logic works is that each unique field is joined with an AND and a repeated field is treated as an OR. Because of that both examples are possible with the current auto-gen system. For example: Developer | Equals | Capcom Genre | Equals | Fighting Will give you a playlist of Capcom fighting games (as requested) And: Developer | Equals | Capcom Genre | Equals | Fighting Genre | Equals | Adventure Will give you a playlist of Capcom Fighting OR Adventure games Series | Equals | Mario Title | Is Not Equal To | Mario Kart Would result in the playlist you are requesting in your second example.

There is a BitBucket ticket you can vote on here. It placed #28 (missing the 20 item cut off) in the last feature poll.

If the decimal part of the rating is above .75 then it gets tossed up to the next star since it is pretty close to that number. That sort logic has been that way for a very long while and to my knowledge we've had no reports/tickets asking to change it. If you would like us to look into taking the absolute value of that data point for the sort I would suggest going to the top of the web page and selected "Help & Support" > "Request a Feature" and enter a ticket for it so we can see how popular that request is.

The executable (.exe) must be in the current user or all users start menu folder hierarchy or have a registry entry in a specific path for that import to find it. It is used primary for games that used to be installed by the OS directly to the Start Menu that were otherwise extremely difficult to locate and import. Some older games used to install this way as well. The reason your example does not get caught is because that is a shortcut.

Windows game importer (as stated on the first page of the importer) looks for games in your Start Menu. Most of the time you will either use the Xbox/Microsoft Store importer (if purchased via that app) or just drag drop the executable for the game into LaunchBox.

There is no current way to run attract mode when Big Box is not the active window/application. We have code in place that makes it impossible as having the possibility could cause issues for any game that uses a launcher (ie any Steam game). Attract mode was never designed to be a second monitor screen saver like you are going for, it was designed to be the attract mode of a arcade cabinet set up (similar to the old arcade games).

Need to make sure of the following: Your drive is always being assigned the same letter (if LaunchBox is not on that drive). If it isn't then the paths won't line up and you'd get that error. Your drive isn't being shut off because of your OS power options. The file in the games application path DOES exist in the path that you have it set to. The location doesn't have a security setting that makes it impossible for LaunchBox to read the directory or file.

<coverFlow:FlowControl x:Name="FlowControl" HorizontalAlignment="Stretch" VerticalAlignment="Stretch" Grid.Column="0" Columns="1" Endless="True" CurveAmount="4.5" CameraZPosition="3.0" VisibleCount="14" PageSize="6" Spacing="1.0" ItemZPosition="1.0" SelectedItemZPosition="2.0"> <coverFlow:FlowControl.FlowTemplate> <DataTemplate> <coverFlow:FlowContext> <TextBlock Foreground="White" FontSize="32" Text="{Binding Name}"/> </coverFlow:FlowContext> </DataTemplate> </coverFlow:FlowControl.FlowTemplate> </coverFlow:FlowControl> Find the FlowControl in the xaml file you linked. Replace it with this. Change size, color, and font as desired in the TextBlock

@nicolasonline Can you confirm this beta push corrected the issues you were having in your wall view?

Thanks @neil9000 @fraganator for confirming the LaunchBox icons are back. @kmoney @BlackSol Thanks for the report. Seems the logic we added to make sure items don't fall off too soon was causing issues so we implemented that fix in a different way for next beta release. Performance should be on par with the first beta release. @nicolasonline Thanks for those clips and XAML. Believe I have track down the cause and have a solution in place for next beta release.

Also those that were reporting the missing icons, can you confirm they are once again showing in LaunchBox? @neil9000 @fraganator @Blitz Mary

Thanks for this. Was able to replicate and have code in place to correct.

To my knowledge no. If you are seeing stuttering thought you could turn down the setting in the options which will make the animations update less often which I would think would make them all appear smoother. I admit though that I'm not real sure what you are experiencing that you believe to be caused by the refresh rate.

Only need to set Opacity in the triggers where IsSelected AND selection active is true and onMouseOver. Should be set to 1. Set Opacity to .45 on the actual control template, not by using triggers.

Opacity changes for the parent element and all children elements. That text is in that border and so should be affected as well. When I get the time I'll take a look. Can't guarantee it'll be right away though. May have to wait until over the weekend. Trying to get the beta squared away at the moment. Let me know if you get it before then.

My bad, I read that post as you wanting to do that with the games, not the index. Not tried it but, but looking at the style I'd suggest trying the following (in the ListBoxItemStyle): Add Opacity property to the border named "Bd". Set the value to the non selected opacity value (.5) In the trigger section where BOTH triggers are true, set the Opacity there to 1

Only way to do different opacities for different items in that view (if using a CoverFactory) to my knowledge is an Opacity Mask, and even that isn't exactly what you're looking for though (though you could make it look pretty convincing). The new FlowContext/Template logics let you do that, but at the moment there isn't a way to rotate items like you've shown in your more recent Colorful theme examples.

Big Box uses a back end called WPF. One important thing to understand about that is that WPF is not designed like a video game. It doesn't render every "frame" or at a predefined tick rate. It only renders frames when a change in the layout has occurred that requires us to re-render the screen. WPF by default should try and match the active monitors resolution and refresh rate. The setting you set in Big Box options sets the tick rate on animations used in Big Box so that you can make them update at the same rate as your monitor to provide smoother animations. It's important to note that animations will TRY and update at that rate, but if it takes your CPU longer than that rate to calculate all the new positions needed during that animation you COULD start to see stuttering that you wouldn't see at a lower setting. It is also important to note that the setting is NOT applied to videos. If the video is a 60hz video it WILL play at that rate and not the refresh rate you set in Big Box.

Those themes are currently causing issues in the version of Big Box you are using. Switch to default and let me know if you still encounter the issue.

Think I have found solutions to both the icon issues many users have reported and the issue still outstanding that @nicolasonline has reported. Would appreciate if you all can confirm the reported issues are resolved in the next push.

The following would be helpful bits of information to have before any one could help potentially identify why you may be experiencing issues: What is your processor? What is your video card? What does your storage situation look like? What type of drive is the image cache stored on? What operating system are you running? Are you up to date with OS updates? Are your video drivers up to date? How many systems/games are in your collection? Do you have these issues with the default theme? What version of Big Box are you running?

Would be curious if others are still having the problem. I know there was a new Windows Update last night and EmuMovies did a server update/restart. Curious if either fixed the issue for anyone else.

The newest beta does make this possible for all Themes/Views but you would need to update the theme xaml to do so, no theme by default does this because it simply wasn't available at the time. Adding the Endless property to the views FlowControl and setting the value to False will do what you want.

Thus far all the logs read the same, that the connection timed out. Not sure at this point the reason you all would suddenly be getting these errors. I have my suspicions that it's related to a Windows update affecting how the LaunchBox client is trying to communicate because the code that controls this process hasn't been changed in a long while. I'll continue to investigate to see if I can find a way to resolve the issue though.