Fursphere

Feature request opened: https://feedback.launchbox.gg/p/auto-remote-titles-from-lb-when-game-no-longer-exists

Yup. Use it all the time. I'd like to be automatic. So I can manage my files outside of LB, then LB adjusts to what I've done without extra steps.

Was just watching the 13.25 release video, and saw that the Android release has "remove games no longer found" as an option. Is this going to be a Windows feature soon?

I ended up writing an AHK script that interacts (via mouse movements and clicks) with the fanatec app (which doesn't support keyboard navigation... sigh) to change settings as needed on game start. A little janky, but it works consistently.

thank you. I'm actually at the point where I'm ready to write a looping AHK script (while LB is running) to just edit that config line anytime the file changes to ensure its off. BigBox isn't having the problem.

Dear Launchbox, please stop enabling this setting. In fact, disabling it by default would be best. As you can see, this time it incorrectly assumed my 12-way rotary controller was a "game controller" and caused input issues in LB. (loss of mouse control, constant inputs, etc). Seriously, I've had to disable it more than a dozen times. It keeps turning itself back on. I haven't confirmed it yet, but it seems to re-enable itself anytime a controller is added to the system (even just turning on a bluetooth xbox controller and then opening LB seems to trigger it...)

I'm not sure if this is even the right place for the thread since the 'problem' is kind of abstract, but here goes anyway... Is there a luanchbox feature / plugin / mod......something that "Tells the user on game launch what physical controls to use?" (lemme explain) Some Background: I'm not trying to get down into the nitty gritty like 'button 1 = jump" or something. (like this thread: https://forums.launchbox-app.com/topic/68739-game-controls-viewer/ ). LEDBlinky mostly has that covered already to be honest. (except for spinner games). What I'm getting at it "this game requires a GamePad" (IE - tell the user to pickup and turn on a gamepad before the game starts). Now, I wrote an AHK 'shim' that does this, and it mostly works. It displays a full screen image and asks the user to press a button on the gamepad to continue. This 1) communicates to the user what's going on and 2) verifies the user has followed instructions. (I opened a feature request to make this a little easier to configure in LB, but proof of concept works) I'm going to write another for Lightguns "Pickup the lightgun and turn on the IR emitters" or "Lightgun + Pedal" (get the pedal out and plug it in). Maybe one for Spinner games (as there is no LED for LEDblinky to light up). (then I have crazy stuff that links both cabinets together so we can play 2 player Smash TV with twin sticks, or 4 player TMNT or whatever... I need to make a thread on that). Or to turn the Dolphin bar on when you're playing Wii games with WiiMotes. The key here is wait for user input to confirm the 'ask' has been completed. (The game start screen and pause screen feature of LB/BB do not meet this need) Now, the big challenge: Enter driving / racing games. Arcade racing game controls are all over the damn place. 270 degree wheel, 360 degree wheel. hi/low shifter, H pattern shifter, sequential shifter. Independent pedals, combined pedals. etc... (at least one uses a lightgun too.... lol) I use Fanatec gear, and there isn't an automatic profiling application (or CLI) to take care of this stuff. You have to open the Fanatec software, and tweak the settings. Thankfully, this is 'easy' (even if its annoying). I have Stream Deck minis on my cabinets with a Fanatec App button - so getting to the app is easy) Logitech wheels have (had?) better automation for this stuff, but that's not what I run in my Twin Daytona cabinet. Anyway.... So the dream is to have some way to tell the user (often ME! - who can remember all this stuff?): "Hey Dummy, before I launch this MAME game, you need to go click the combine pedal checkbox, and set the wheel to 270 degrees" (Ace Driver Racing for example) or "Spy Hunter uses a sequential shifter, flip the level on the shifter base" or "Pole Position uses a 360 degree wheel, set the wheel to 360 degrees and turn FFB off" (I was so happy when I figured out this worked...) There are significantly less racing/driving games than a regular cabinet game list, so I can just proceed with creating static images per game or AHK message boxes or something. (ugh). But before I dive in, does anyone have a better idea?

Just in case anyone doesn't know - RPCS3 now supports running (decrypted) ISOs directly. No more need for fancy tricks. You can just boot directly from an ISO file.

I think I figured it out. Looks like Launchbox 'sees' my SpaceMouse as a controller (why!?!?) and defaulted to it (why?!?!?!) to which is freaked out. Is there a way to have it NOT do this? like.. blacklist controllers? "never use" list or something? "Don't use a gamepad for mouse movement" (checkbox?) (I think this happened on my driving cabinet too - where launchbox was trying to use the wheel and some random axis for mouse movement)

I have this issue on two different systems, sometimes on a 3nd. When I open Launchbox / Bigbox - the application takes over my mouse and drives it to the upper left corner, and locks it there (constant input). If I alt-tab out of LB/BB (or even just bring up the start menu), complete control is restored. What code in LB/BB interacts (and takes over) mouse control? Edit - this happened on 13.24 and the 13.25 Beta-3

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!