C-Beats

@zugswang Your reported issue should be resolved this beta @betikito84 RetroAchievement scan should play nicer with M3U files as of beta 3 @kurzih Model setting overrides can now be set in bulk edit as of beta 3.

Glad to hear, thanks for following up.

Isn't in the plans at the moment. Honestly hadn't even considered that people may want to do so until you mentioned it. I have the idea written down and will keep an eye on it as we move forward.

I'm not real familiar with the app, but Pinball FX was made specifically to accept command line to launch to a specific table. If that app isn't built to allow for the same thing the closest you're going to be able to get is to get an ahk script that automates the key presses once the app is open to get to the correct slot/game in the application.

Close LaunchBox, then navigate to \\LaunchBox\Data\Settings.xml and open that file in a text editor. Search for "<ControlsBarHeight>" (without quotes) and set that value to 56. Save the file and close it. Then re-open LaunchBox.

It's always cool to hear where potential interest may lie for our product to expand into. Unfortunately a lot of the desired platforms require a complete re-write to develop to as far as I'm aware so wouldn't be something we can quickly hop on and get done, but it's always nice to know what options are available. I personally would never have even thought to look into emulation on modern consoles. I've not owned any since the Xbox 360 and so not real sure what is going on in that space anymore.

BitBucket is having issues on their end. We are working with them to attempt to resolve this issue and will let you all know when we get it sorted out.

That file is generated at runtime using data from MAME directly as well as a few INI files. You don't ever actually download it.

Next version of LaunchBox is on .NET 6.0 and is in open beta at the moment.

Should be able to press "Windows+R" to bring up the run command, then type explorer and press enter to get the desktop to show again. If you can't do that, restart your computer in safe mode then try it there (Not sure if the shell option fires in safe mode or not honestly).

Steamy is a LaunchBox theme not a Big Box one. If you're manually installing it the theme goes in the LBTheme folder, not Theme.

Those filter views only have text view that I'm aware. You could potentially create your Platform Category view to look like the view you're trying to use and then you could select any of the platform views.

Easiest way is to go platform by platform. Select all the games in that platform (CTRL+A works) and then go to Tools > File Management > Change ROM Path for Selected games. A wizard will come up asking you what root folder the roms are in, point it to the new location and let it do it's thing. If you're feeling risky you could also just use string find and replace on the xaml files located in \\LaunchBox\Data\Platforms. If you do this make sure you have a backup of your files and are doing it with LaunchBox closed.

I don't really have any answers for these questions. You could reach out to support@unbrokensoftware.com and express your interest there and leave any questions you need/want answered and some one that can actually get you real answers can respond to their best ability.

Typically when we see reports of items being "moved around" automatically the user has files in the \\LaunchBox\Data\Platforms folder that don't belong. For example Skraper tends to put "-backup" files in there and it causes issues like what you're describing.

You can turn debug logging on in Tools > Options. Files are then generated in \\LaunchBox\Logs

We don't actually tell the application being launched what monitor or orientation to launch in. Do you have a plugin running that may be causing this? I know we do have some on the forums that change how/where an app is launched.

You definitely have something going on with your machine if closing the app doesn't revert any lag your experiencing. LaunchBox doesn't leave anything open or running once the save event is done (which should only last a few seconds after closing the app) and so there would be nothing to affect your PC. When LaunchBox is open you can launch Task Manager and see if your machine is bottlenecking at all. You can also then close LaunchBox and make sure the process closes out (again it won't be removed from the list until the save event finishes, this shouldn't take longer than 60s, if it lasts longer let us know).

This hasn't been changed. We can potentially take a look at addressing it if time permits.

The runtime needed for 13.2 is .NET Core 3.1 Desktop Runtime. We've noticed in Windows 11 that the OS doesn't properly report that the runtime is installed if installed after a newer runtime. Typically if you run into the issue you need to uninstall the .NET Runtimes you have and then install them again from oldest to newest and then restart your computer. This is one of the reasons we decided to change how we distribute the app from 13.3 onward.

Company is US based. We all work remote and the company itself doesn't have a central physical location.

Yeah, the documentation should be up to date. I was thinking it may be possible to pass the URL to the "VideoPath" property of the control.

All default controls and logic in both apps use local videos only and don't stream videos from the net at all. It MAY be possible to pass the URL to our newer FlowVideo control, but I've never tested it to know if it works, and what types of URL's it would or would not play nice with.

In Tools > Options there is a section for turning items off/on in Game Details. You need to uncheck the "3D Model" item.

Well something is going on because that isn't the right size for 13.2 DLLs. Can you take this file and the installer you have and upload both to VirusTotal.com and let me know what hash you get for both files? Seems for some reason you may not have the correct files in your directory.