C-Beats

Thanks for the detailed step by step @Fursphere I'll sit down with it and see if I can replicate at all. It shouldn't affect anything, but so I can get the test as close as possible, were you launching the games from LaunchBox or Big Box?

They have changed their API and send both. We've just opted to match the scoring system they've chose to adopt on their website. We can look into it changing it a bit down the road, but last I knew the softcore score was something they were debating eventually removing. They already don't really support them and so until we know how secure that scoring system was we opted not to change to showing it (or a combination of the two)

As of right now the Sort Title is the only way to order the items in that view.

This is a Direct X error thrown by your video card. Typically happens when drivers are out of date of an app corrupts your video card buffer and causes unforeseen issues. Vet your video card drivers are up to date and then restart your computer and you're usualy fine after.

The app doesn't "install" the runtime. It's just placed in the core folder with the rest of the dependencies and is loaded from disk to make the program function.

The binding is in Game Details and allows the theme to respect the setting to use or not use 3D models in the Game Details view. Faeran requested it be added so he can make Big Details respect your settings and hide the model if you've disabled it via Options

I personally use x360ce in my cab. I didn't have the issue you are experiencing but I needed it to get the controls to work the way I wanted across all the games I wanted to play on it. x360ce will be able to map all your inputs to a virtual Xbox Controller that the app can see and use and should fix your issue. You also have the ability to set up per-app configurations to assist you should you run into any issues with the games/emulators you want to play with your cab.

Are you getting any error messages pop up? If so can you post them? If not can you do the following: 1. Shut down Big Box 2. Open LaunchBox 3. Go to Tools > Options > Debugging and makes sure debug logs are enabled. 4. Press OK to save options and then close LaunchBox 5. Open Big Box, let the screen go black then kill the process 6. Navigate to \\LaunchBox\Logs\ and post the latest file in that folder here so I can review it.

I reached out to @JoeViking245 to ask if he saw any issues with the migrations in his plugins and he didn't have any with his plugins. Not saying that means we won't with ANY but as of right now I believe plugins should transition fine, they just won't have any benefit add in the move since they are using old frameworks. A user would also have to make sure the 3.1 runtime was installed to use the plugin and that runtime will no longer be distributed and installed with LaunchBox installation so as we move forward more and more users would have to take extra steps to use any plugin still on .NET Core 3.1

Yeah, do you. If you're happy with the experience not going to stop ya from doing it. Glad it all working out so well for ya.

Glad to hear and apologies you had to wait so long for the correction.

No that line is related to the RetroAchievements leaderboards found in LaunchBox and Big Box that you see when viewing your achievement profile.

You obviously can't manage your collection in it, but for simply navigating to a game to play Big Box would play far nicer with that device than LaunchBox will.

Basically when enabled, any time one of the fields we are syncing get updated in your build you send the data to our cloud. Then when another install is syncing it grabs that data and applies the changes locally. For example if you have a PC build and a Arcade build. You play Aero Fighters 5 times for a total of an hour of gameplay. Those stats get sent to our server and then when you start up your PC build the play time and play count is set to the new value and will show in the UI. There is a visual element added to the Default theme that shows the cloud sync status. This will get added to other themes once the version is closer to release. Overall a sync shouldn't take any noticeable amount of time for most users. The initial sync (the first time doing it) may take a second but overall you shouldn't notice it and it shouldn't slow down your app at all. Outside of viewing the game in the LaunchBox app there is no other UI at the moment for looking at your sync data.

Can you rerun the installer over your current setup? This won't overwrite data, just make sure you aren't installing a LaunchBox folder INSIDE of your LaunchBox folder in the installer. This error reads like there is some sort of mismatch in your DLL files

Sounds like you potentially hit a rate limit with the Steam API/Website. I was importing my Steam collection over the weekend so I know the functionality is working. I do know Steam has been getting more fussy about their rate limit since the deck came out. We put some code in to help with this recently, but I'd like to take another look soon to see if we can improve this even more.

I did with Faeran after I posted but don't really remember what came out from it. Some of the situations aren't as straightforward as they could be if wanting to use FlowContext. If just wanting to use a logo using the old CoverFactory is of course an option. Feel free to PM me and remind me in the future. Been working hard on the next version and I admit it slipped my mind after that initial talk and I forgot to post any update on the forum. My apologies. You have a concept image of what you're ultimately trying to that I could see that would help me make sure I'm getting you the best information?

.NET 7.0 isn't LTS so we would never move to that version anyway. We are moving versions soon, but are changing how we release the app so that runtime download/installation isn't required.

Means you have a corrupted image file associated to that game and the program is failing to open it

What resolution are you running at?

LaunchBox often needs restarted after enabling game controllers before the input can actually be used. I'd enable the option, press OK to save changes, then close and reopen LaunchBox and then try to set the bindings and see if it improves then.

Wall view does support an index, that being said to access it you must press the "Show Index" binding, you can't navigate to it using the direction keys like you can in other views.

Errors point to there being an issue with the theme you're using. This error also happens a lot on drives that aren't NTFS formatted.

Yes, the default box logic looks at the spine image and uses it's dimensions to determine whether it's a top/bottom spine or a left/right spine. If the image height > width then it's left/right, otherwise is top/bottom.

Can attempt to throw em in a zip file then use the image pack importer tool and see if it associates them correctly