eatkinola

Posted the platform exporter. The bundled PDF describes it a little and I think it's pretty easy to use, but let me know if you have any questions. If you do, please post to the download page or open up a new topic since I've kinda gotten this thread off topic (sorry @Joelbagz).

Updated WootLauncher to v1.2 - major improvements to the joypad framework which manages gamepad inputs. This includes bugfixes and new gamepad features, e.g., you can now bind the "home" button on a DS4 or Xbox controller to launching the pause menu. It also now handles cases when gamepads are unplugged or plugged in; this is done seemlessly without need for any user intervention. Another cool addition: you can now map a button combo to quickly exit the game, bypassing the need to use the pause menu to exit a game. Also, a game reset function was added to the pause menu. The PDF manual on the download page is also updated and explains how to use these new features.

Updated dropins, including a new one called PlatformExporter -- created to export LB platform libraries for use by EmulationStation. I built a little retropie box and wanted a quick way to export the games including metadata I had curated within LB.

Yes retroarch does the same thing, showing menu when guide button pressed; so I disabled that in retroarch and the ds4 guide button works great for WL. Easy way to find the button ID is to use the BigBox settings controller mapping feature, and pretend to map the guide button to something (you can then quickly clear out that mapping). I'll provide some more details when I post the WL update.

It should as long as you specify the button id in the WL config file. I use DS4 so I could test with that only. It's a new feature that will be in the WL update I'll post this weekend. Would be great if u could test it with the Xbox controller.

Have an update almost ready to go: * ADDED: gamepad mappings to directly exit game w/o needing to use pause screen; @JaysArcade * ADDED: game resume option to pause menu, inspired by @Chadmando's new pause menu app * ADDED: custom mapped "function" buttons, e.g., activate pause menu via DS4's PS-logo button Any suggestions let me know, and perhaps I can roll it into this update.

^^ this ... recently made a little retropie setup using a nespi case and it's very nice. It's not as flashy as LB/BB but it's so easy to use. I made a little LB plugin to export the LB library to EmulationStation (on retropie), and I'll probably upload that plugin soon.

Thanks for the info. Would you please try FluxCRT and see if the same thing happens? It's pretty similar to Refaktor under the hood but has a few differences. Might help me narrow it down a bit. If you could also check MinmalX that'd be helpful, too.

Might be a bug. I've not noticed in my setup, but I don't use AHK scripts outside of WL so maybe that's why. Does it only occur with certain emulators in BB? Yeah that's just personal preference. I can see users wanting either approach. I use the pause menu to exit, and that way the emu exit is baked into WL and I don't need any extra WL scripts. I guess I could add an option to WL to map an exit button combo that would work across all emus supported by WL. Do you think that would be useful?

Not at all. Apologies for the radio silence. I've got some hectic stuff going on at the moment, travel stuff. File names such as for bezels should be explained in the PDF for WL. You can name per emulator (including for core if RA), and game. For vertical vs horizontal, I'd recommend naming the horizontal bezel MAME (if that's how you name the emulator in LB). Then, you could place your vertical bezel is the Games subfolder and name the file using the LB game ID. You'll have to have a copy of the vertical overlay for each game, unless you could somehow use mklink (not sure that would work). I actually recommend letting RA or MAME manage the bezels so you can then use with or without WL did you want, but that's just my opinion. I let RA handle all it's own bezels.

Hey, it's no trouble at all! Appreciate you doing a thorough job of troubleshooting and reporting back. I'm sure your efforts will help someone else down the road. I actually just let retroarch handle it's own overlays, and WL does overlays for emus that don't support them such as dolphin and demul. Whether overlays are provided by retroarch or WL, the pause menu should still work just fine.

Good call spycat -- that'd be much easier for xllovera.

Identify the platform view file by going to the BB options menu -> Views -> Platforms List View (what is currently selected as the platform view). Then, look for a file with a name like that in the Views folder. The line(s) of code you need to comment out should be in that xaml file. Not trying to be vague, just want to point you in the right direction. There are an endless number of mods you can do to a theme. Don't be afraid to try stuff out and see what happens. Just keep a backup file to restore if needed, or download the theme again if things really get messed up. That's how I learned to create themes, and I messed up a lot; hopefully I eventually got some things right... You can always contact the creator of that theme, but please do a little more digging first; maybe post the code you think you need to modify or something.

That's a bummer. I tried every combination of video_fullscreen, video_windowed_fullscreen, and ui_menubar_enable, but I cannot reproduce that problem on my system. If I've got it right, the problem is that when you use a combination of these options that successfully hides the menubar, the pause menu does not work. It sounds like it's not properly capturing or holding onto the RA window, and two things I can think of could cause this: (1) RA is somehow starting in exclusive fullscreen mode (you would probably see a black flicker on your monitor when starting up), or (2) the RA fullscreen toggle (e.g., "F" by default) is being triggered somehow -- I know that will break the pause menu because it will lose the RA window it captured. Any chance one of these is going on? Using a dual-monitor setup in a special way? It might help to see your log file again when this happens. Also, are you using anything else such as a AHK script from within LB? In case it matters (it shouldn't), I use RA core overrides to configure my emulators. This is what I use for the nestopia core:

@JaysArcade: Could you try the new version 1.1 when you have time and let me know if you still have this issue?

Well at least that's progress! Does it show an error message when quitting BigBox, and does that happen with WMP or VLC? Anything in the log file? Refaktor\Plugins\Ao.Bigbox.Themer.v3_9_2\AssemblyLogger\ Does it look like it's running out of memory? How much RAM in your system? Edit: P.s. to generate a log file you have to enable logging in LaunchBox

