Fursphere

My solution to that issue has always been to physically remove the files I don't want from the ROM folder. I have a separate folder with alternative rom versions for archival purposes (who is going to care about this when I'm gone? I have no idea... but I still keep the things). Basically, one folder for the "cabinet" set, then another for the "archive" set.

To that, I respond with this: (posted 12 days ago, by someone who is in the business of being a techie) Ya.. it sorta works. Sorta. Sometimes. If you're got copious amounts of time to mess around with it, and the technical expertise to back it up. (The majority of PC users DO NOT have the time or the skills)

Is it possible to get this working with Platform Categories? For example: "<path_to_launchbox>\ThirdParty\CLI_Launcher\CLI_Launcher.exe" category "<category_name>"

I'm occasionally seeing this error on one of my cabinets: Interestingly enough, I see "Xbox" in that error. And on that Windows 11 install, the included Xbox apps are installed: On my other cabinet, I am NOT seeing this error, and those Xbox apps have been uninstalled. No idea if these things are related... I'm going to remove the Xbox apps from the cabinet with the errors and see if the errors still occur. (its a relatively new Win11 install that I haven't cleaned up yet)

I think I only had like 4 games loaded at that point. (secondary Steam account is pretty light on driving cabinet games) It comes up looking like this... Not a problem, just odd I guess? lol I really have no idea how you'd make it better.

I noticed something funny today. Rebuilt one half of my Daytona Twin, and let launchbox auto-populate the windows games. I only have a few on that Steam install right now. Apparently none of them are 4.0+ Star Rated, so the "Highly Recommended" games section of Discovery Center is blank. lol Is this intended? I'm sure once I get more system loaded this "problem" will sort itself out, but it just seems odd that in the absense of 4+ star rated games, the answer is "display nothing" (basically telling the user - your games suck! lol).

I'm rebuilding my Daytona Twin driving cabinet, and started with fresh installs of launchbox. Using the 13.25 Beta 3 EXE installer - once completed, there were XML config files missing and wouldn't allow launchbox to start. I had to use the 13.24 installer then allow it to upgrade back to 13.25 Beta 3.

On one of my two cabinets running the latest beta... when I let them idle with the screensaver (big box screensaver) running, I eventually get this when I close bigbox...

People have been hailing the death of Windows and the beginning of Linux's rise to the top since the early 1990s. (Remember slackware and their "f**k you, figure it out yourself" welcome message?) Yet.. here we are. Value is pouring R&D money in Linux... for Steam. With Steam being the front end and operating system (more or less). The Steam Box may die and early death due to the RAM prices skyrocketing due to the AI data-center slop rush currently happening right now. We'll see. But the Steam Box (Steam Console?) is going to be more akin to Apple Mac than Linux. Its going to be a fit-for-purpose OS on fit-for-purpose hardware. Most people aren't going to buy a Steam Box to NOT use Steam big picture. That's the whole point. They'd just buy a regular computer instead... and SteamOS is only putting in drivers for the hardware they're selling. Anyway, long story short. Yes, it would be great to have a mainstream alternative to Windows. But Linux ain't there yet, and probably never will be since the solution to every major problem is "these guys are doing it wrong, I'll make my own fork and do it right!" (insert Bender quote here) - and now we've got thousands of forks.

Teknoparrot support in launchbox has been getting much better (thank you!), but the auto-import feature still doesn't seem to work. The 'roms' for Teknoparrot are XML files to the 'emulator', and auto-populated in the /teknoparrot/userprofiles/ folder. Add a game to TK, it makes a new XML file for that game. Launchbox should be able to see those XML files and treat them as a newly discovered game and auto add it to the platform. Before I open a bug (or feature request, although I think I've opened one before for this) - is this a limitation by design? Is there some technical reason that LB ignores XML files for this platform? thanks, as always

Everytime this thread gets a reply, the Linux port of Launchbox gets pushed back another year.

I couldn't find the feature request for this one, but it looks like its still not implemented as of current version 13.24. Any plans to work on this one? Or is the screensaver feature basically the only option here still? Thanks!

HBMAME Roms =/= MAME Roms MAME cores in RetroArch are looking for MAME Roms, not HBMAME roms. They're not compatible. And why are you using RetroArch for MAME / HBMAME?

I'm going to assume you don't support Windows 10 (Pro, 22H2) anymore, but in Beta 3 I'm seeing BigBox close (crash) after about 30 minutes of attract mode running, and i see this in the application logs: Beta is running fine on my Windows 11 (Home / 25H2) machine. I'm getting ready to reload this machine with Windows 11, so this isn't an issue for me. Just an FYI. Thanks.

I had no idea you could just drag files into the LB window to start the import process. Neat!

Why would you want to drag the XML files out of Teknoparrot's /userprofile/ directly and into launchbox's? Can't you just point launchbox at the /userprofile/ folder directly, so when you add a new game (using Teknoparrot's UI) LB will autoscan and pick it up?

I couldn't grab a screenshot fast enough. There were two running. First one finish and actually launched BigBox. Second one errored out.

So, this is been happening more and more with upgrades. When you click "yes" to upgrade in BigBox - it launches the installer TWICE. And one collides with the other. I usually have to cancel both, and then run the installer manually to get it to fix itself.

Manually reinstalling 12.23 Official fixed the auto-install issue.

The 12.23 "official release" upgrade broke my Launchbox / Bigbox install. It launched two copies of the installer automatically, and I suspect one messed up the other. Going to try and reinstall in a minute. But currently, trying to launch BigBox or Launchbox does absolutely nothing. It won't even attempt to start.

That was me. I'll test it out in a bit.

That's the one. Thank you!

Any updates on the MAME importer being broken?

How fast is your network between system running LB/BB and network share? If its Wifi, I would expect it to be very slow. I would even expect it to be slow on a 1gb ethernet link.

13.23 - BETA 2 trying to update my MAME set to the new version. Import wizard - "select rom location" - NEXT button is not usable. Unable to move past this screen.