C-Beats

You can set default artwork on a per platform basis if you wanted.

Point of the feature is to cleanly boot into Big Box on startup, not make Big Box a security suite for your PC. If you don't want users installing software, don't put any uninstalled game in your visible collection in Big Box. Even better yet, don't allow people access to your computer you can't trust not to do something like that in the first place.

I use an Odin Pro and the only issue I have is that sometimes their emulated controls cause the LB button to stick and causes menu to open/shut rapidly. To fix all you have to do is physically press the button though and that behavior stops. Outside of that I've had 0 issues.

You can change the display used in Big Box options for Big Box. MAME has an INI file that can be altered as well. I would verify that the correct monitor is still marked as primary in Windows though. LaunchBox doesn't tell emulators/games what screen to run on and so they default open on the default monitor unless that emulator/game overwrites that setting (like MAME does)

We're aware of Avalonia but moving to it would mean not only a complete rewrite of the UI, but would break all themes as well. So even the best case scenario is that we'd be able to right some sort of translation layer for themes to the new syntax, but to do that on top of an complete rewrite AND still deliver on the current product suite is a bit unrealistic for a team as small as ours.

Big Box by default opens up to Platform View, what you want to do is change settings to use Platform Category view instead which allows for this type of heirarchy. The tree needs to be built in LaunchBox using it's Platform Category View though as you can't set that up in Big Box.

\\LaunchBox\Data (contains all information about what's in your collection) \\LaunchBox\Images (by default is where all images are stored) \\LaunchBox\Videos (by default is where all images are stored) \\LaunchBox\Games (if you use this folder to store your ROMs) \\LaunchBox\Manuals (if you downloaded, or manually added, manuals) \\LaunchBox\Music (if you downloaded, or manually added, music) \\LaunchBox\Sounds (if you manually added Big Box navigation sounds) \\LaunchBox\Emulators (if you use this folder to store your ROMS) \\LaunchBox\Themes (Big Box themes if you want to back them up for any reason) \\LaunchBox\LbThemes (LaunchBox themes if you want to back them up for any reason)

Yeah we should look into that. I don't have any ETA guarantee's but I have it jotted down and put it on our short list of things to tackle

I can assure you the issue is local to your environment. We have already had several thousand users update automatically without issue so there is something going on in your setup. If you can proceed without the excessive aggression I'd be happy to help you troubleshoot the issue to see if we can find the cause and get you squared away.

Do you know how many pixels there are between the bottom of the back glass and the top of the DMD?

Yeah. That would fairly simple to do. I got some dev I got to finish up but if no one reaches out to ya by time I'll done I can write ya up something quick and dirty for ya.

Think you may have misunderstood. You have 2 files that need created for your entire library. The marquee view for your platform list, and the marquee view for the games list. The XAML would be pretty simple/straight forward. If you let us know what you want displayed on both monitors some one could help you make the files. If you just want two images shown it's a 5m job to do.

You'd have to manually create a marquee view file to do this, but yes it's entirely possible to do. I enjoy your cab design quite a bit though the main monitor being 4:3 for pinball I'm not sure I'd enjoy, the overall concept is pretty cool.

The GUID you see on some video filenames is because you have multiple games with the same title in the same platform. We add the game ID to the filename so we know for sure which video goes with which game.

I know my Nvidia cards have the ability to mess with settings like that per app. I'd check and see if you can do any app overrides and just turn it off for LaunchBox/Big Box and leave the global setting to on.

As stated, open up a ticket and we'll see how widespread the issue is. I am locking the thread as it's clear you have no interested in having a civil level-headed conversation about this issue.

Intel drivers are known to have issues with WPF applications (at least for their integrated graphics cards). Do you have the intel graphics software for that card? Or whatever AMD calls theirs? If so look for a setting to force anti-aliasing off or on. Intel drivers by default attempt to "auto-detect" whether they should use it or not and it causing a lot of artifacting. I've never seen it cause the issue you're reporting, but is worth a shot.

CRT is a dying tech, which is why there are adapters being made... to help those refusing to quit it. 640x480 IS low resolution and has been for several decades. 4:3 is an aspect ratio (which is what themes target) not a resolution and IS supported just fine as you've stated. You have several ways of accessing your LB data on another computer or monitor to make it possible to configure your machine. I don't mind discussing the issue with you, but if you are going to be entirely unrealistic about the facts of the matter than it'd be in both of our best interest to just move on.

Yeah, np. I get where you're coming from. Out of curiosity what card are you using, and does your system have an integrated card, a dedicated one, or both? I do know that intel integrated cards have known issues with WPF applications, so curious if something similar may be occurring on your machine.

LaunchBox doesn't have any custom code to handle rendering, it's all done by the WPF framework which is just using Direct X to do everything. A lot of what you're talking about is far too low level for the application to have any idea about it, let alone change behavior because of it.

Most of your performance hit isn't the symlink (per se), it's the fact you've linked to a location on network instead of local. Because of how those links work this WILL cause serious performance degredation.

We don't actively target such a low resolution because frankly a lot of the content just won't fit and be real legible on the majority of machines using that resolution. As many others have stated the amount of users touching resolutions THAT low are extremely small. As a business analyst I would expect you to be able to look at this objectively. We have a team of 3 and only one person actively developing LB/BB. The amount of time we can devote is a set number and any time spent on one item is time that can't be spent on others. To make the highest return on our time investment we have to take into consideration the amount of users affected by an issue as well as if there are feasible work arounds. This particular issue affects very few users, and there are several work arounds since the app is portable. I'd suggest you create a ticket on it so we can get a better understanding of how many users are affected by this issue, then can properly triage the issue from there. That being said you also have to take into consideration you're asking for development time on a hardware that is no longer in production (at least I'm unaware of any company still producing them) and will likely never be again, which alone is a pretty hard pill to swallow.