Ao.Bigbox Customs View File Ao.Bigbox Customs is a collection of LB/BB plugins. The Themer library contains custom controls useful for theme developers. The Dropins library contains true plugins you can just drop into the LB plugins folder. By default, the only drop-in enabled is WootLauncher; enabling the other drop-ins is easy (see the PDF doc download). Here are the included drop-ins: GameManualViewer: Adds menu item "Game Manual 8D" (string is customizable) to the game details menu in BB, if the game has an associated PDF manual. When activated, the PDF will be read and converted to images on the fly for display within BigBox; it will not launch an external program. As occasionally some manuals take a few seconds to load, an animated GIF is displayed while you wait. The gif is currently a space invader, but I might add customization in the future. When viewing the PDF manual, use the standard keys (or gamepad buttons) used to navigate around BigBox. PlatformAuditor: Adds another media audit tool for LB with support for OCD-type personalities. This can help you quickly find a platform's missing game media and rename media according to the game's title. It can also be used to delete superfluous media. It works for images, manuals, music, and videos. As with any tool that potentially modifies your library, consider backing up your media folders before using this. PlatformExporter: Adds a simple way to export games including metadata and boxart to other applications. Currently, the only application to which it exports is EmulationStation. Support for other applications might be added in the future, if there is enough demand and I have enough time and interest in doing so. PlaylistGenerator: Adds playlists to your library but does not otherwise alter your library. Playlists are regenerated each time LB/BB is started. You can add your own media (videos, banners, etc) for the playlist, in the same way you would for manually generated playlists in LaunchBox. This media will not be overwritten when the playlists are regenerated. You can customize the names of these playlists and number of games added to each. WootLauncher: Adds game load/exit screens, pause screens including support for viewing PDF manuals and save/load states, and bezels/overlays (useful for emulators which do not themselves support overlays). There is a separate download page dedicated to WL: Here are some of the themes that use Ao.Bigbox.Themer FluxCRT - videos displayed within a mock CRT including curvature effect MinimalX - simple but very flexible (skinnable) theme with some cool controls Nostalgia - videos displayed within viking's clean and nostalgic platform images Refaktor - clean view suited for 16:9 or 4:3 displays and videos/screenshots of all sizes Submitter eatkinola Submitted 02/17/2019 Category Third-party Apps and Plugins

Yea the format of this text is hardcoded. You can however remove this Progress line entirely. Look for this in AOStyles.xaml: <!-- FILT/GAME: METADATA TABLES (SIDEBAR) --> <FontFamily x:Key="AOMetadataTableFontFamily_TAG">Calibri</FontFamily> <FontWeight x:Key="AOMetadataTableFontWeight_TAG">Bold</FontWeight> <SolidColorBrush x:Key="AOMetadataTableFontColor" Color="#CCFFFFFF" /> <Style x:Key="AOMetadataTableSide" TargetType="aop:AbstractMetadataTable"> <Setter Property="TagFontFamily" Value="{DynamicResource AOMetadataTableFontFamily_TAG}" /> <Setter Property="TagFontWeight" Value="{StaticResource AOMetadataTableFontWeight_TAG}" /> <Setter Property="Foreground" Value="{StaticResource AOMetadataTableFontColor}" /> </Style> <Style x:Key="AOMetadataTableSide_PLAT" TargetType="aop:PlatformMetadataTable" BasedOn="{StaticResource AOMetadataTableSide}"> <Setter Property="FieldOrder" Value="PlatformGamesCompleted,PlatformStarRatingsAvg,PlatformReleaseYear" /> <Setter Property="ColumnBalance" Value="-0.15" /> </Style> <Style x:Key="AOMetadataTableSide_GAME" TargetType="aop:GameMetadataTable" BasedOn="{StaticResource AOMetadataTableSide}"> <Setter Property="FieldOrder" Value="GamePlatform,GameProgress,GameReleaseYear" /> <Setter Property="ColumnBalance" Value="-0.15" /> </Style> For AOMetadataTableSide_GAME, edit "FieldOrder" to remove "GameProgress". Available options for fields are: Your theme mods look nice!

Updated WootLauncher v1.1 -- see changelog on download page for details @Spiro9210: one of the changes includes support for what you asked above

That's currently the only way to do it. There are two ways I could help automate this: (1) have it automatically delete the cache for a theme when you switch to that theme, or (2) create a system menu item for doing this. I kinda like option 1 as it'd quietly do it's thing in the background; the cache would not be deleted when starting BB, only when actually changing to that theme in BB. Awesome, thanks! I try to keep things documented partly so I can remember how they work later. I do need to document the cache thing better.

FYI posted an update that might resolve that problem from before. The update includes changes pertaining to WMP and especially VLC.

Posted the update -- please try it out and let me know how it goes on your system.

Well it's been awhile but I found time to dig into this more and am almost positive I found the problem; it was a pretty sneaky memory leak. I should be able to post an update over the weekend. Thanks again for bringing this to my attention; this same bug was affecting another one of my themes.

Bingo -- reinstalled Beta 10 and works fine, so +1 on the directx install issue. Thanks Jason. Now I'll install Beta 11 ... all this progress!

I'm getting an error in beta-10 every time I start either LB or BB. I close the error dialog and things work as expected, but the error dialog pops up every time. I get it even when using no plugins at all and using the default theme. I'm hoping it's just a random thing on my system and goes away with the next upgrade. Log: