JoeViking245

One [major] thing to consider is why it's still running in Task Manager after exiting. (more so with LaunchBox) When it exits, it closes the UI [right away] so you can go about doing other 'computer' stuff. After closing the UI, LaunchBox then goes about saving any changes (e.g. adding platform/games, editing stuff, etc.) that were cached during your session, in the background. Thus still present in Task Manager and not instantly being able to restart it [right away]. "Killing" it in Task Manager will essentially erase any changes that have not yet been saved to your drive. The amount changes you made (as well as the speed of your system) will determine how long it actually stays in Task Manager after "closing". I've seen it take from nary a couple seconds to upwards of 45 minutes. Do NOT take the 45 minutes as a measure of any sort of norm. That was on an old, slow arse machine, and I had done a MASSIVE import. Use it as just an [exaggerated] indicator that the more changes made, the longer it may take. The takeaway here is, let it finish "doing its thing" in the background, without "killing it" and potentially compromising your build. Make a mental note of changes you made and then take note of how long it actually stays in Task Manager. Even if it appears nothing is happening, wait it out. If you find you're making little-to-no changes and it stays in Task Manager after exiting 10-minutes (that's just a round number I threw out there) and doesn't go away, then it should be looked into further. On a related note, you may want to look at and upvote this Feature Request if you agree with it: Feedback - Seamless Switching Between LaunchBox and Big Box When Launching Executables

Edit the game and in the Start/Pause section check Override click Customize check Enable Game Startup Screen un-check Enable Game Shutdown Screen Click OK, OK To edit your Windows games in bulk select all the Windows games press Ctrl+E (to start the bulk edit wizard) for the Field, select Startup Screen - Shutdown Enabled leave the Value un-checked click Next, Next if you want to still have the Startup Screens enabled Select Yes for the Field, select Startup Screen - Enabled check the Value box click Next, Next Select No Otherwise (for no Startup or Shutdown screens) Select No

Does the Enable microphone support appear under View < Badges < Controller Support? I'm not sure if you can simply add them like that. May need to create a custom badge.

If you had Box-Front images (can have them along with your Box-3D images) for the games, it would take care of that. The 3D Model your referring to uses the Box-Front image for the rendered 3D box. (It will also use a Box-Back and Box-Spine images for when you spin the box with the mouse.) But if you must, you can disable seeing the 3D model under Tools < Options < Visuals < Game Details. (un-check Show 3D Model).

The "marques" on the left are Clear Logos. When a Clear Logo (image) for a game doesn't exist, it will show as white text. So the correct metadata Media you need to download for the game is Clear Logos. Once you've done that (from LaunchBox), in Big Box, you may need to go to System Menu < Options < Image Cache < Refresh Game Wheel Images to have them appear.

20 "images"? Or 20 "games"? If the latter, it's auto-importing files/games that are in the platforms' Games/ROMs folder that aren't in your collection. You can disable the Auto-Import feature globally under Tools < Options < General < Automated Imports. Or you can do it per-platform by right-clicking the Platform in the left panel and select Edit. Check the box Disable ROM Auto-Import. Details about the Auto Import feature can be found here: Automated ROM Imports - LaunchBox If I totally misunderstood, can you share some screenshots of what you're referring to?

This is a known issue. See more here: Feedback - Big Box Platform Wheel Not Rendering Until Scrolling

Pretty sure that's not downloading anything. Unless you've added new ROMs to the platforms folder and it's imported those and downloading metadata/images for those new ones. Most likely what you see is LaunchBox updating the cache for the images. Still. nothing being downloaded.

You might be able to just..., in the Associated Platforms section for the emulator, for that platform, check the box Extract ROMs.

These are both known issues. Feedback - Big Box Platform Wheel Not Rendering Until Scrolling Feedback - Big Box Background Images Not Appearing in Platform View You can email support@unbrokensoftware.com or at the top of this page, under Help & Support click Contact Us. They should be able to provide you prior releases.

Try this: This is a known issue: Feedback - Steam Trailers Unavailable Due to New Steam API Changes

Not all emulators have been tested. But the ones that have been all work. What emulator specifically are you using for the console Atari 2600? You can always manually edit the ini file (\Plugins\BezelLauncher\Bezels\Atari 2600\Atari 2600.ini). Remember, for your emulator settings, you will need to disable fullscreen. My guess is that's the issue with Daphne.

Ok, so it's not "it as stoped working in launchbox 13.25 the new update of launchbox." It's that 2.2.0 never worked for you. That's 2 different things. Whew! That's good to hear! Thanks for looking into it more on your side. I will look further into: not having any bezels creates an issue (which it seems to have done on your 2nd build). Thanks again.

You sent the "SetupLog...txt" (which is fine). Can you also send the corresponding "log....txt" file. Or better yet, zip up the "Logs" folder and attach it here. Also, to clarify some things: LaunchBox v13.25, v2.1.2 and v2.2 both do not work? LaunchBox v13.24, v2.1.2 does work? LaunchBox v13.24, v2.2 does not work? aka: v2.2 never worked for you?

It loads the same. Can you share a screenshot of your (LaunchBox) emulator settings. Make sure to check all 3 boxes (No quotes... etc). Also show the Associated Platforms section. And make sure the ROMs can be "seen" by DEmul. Easiest way is to place them in its /roms/ folder.

I'm still not able to reproduce the error. I'll try some things over this next week and see if I can break it to give me that error and see what I can do to fix it (provided I can get the error to appear).

Try Exit LaunchBox delete (or rename) the file BLSetup.xml that's in this plugins folder Start LaunchBox Open the setup [again] from the Tools menu

What's the error? Can you share a screenshot of it? If you attach (drag & drop the file here. Don't copy/paste the contents) the Log file from when it errored from \LaunchBox\Plugins\BezelLauncher\Logs\, I might be better able to help you figure out what's wrong.

A quick test shows it's working here. Can you attach (drag & drop the file here. Don't copy/paste the contents) the most recent Log file from \LaunchBox\Plugins\BezelLauncher\Logs\?

Go here: LaunchBox for Android - LaunchBox Scroll down to and click Importing from Network Drives. (I think that's what you're after)

Some examples (the last 2 probably being the more "popular" use case(s)): "I want to see (filter) only games that are controlled with a [steering] wheel." "I want to (play) see only games that can use a VR headset." "I like visually seeing the controller 'badges' a game uses." "I want to create a playlist that shows only games using a VR headset." ("so I can just select the playlist rather than clicking through filters")

The game controller management system you're showing is informational only. It adds another layer of metadata for games (and platforms) that can be used to filter from and/or show badges for quick identification. Its intent is to show the supported controllers for games and allow full flexibility for customization. aka Customize it to have information that makes sense to you. LaunchBox does not (can not, and most likely will not ever) do any in-emulator controller configuring (outside of being able to access the LaunchBox Pause Menu and exiting the emulator).

As an experiment, can you extract goldrunner.st from the zip and point the games application path to the st file and then try launching? According to this, single file games should load straight to the game. But theirs weren't zipped.

I have one plugin that [still] uses that copy of VLC. Fortunately, it's only one and can easily be changed to use the assets under /FFMPEG/. Thanks for the reminder that this removal (could happen?) is imminent.

A fresh install of MAME doesn't come with mame.ini. Open MAME double-click General Settings double-click Save Settings Press Escape 2 times make your changes to [the now present] mame.ini