JoeViking245

Using "select start on my controller to exit emulators" essentially the same as pressing Alt+F4. The Exit Game (LB) and Close the Active Window (BB) will "press" Escape. If the emulator stays active, it will then "press" Alt+F4. At least that's my understanding. You can test it by making a backup of your save(s), then play the game a little and press your button-combo to close it. If it does work to close it, then restart the game and see if all's still good.

What version of LaunchBox are you running? One thing you can try is to disable automated imports (2 locations). Tools < Options < General < Automated Imports Tools < Manage < Storefronts...

I have yet to look into this. It's sitting somewhere on my to-do stack.

@AZUR3US @Rlad Been doing some testing and indeed, when BezelLauncher is enabled, it is not incrementing play time. But... it is incrementing the play count. However, if you go back to LB version 13.22 (an arbitrary version I had installed) it will track time. But only 2 seconds for each game startup. Play 20 minutes, it tracks 2 seconds. So, yeah... confirmed it never worked. 😊 I looked at (refreshed myself what exactly I did way-back-when) my code for this plugin and I can't see rhyme nor reason why this is affecting LB from tracking playtime with the plugin enabled. The only thing I can think of is it's an emulator window focus or an emulator top z-order thing. Where the bezel window may take focus for a second, but then gives it back to the emulator window. All while forcing itself (the bezel) to the top z-order. Another thing is you can play for "that 20 minutes" with BezelLauncher enabled and when you exit, LB's shutdown screen will show. Which itself is a good thing. But to me is perplexing because the shutdown screen knows when the game exits, but the time tracker isn't following suit. Long story short... it ain't gettin' fixed anytime soon.

It's weird that it's just locking up LB/BB (vs. the whole PC). I missed this earlier. Are you saying the when you launch the game from LB, and you press Alt+F4, there are no issues with it closing and LB regaining focus? Or was that an actual question? I don't own the game, so can't test. If pressing Alt+F4 does exit the and returns focus back to LB, what happens if you press your controller mapped button(-combo) to Exit Game (LB) or Close the Active Window (BB)?

When you Ctrl+Alt+Del, are you restarting the whole PC at that point? Or selecting Task Manager and just force closing (End Task) LB?

Did you try disabling Startup Screens? (not sure if it'll change anything, but worth testing) Edit game. (left panel) scroll to the bottom Startup/Pause. Check Override Default Startup Screen Settings. Click OK to save and close.

Ah Ok. Sounds like it may be the game then. Is it a stand-alone exe? Or are you running it through Steam? Is it only in Big Box this happens? Or does it cause issues when ran through LaunchBox as well? If you have startup screens enabled for it, can try turning them off [for process-of-elimination testing]. To clarify, when you say "exit through the game", you're exiting through the games' Menu? Vs. exiting using Big Box's controller mapped Close the Active Window.

Startup/Shutdown has been overhauled in the 13.28-betas. Not sure if it'll fix the issue with this one game. You can opt into the beta releases under Tools < Options < General < Updates (if you so desire to test and provide feedback). Or wait for the Official release. I don't know the ETA for the 13.28 Official release.

VLC has been overhauled in the 13.28-betas and ffmpeg has been removed. (if that helps any. ) You can opt into the beta releases under Tools < Options < General < Updates (if you so desire to test and provide feedback). Or wait for the Official release. I don't know the ETA for the 13.28 Official release.

To clarify: Do they not show in LaunchBox? Tools < Options < Visuals < Game Details - Show Videos Or are they not playing? View < Media < Auto-Play Videos (Ctrl+Alt+V)

Alt+F4, File>Exit and clicking the X in the upper right corner all close the app the same [nice] way. In AHK, Process, Close, program.exe is the brute force method for closing an app. Same as clicking End Process in Task Manager. There are a few rare cases though that this is necessary. joytokey.exe is one of them. Glad it worked and glad I could help.

There's probably a ton of factors involved here. Like sensible vs. completeness. And even that depends on the individual. It really boils down to what do you want to look at. And possibly to a greater extent, what the theme you're using will show (vs. what it will never show because it's not an option). In LaunchBox, what 'will show' is less of a concern. Whereas in Big Box. the Theme you use will dictate if "that image" will ever be displayed. e.g. for Arcade, I don't think I've ever seen a Theme that will display the Arcade-Circuit Board image. Granted, in both LB and BB you can see all images you have for a specific game in the Game Details. The image types you chose will (can) also depend on the platform you're downloading them for. Going back to Arcade, arcade cabinets never came in a box, so a real Box-Front image will not exist. But users have created box-front images for arcade. Though I've yet to see one that shows "the wooden crate". For this, many will use the Arcade-Flyer Front image. Myself, I like the nostalgia of the Arcade-Cabinet image. For all other platforms, at minimum (my opinion) you'd want: Clear Logo Box Front Box Back Box-Spine (if available) Fanart-Background The Box-Front is (typically) the games main image. That, plus the other box images mentioned make up the 3D box model (the one you can rotate to see all sides). In LaunchBox, the logo and background images are what will show on the top of the Game Details panel. Which is both sensible and complete. Note: The Box 3D Model is different from the Box-3D image. Depending on the Big Box theme being used, it may make use of a Cart-Front (or Cart-3D) or Disc (e.g. Wii) image. I think I've seen it more so in the game details section. The Default [game] Startup Theme will use the Disc image for GameCube, Wii, PS1, PS2 and Sega Dreamcast. Screenshot images are a whole 'nother thing. Mainly because there can be a gazillion gameplay images per game, but only one can ever be displayed at a time. Which actually holds true for ALL image types. That said, if you have 2 different Box-Front images for [Atari 2600] Adventure, only one of those will be (can be, actually) shown when you select that platform. However, if you select a different platform then go back to Atari 2600, the 'other'' image might get displayed. It selects them randomly (id there's more than one). I believe it works that way for Screenshot-Gameplay images shown in Big Box as well. But seriously, I don't think even in "completeness" mode, anybody needs a dozen gameplay screenshots. After you get a baseline for what images you want, then come to a realization of only the images you need, the cherry-on-top for media is gameplay videos. If you have a paid EmuMovies account, they can be brought in (imported/downloaded) the same time as images. Just don't forget about actually playing your games too!!

Batch files cannot detect key presses. But AutoHotkey scripts can. It might look something like this: SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. #SingleInstance Force rom = %1% FileDelete, .\reshade-shaders\Textures\bezel.png FileCopy,.\Artwork\naomi\%rom%.png, .\reshade-shaders\Textures\bezel.png Run, nomousy.exe /hide RunWait, Demul07_CRTGeomMOD.exe -run=naomi -rom=%1% Run, nomousy.exe ExitApp $Esc:: { Send !{F4} } Save the file as fileName.ahk This was created 'quick-and-dirty' and has not been tested.

It's under JVS Mode - System.

Sorry. I figured the article may have talked about doing a manual restore. (obviously I didn't read through it) manual restore (for this case of a corrupt ListCache.xml file) Go into /LaunchBox/Backups/ and look for a zip file that is dated before this issue occurred. Open the zip file Copy the ListCache.xml file that's in there in your /LaunchBox/Data/ folder. Replacing (overwriting) the existing one that's there. Start LaunchBox

@PolybiusExtreme @prophecy0 @Barebum @goofers My 4 and only plugin commentors/followers (thank you for your support): Do any of you use DemulShooter with Dolphin? I'm looking at adding in that emulator and would appreciate some insight. If you do use DemulShooter with Dolphin, please read on. If not, no worries and thanks for checking in. For Dolphin, DemulShooter only requires DemulShooter.exe -target=dolphin5 -ddinumber=x (replacing "x" with an appropriate number) I know that if you leave off -ddinumber=x completely, it'll default to -ddinumber=3. It's my understanding you only need to add -ddinumber=x if you're setup for 2 players. (And... I could have totally misread that when I looked at it a couple months ago.) Either way, it doesn't hurt to add it in. Assumptions on my part: There's only a handful of lightgun games for Dolphin. The DDI number will be the same [on "your" setup] for all Dolphin lightgun games. I'm pretty confident about #1. And would appreciate some confirmation (or correction) about #2. My thoughts are, in DemulShooter Auto-Launcher Settings, to add button to show only games using Dolphin. From there, the user can set which games they want DemulShooter to launch with. Aka, DemulShooter won't start for Dolphin games unless you specifically tell it (the plugin) to. Then of course, there'll be a spot for the DDI number to use (A) for all games, or (B) on a per game basis (depending on the response for #2). I'd rather not launch DemulShooter unnecessarily. Hence forcing 'you' to tell 'me' which games specifically to load it for. Also, if my assumption #1 is correct, it won't be too much hassle. Next big unknowns to me, would a user ever use/need for Dolphin: -nocrosshair -noinput -nogun -profile=[config file] The last one I'll leave available as it makes sense, overall. But not sure if the other 3 are applicable to Dolphin. Are the 1st 3 applicable for Dolphin? Worse case, I'll have users check which games to run DemulShooter with, have them add the "x" number per game and leave the above 4 options available. I think™ that should cover it. As always, am open to suggestions. If you got this far, thank you for your time.

From the LaunchBox for Windows - Strategy Guide: Backing Up and Restoring Your LaunchBox Setup - LaunchBox

If you had updated to the 13.28-beta release and are seeing it 'worse' (or I suppose, still an issue), for best results of helping to get it resolved please post you findings on the 13.28 beta thread. Note, the afore mentioned "Improvement" was done in release beta-4. Since you're still seeing it in beta-5, it would help best to let the deveulopers know in the beta thread.

Apologies. You are correct. It doesn't give you the 'option' to not update it. I guess what I was thinking of was when importing games or manually adding a game and clicking Search for metadata.

Thanks for testing that. Personally, I never look at how long I've played a game and as stated, no one has brought this to my attention. When I get back to town later this week, I'll look into this more. But my gut feeling says no. It comes down to how LaunchBox is determining the game is still active/being played and what BezelLauncher is doing with the emulator. Which this plugin is [basically] only resizing the emulators window and setting it as the active window. Hence my perplexation. To clarify, if you use just the mouse to adjust the slider and save, there're no issues? But when using the arrow keys to adjust, is when the issue occurs? If these are both true, I have a fix in mind [for (hopefully) later this week].

Well, this is perplexing. You couldn't find anything because no one's brought it up before. I'd be curious to know if this happens with all emulators [using BezelLauncher], or just the Mupen GUI. Are you seeing this with other emulators using BezelLauncher? Or just the Mupen GUI emulator, as well? If it's with all emulators, it makes me think that the playtime tracker is looking for the emulator to be the top Z-order window (which is where the plugin forces the bezel to be) vs. the Active window (which will be the emulator, itself).