JoeViking245

Yes. That error that popped up is a LaunchBox error, caused by this plugin. There were no log files in ../LaunchBox/Plugins/BezelLauncher/Logs/ ?

I just tested with LaunchBox 13.27 and a fresh install of v2.2.1 of the plugin and it worked fine here. Try deleting this plugin's folder ("BezelLauncher") from within the /LaunchBox/Plugins/ folder. Unzip v2.2.1 into the /LaunchBox/Plugins/ folder. So you should have ../LaunchBox/Plugins/BezelLauncher/BezelLauncher.dll and no other files or folders next to the dll file. Start LaunchBox and go to Tools and select BezelLauncher Setup. Without clicking anything else, do you get that same error? If so, can you share the 2 files that are in the plugins Logs folder? (If there's more than 2, you may have done something wrong. If there's less than 2 or none, then something's really screwy.) Just drag and drop the 2 files here. Don't copy and paste their contents.

Glad it was an easy fix.

Does clicking Uninstall for that plugin do anything? (Honest question. I've never tried it.)

On the download page, scroll to the bottom of the description. Where it says What's new in version xyz, click See changelog and select the old version you want. At the bottom of the notes for that release, click Download.

You don't want to do that. That will create other issues down the line. Link making LB/BB throw [other] errors. That's usually the 1st thing I do on a PC. But in this case never had the issue [not hooking] you're seeing. Another thing I'll do is add an exception in Defender for the entire LB folder structure. Most likely not related but doesn't hurt if your diligent with your build. I say I "never had the issue", but I also don't run TP at all. I 'threw it out the door' several years ago. To many idiosyncrasies, more than I felt I should have to deal with. Switched to JConfig, and more recently Linux Loader. Unfortunately, the 2 example games you mentioned aren't in my arsenal. You don't have TP running as Admin. Do you? (That may have been part of the reason I 'threw it out'. For me, if a gaming app requires elevation to run on my machine, it doesn't get used on my machine.) Do you have issues with DemulShooter and other emulators? Flycast, Model2 (emulator_multicpu.exe), Demul, Linux Loader, MAME w/lua scripts, CXBX Reloaded...? What hooking app are you using? No idea if that'd be related at all. But if I'm thinking correctly, the hooker app is about the only way you can tell if DemulShooter is relaying the outputs. I used MAMEHooker for about a half day until I told to use QMameHook. Not that there was something wrong with MH. It's just that I was told QH works better. (Note, I've only been in the lightgun scene for 3 months. So still learning as I go. ) I've recently switched to the up-and-coming OutputHooker, which has been working great. Wait... is you hooker app running as Admin?

I figured as much. But you said it 2 different times, so thought I'd have some fun. I would hold off on the CHD set and concentrate on just the main ROM set to start. This should whittle you down to about 85GB. One of the Features in MAME Tools is Which MAME Machines Require CHDs. It's basically a visual representation of 'is it worth it'. e.g. Of the just over 1TB of CHDs, you're looking at almost 690 games [comprised of about 1040 individual .chd files] . About 370 of those games are parents (since the files are so big, probably don't want to mess with the clones). Of those approx. 370, only 57 are considered "Working". 112 if you look at "Working" and "Imperfect" ('may run but has some minor emulation issues'). Anyway, just food-for-thought. clrmamepro can help you to create/isolate a curated set. IF you can figure out how to use it. I don't know how to use it, myself. But I've heard great things ('once you figure out how to use it'). Honestly, I think you'd be time-[WAY]-ahead getting a non-merged set (about 151GB) and doing step 2 and 3 and just-be-done-with-it. Once you whittle out the crap create your perfect curated set, the storage space consumed will be much less. The Merged CHD set will work just fine. Besides, you don't have a choice. That's the only format if comes in (from reliable sources). As for the BIOS set you mentioned, with a non-merged set it won't be needed. Whether you stick with merged set or get a non-merged set, if you can, I suggest keeping the full set in-tact somewhere (external drive? thumb drive?) and then pull out (copy, not move) for your curated set. You never know when someone's going to point out that Hidden Gem you never knew about and then wished you hadn't deleted the rest of the full set. Been there. Done that.™

For a 22 your old ROM set, I'm curious how many games are actually in there. Actually, I just looked. There's 4605 ROMs. Only 2492 if you take out the clones. And less than 50 of those require CHDs (which is higher than I thought it would be). But compared to the current MAME release having 11,761 games, that's a lot more manageable. For a non-merged set, that would work perfectly. The main issue you run into with a merged set are the clone ROMs. These are actually physically inside the parent ROMs. But the application path will point to the ROM filename of the clone, even though the file doesn't physically exist. This is where MAME knows to look inside the parent ROM file if the clone file doesn't exist. But LaunchBox doesn't know to do that. So in step 2 of the process, LaunchBox will look for the physical files to copy. It won't "see" the clones and will tell you as much. Which may not be so bad. As long as MAME knows what it's looking for when launched. For step 3, I believe LaunchBox again look for the physical files and change only the path for ones it can find. You might be able to do step #2, then for "step 3"... close LaunchBox and manually edit the platform's xml file, doing a bulk Find/Replace of the application paths (changing from the old to the new). If you imported no clones, that should make it a lot easier. If you imported clones as Additional Apps, you might still be [somewhat] ok. If you imported clones separately, you still could be ok. These latter 2 using the might method. However, this all depends on you being "aware I need to add the BIOS and CHD files later on" as that's the "next issue". Not all games require a BIOS and/or Device file, so quite a few should continue to work [after "the move']. Knowing which BIOS and Device files is a feat on its own. But yeah, could just copy them all into the new location and call it good. LaunchBox won't/can't do that for you. However you go about it, just don't delete your full set until you know everything's good. Which.. note step #2 only copies the files. So that'll help [just in case ]. When you think you got it all good and find that a particular game or 3 don't work, there's a plugin called MAME Tools that one of its features is MAME Troubleshooting that can tell you exactly what's going on (or not going on) with a particular game. e.g. a missing BIOS or Device file or CHD and what file exactly it's looking for.

Made some changes. Can you give this a try and let know how it goes? RunDemulShooter (v1.3.0-beta-1).7z Yeah, that is weird. It sounds like when you start DemulShooter, it can't find the corresponding game to hook, so instead of waiting around, it exits itself. Which if that's the case, the HookTimeout got set to something other than 0 (zero). ("If the value is 0, it will wait forever.") This setting can only be changed by manually editing DemulShooter's config.ini (should be the last line in the file). Check if you have a value other than 0 set there. Which games are you seeing this on? (Don't say all of them! Name a few. ) I know with their most recent release (v17.5), Lindbergh games now require the parameter -pname=BudgieLoader.exe. There was also a resolved issue with TP games when ran fullscreen. However, neither of these explain why they'd work if starting DS after the game is running. (dang it!) So back to the original question: "Is there any way to automate this [starting DemulShooter after the game is running] via the plugin?" No. Because of how TP is a launcher, it's difficult to determine when the actual game is up-and-running to then start DS. Well, there could be. But it'd be a guessing game and would have to customize it on a per game basis. It's not something that should need to be done and is more than I want to do. If this becomes an epidemic, I may then rethink my position. A fix: Go old school and create an AutoHotkey script set to run Before the main application that will 'Sleep' a certain amount of time then start DS with the appropriate parameters. The Sleep may, and the parameters will vary from game to game. So you can't just add something to the emulator's Running Script. Hopefully your post on the DemulShooter thread will get a response that has a simple resolve.

To clarify for the developers, are you seeing that same error? Or is it a 404 error you're getting?

You're welcome. Edit: You didn't follow the Installing and Using instructions; The 2nd bullet (right after extracting the files). (I should probably fix this. But this also shows me who can follow instructions. ) Can't say I've ever heard of that before. 'Need to launch DemulShooter after the TP game is running.' Unless you're saying that's the case ONLY via the plugin. If this is the case, may need to set the -pname= option for those games (?) via the settings menu. Edit Which according to the above error, you can't even do that.

Time lost is knowledge gained?

'Hamburger' Menu < Help < Check for Updates...