Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'plugin'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LaunchBox
    • Android
    • Beta Testing
    • Collections and Builds
    • Features
    • Troubleshooting
    • Website/Forum Support
    • Noobs
    • News and Updates
  • User-Created Content and Downloads
    • Big Box Custom Themes
    • Big Box Sound Packs
    • Big Box Startup Videos
    • Custom Theme Tutorials
    • Game Media
    • LaunchBox Custom Themes
    • Pause Themes
    • Platform Media
    • Playlists & Playlist Media
    • Startup Themes
    • Third-Party Applications and Plugins (Released)
    • Third-Party Applications and Plugins (Development and Beta Testing)
    • Videos
  • LaunchBox Games Database
    • News and Updates
    • Contributions
    • Features
    • Troubleshooting
  • Off Topic
    • DOSBox
    • Emulation
    • Games
    • Monkeys
    • Buy / Sell / Trade

Categories

  • Big Box Custom Themes
    • Legacy Themes
  • LaunchBox Custom Themes
  • Startup Themes
  • Pause Themes
  • Big Box Startup Videos
  • Big Box Sound Packs
  • Third-party Apps and Plugins
  • Game Media
    • Game Theme Videos
    • Game Media Packs
    • Game Marquee Images
    • Game Clear Logos
    • Game Box Art
    • Game Cart Images
    • Arcade Cabinets
  • Platform Media
    • Platform Theme Videos
    • Platform Console Images
    • Platform Backgrounds
    • Platform Banners
    • Platform Clear Logos
    • Platform Bezels/Overlays
  • Playlists & Playlist Media
    • Playlists
    • Playlist Theme Videos
    • Playlist Backgrounds
    • Playlist Banners
    • Playlist Clear Logos
  • LaunchBox/Big Box Media

Blogs

  • Jason's Devotions
  • Thatmans Blog
  • THAT NINTENDO SWITCH EARLY REVEAL WAS FROM A STOLEN CONSOLE
  • Version 8.8
  • Game Theme Videos

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 49 results

  1. AxLauchBox v1.00 =============== Hey everyone i present to you my Second Launchbox plugin AxLaunchbox. With this plugin you will be able to launch all you're favourite shockwave flash games and movies all within launchbox Instructions Unzip the contents of the file into your launchbox plugins folder , all dll's must go into the folder for this plugin to work. There is also a file called dummy.exe you can put that in there too, import your games as Flash on launchbox and point emulator to dummy.exe , this will allow you to be reminded if needed that you launch the games by right clicking and clicking Launch with Axlaunchbox just a place holder so launchbox thinks there is an emulator there.Yot do not need to use the dummy.exe if you do not wish. Unfortunalty you will have to find your own images for the covers until I or one of the launchbox team codes a Flash scraper Enjoy Feedback and drinks are very much appreciated , Thankyou Superfurry(Paul) AxLaunchbox.rar
  2. Version 1.0.1

    337 downloads

    About Plugin that scrapes information from HowLongToBeat.com and adds custom fields with game lengths information. I made this plugin to add length information for certain games, mostly rpgs. This adds 3 custom fields for Main Story, Main + Extra and Completionist length. You can configure which ones you want to add by editing the file HLTBPlugin.xml. Because there's no oficial API from HLTB, I had to parse the HTML, which means that as soon as they change something on the HTML this plugin probably will stop working... Install Extract files (dll + xml) to : Launchbox/Plugins/HLTBPlugin. Config (HLTBPlugin.xml) MainStoryLength: Enable/disable main story length update. Default: true. MainExtraLength: Enable/disable main story + extra length update. Default: true. CompletionistLength: Enable/disable completionist length update. Default: true. MainStoryFieldName: Change main story length custom field name. Default: Main Story Length MainExtraFieldName: Change main story + extra length custom field name. Default: Main + Extra Length CompletionistFieldName: Change completionist length custom field name. Default: Completionist Length Note: If you change the fields names it will not update the games that already have information, so you will end up with duplicated fields with different names and you will have to manually delete them (edit game -> custom fields tab). So config the first time and stick with that. Usage Access the option by right-click a game (only one game, no massive update yet). A window will popup with all the games found and you can choose which one correspond to your game. If there's no results you can manually change the search words (e.g. Metal Gear Ac!d will get no results but you can then change the search to Metal Gear Acid). You can use the "Arrange By" option to order the games by length. Lengths are shown with leading zeroes because is the only way to properly order the games since custom fields are strings and not integers. Tested on version 8.9. I think you need a premium license because custom fields are not supported in free license (not sure). I have no relation with HowLongToBeat.com, if you like their work please go and support them.
  3. Version 1.1

    53 downloads

    Resets a games Play Count to 0 (zero). Place the "ResetPlayCount.dll" file into your ..\LaunchBox\Plugins\ folder. *edit* Right click ResetPlayCount.dll, select Properties and click "Unblock". Start LaunchBox. Select just one, multiple or all (Ctrl+A) games. Right-click and then click on "Reset Play Count" located at (or near) the bottom of the popup menu. There is no "Please Confirm" nor "Play Counts have been reset to 0 (zero)" message boxes. It just does it as soon as you click it. (V1.0) *edit* Version 1.1 adds a confirmation message box. ResetPlayCount.dll - 6KB
  4. SteamLauncher View File SteamLauncher Plugin for LaunchBox Introduction SteamLauncher is a LaunchBox plugin designed to allow roms/emulators to easily be launched through Steam, directly from the LaunchBox/BigBox interface, without any complicated setup or technical know-how. Simply follow the instructions for installation (see Installation section), enable the plugin (see How to Use section), and then launch any game as you normally would. Updates/Notices If you have ANY problems with the plugin, I want to know about them. While you are free to post on the plugin thread or send me a PM, the most effective/fastest way to speak with me personally is via Steam. If I am at my computer, I will answer your message immediately. My Steam alias is lahma0. You can click on my alias to open my Steam profile to add me as a friend, or you can copy/paste the following URL into your address bar: steam://friends/add/76561198237461630 MAME Compatibility Fix It was recently observed that MAME crashes when launched through a non-Steam shortcut in the latest version of the Steam client. This problem is not directly related to this plugin but being that this plugin relies upon non-Steam shortcuts, it meant that launching MAME via this plugin no longer worked. After a lot of investigation and tinkering by @cammelspit and @JedExodus, @JedExodus managed to find a fix for the issue. Whether launching MAME directly in Steam via a non-Steam shortcut or via LaunchBox/BigBox using this plugin, the fix is to simply modify the launch parameters to include the following: -joystickprovider xinput -keyboardprovider win32 If one of these parameters already exists when modifying MAME within LaunchBox, you will obviously need to replace it (don't just add a 2nd instance of '-joystickprovider' or '-keyboardprovider'). You can safely ignore any popups/warnings that LaunchBox displays about pause screen compatibility. If you have any problems, feel free to join the plugin support thread by clicking the 'Get Support' button on the right hand side of this page. 6/18/2019 - New Update Adds Resilient Method for Resolving VTable Offsets (Beta v0.9.3.0) This update makes some significant changes in the way the plugin finds the needed vtable offsets when interfacing with the Steam client DLL. This should finally solve the problem of Steam updates breaking compatibility with the plugin. 5/13/2019 - A New Beta Update is Available (Beta v0.9.2.0) This new update to the March 2019 Beta fixes some reported issues and contains many small optimizations. If you are new to the plugin, please read the "March 2019 Beta" notice below as well as the rest of the documentation. For a list of changes, please see the Change Log at the bottom of the page. REMEMBER, if you're updating from an old version and want to back it up before replacing it with the update, it must be moved ENTIRELY outside of the LaunchBox root directory or ANY of its subdirectories. Having 2 copies of the plugin ANYWHERE within the LaunchBox directory structure simultaneously WILL cause big problems. 3/16/2019 - Major Overhaul of SteamLauncher - New Beta Available for Download (Beta v0.9.1.0) There is a new beta version of the plugin available for download. I’ve been working hard over the last few months to complete this major overhaul of the plugin, and I’ve decided to release this beta for those wanting an early peek at the new features. This new version works in a fundamentally different way when compared to the old version. The biggest change is that there is now a universal toggle to enable/disable the plugin, and when enabled, any game/emulator launched through LaunchBox/BigBox will now be launched via Steam, without the need to select the “Launch via Steam” context menu item. Nearly all of the limitations of the old plugin are now eliminated, enabling features such as compressed rom support, non-default emulator configs (“Launch with [...]”), and startup/shutdown screen support. The old version of the plugin will still be available for those who prefer to wait for a stable release. However, the current beta still retains the old “Launch via Steam” context menu item whenever the universal Steam launching toggle is disabled. This should make it easy to switch between the old plugin’s Steam launching feature and the new beta’s universal Steam launching feature. A moderate amount of testing has been done on the new version, but seeing as this is a beta, there may still be some bugs under certain edge cases. If you find anything, please report your findings in the plugin’s forum thread. Before using the new beta, please read the new “How to Use” section in the documentation below. While in transition to the new plugin, please excuse the messy, unorganized documentation. It will be completely overhauled once a stable release of the new plugin is available. If you want to back up your existing "SteamLauncher" directory prior to installing the beta, MAKE SURE you do NOT leave it inside of the "Plugins" directory OR ANYWHERE ELSE within the directory structure of LaunchBox.. Move it outside of the LaunchBox directory entirely.. If you have 2 copies of "SteamLauncher.dll" ANYWHERE within the LaunchBox directory structure simultaneously, VERY WEIRD THINGS WILL HAPPEN. Strictly speaking, you probably do not have to delete your existing config.xml file before upgrading to the beta, but if you have any problems, close LaunchBox, delete config.xml, and then run LaunchBox again (it will create a new config.xml file when the plugin loads.) 5/26/2018 As of v0.9.0.2, the plugin now supports PC/Windows games, DOSBox games, and ScummVM games in addition to emulated games (roms). UNBLOCK DLL AFTER DOWNLOADING @neil9000 reminded me that Windows automatically "blocks" DLL files that are downloaded from the internet, so after following the instructions and placing the plugin DLL in your LaunchBox plugins directory, you need to right click the DLL, click 'Properties', and check the box at the bottom of the dialog that is labeled 'Unblock'. Features Here are just a few of the features or benefits provided by using this plugin: Allow LaunchBox to do what its good at - be the sole organizer and maintainer of your rom collection, without having to duplicate its functionality in Steam (something it was not designed for) Keep your Steam library clean and uncluttered by hundreds of emulator/rom shortcuts Get all of the benefits of Steam's excellent overlay system while playing any rom or emulator Take advantage of Steam's infinitely customizable controller configuration (bindings) for both the Steam Controller and nearly all other DirectInput/XInput controllers Use per-rom or per-emulator controller configurations that are automatically remembered between gaming sessions (without having to create convoluted Steam shortcuts for every rom) Bypass or improve upon many emulators' extremely limited controller bindings and hotkey options Share your "currently playing" status with Steam friends for whatever rom you launched from LaunchBox/BigBox. Example: “YourSteamAlias is currently playing 'Super Metroid (SNES)'” Features (New/Current Version) Here are a list of the features added in the March 2019 beta update: Compressed rom files are now supported (should work the same as when the plugin is not enabled) Startup/shutdown screens should work normally (as they do when the plugin is not enabled) Non-default emulator configurations are now supported (when you right click a game and choose a “Launch with” option) There are other additional features included with the new beta that will be explained at a later date or upon release of a stable/final version. Requirements .NET Framework 4.7+ Steam for Windows LaunchBox Installation Extract the 'SteamLauncher' directory from the compressed package into your LaunchBox plugins directory Right click the SteamLauncher.dll file, click 'Properties', and look at the bottom of the dialog (on the 'General' tab) for a checkbox labeled 'Unblock'; if you see it, check that checkbox and click 'OK'; if you don't see it, then you are done Example: If LaunchBox is located at 'C:\LaunchBox', you would copy the 'SteamLauncher' directory to 'C:\LaunchBox\Plugins'. This would result in 'SteamLauncher.dll' and any additional files (if any) being inside the directory 'C:\LaunchBox\Plugins\SteamLauncher'. It would be greatly appreciated if you would leave a comment/review on this page with a bit of feedback after installing the plugin and trying it out. Even just a short comment such as, "It works for me" or "Not working" would help out a lot. The plugin was tested on a very limited number of setups and environments prior to release, so any small amount of feedback will help in gauging whether the plugin generally works for most people or whether more testing is needed. How to Use New/Current Version After installing the plugin, there is now a simple ON/OFF toggle to enable the new functionality. In LaunchBox, this toggle can be found at the bottom of the “Tools” menu. In BigBox, this toggle can be found near the bottom of the root system menu (go back one level after starting BigBox). The new functionality is OFF by default. To turn it ON, simply click the menu item. When enabled, the menu item text will end with “(ON)” as displayed in the image below. When this option is turned ON, the old plugin’s “Launch via Steam” context menu item will be unavailable. LaunchBox BigBox Original/Old Plugin (Deprecated Information - For new users, simply ignore this. The current version no longer requires this.) Simply bring up the rom's context menu in LaunchBox (in BigBox or normal mode) and click the option at the bottom of the menu labeled "Launch via Steam" Note: Currently SteamLauncher will only launch the rom using its default emulator. If you wish to use a different emulator with that particular rom, you will have to go into that rom's settings and change its default emulator (or change the default emulator for the entire platform associated with that rom.) Customize Platform Names When roms are launched with the plugin, the title of the game, as Steam sees it, will be in the format of: "Game Title (Platform Name)" Example: Super Mario Bros. (Nintendo Entertainment System) For whatever reason, you may want to keep the long "official" name of the platform in LaunchBox, but use a shortened, abbreviated, or different platform name inside of Steam. The plugin has this functionality available, and it can be enabled by following these instructions: Open the SteamLauncher directory and look for a file named 'config.xml' If you do not see the file, you need to launch at least 1 game with the plugin, and then manually close LaunchBox, and the file should then appear in the directory Open the file with a text editor, and look for the line labeled, '<CustomPlatformNames>' Anywhere under this line, and before the line labeled, '</CustomPlatformNames>', you can add as many new lines as desired in the format of: <Platform Name="Original LaunchBox Platform Name" Custom="Custom Platform Name" /> You may already see a couple of example lines in place with fake platform names which you can copy/paste and modify to add your own custom platform names After making your changes, simply save the file, close it, and then reopen LaunchBox The next time you launch a game, you should see your new custom platform name substituting the real platform name in Steam (an easy place to see the title of the game you're playing is in the Steam overlay) Just to reiterate, here is an example of what the aforementioned lines look like in my config file: <CustomPlatformNames> <Platform Name="Super Nintendo Entertainment System" Custom="SNES" /> <Platform Name="Nintendo Entertainment System" Custom="NES" /> <Platform Name="Nintendo Game Boy Advance" Custom="Nintendo GBA" /> <Platform Name="Nintendo Game Boy Color" Custom="Nintendo GBC" /> </CustomPlatformNames> Known Issues There appears to be a significant bug in the Steam Client right now that can cause problems with controller bindings under a variety of situations for certain users. If you launch a rom/emulator with LaunchBox and your controller bindings don't seem to be working, simply exit the game and launch it again. This may happen the very first time you try to launch a game using the SteamLauncher plugin (one time total after freshly installing the plugin, not on every new session in LaunchBox). If it happens frequently, please report the problem so further workarounds can be investigated. Support Unfortunately I don't run a dedicated call center to provide technical support... However, if you need help with any technical issues or bugs (see 'Debug Logs'), want to suggest a new feature (I am very open to any ideas), just want to chat, or anything else related to the plugin, feel free to send me a PM or shoot me an email at the address listed below. Contact Information Alias: Lahma Email: lahma0@gmail.com GitHub Project URL: https://github.com/lahma69/SteamLauncher (Does not yet reflect the changes made in the March 2019 Beta or newer versions. I will be updating the GitHub as soon as I can.) LaunchBox Community Forums Profile: https://forums.launchbox-app.com/profile/89710-lahma/ Debug Logs To provide help with any technical problems or to investigate a bug, I will need a copy of the debug log that is generated whenever debug logs are enabled in the configuration file. To enable debug logs follow these instructions: Close LaunchBox/BigBox (this is important.. changes to the config while LB/BB is running will be overwritten) Locate the file named 'config.xml' in the SteamLauncher directory and open it with a text editor Find the line that looks like this: <DebugLogEnabled>false</DebugLogEnabled> Change the word 'false' to 'true' (do not include the quotation marks) Save the file and close it Now simply repeat whatever behavior was causing the issue and/or bug, and after you're sure you've replicated the behavior, manually close LaunchBox Again, look inside the SteamLauncher directory, but this time looks for a file named 'debug.log' (there may be more than one sequentially named log files if there was an enormous amount of output, but this is unlikely if debugging was turned on just briefly) Zip up the one or more log files and attach them to your message, along with the details of your particular setup (Windows version, 32-bit or 64-bit, LaunchBox version, Steam version, SteamLauncher plugin version, etc). The more information the better. Source Code https://github.com/lahma69/SteamLauncher Legal Stuff ©2017 Valve Corporation. Steam and the Steam logo are trademarks and/or registered trademarks of Valve Corporation in the U.S. and/or other countries. Submitter Lahma Submitted 02/11/2018 Category Third-party Apps and Plugins  
  5. Steam Tools Plugin View File This is a test release of Steam Tools for LaunchBox. To install, unzip the contents of the ZIP into LaunchBox's Plugins folder. This plugin now supports being in a subfolder. Current Features: Basic Steam game import functionality Install with Steam function for games (with custom Menu in BigBox) Provided SteamTools.BigBox.DataElement available for inclusion in themes to access SteamTools.Core data Options Menu Automatic custom field if using LB Premium for use in playlists Optional automatic Hiding of uninstalled Steam games Optional automatic Un-Hiding of installed Steam games Background task for automatic updating of Installed/Uninstalled fields Future Features: Steam game Metadata and Media system (requires external database) Current Test Targets: Stable Steam instance detection if Steam is opened after LaunchBox or closed and reopened while LaunchBox is open Import Stability Example use of the SteamTools.BigBox.DataElement plugin in a theme: <UserControl xmlns:st="clr-namespace:SteamTools;assembly=SteamTools.BigBox.DataElement" xmlns:gif="clr-namespace:WpfAnimatedGif;assembly=Unbroken.LaunchBox.Wpf"> <Grid> <st:SteamTools.BigBox.DataElement x:Name="SteamData" SetOnce="True"/> <DockPanel> <Image Name="SteamInstallStatus" DockPanel.Dock="Left" Margin="0,0,5,0" RenderOptions.BitmapScalingMode="HighQuality"> <Image.Style> <Style TargetType="Image"> <Setter Property="Visibility" Value="Collapsed"/> <Setter Property="gif:ImageBehavior.AnimatedSource" Value="pack://siteoforigin:,,,/Themes/Nielk1-CriticalZone/Resources/RatingLoading.gif"/> <Style.Triggers> <DataTrigger Binding="{Binding ElementName=SteamData, Path=IsSteamGame}" Value="True"> <Setter Property="Visibility" Value="Visible"/> </DataTrigger> <DataTrigger Binding="{Binding ElementName=SteamData, Path=IsInstalled}" Value="True"> <Setter Property="gif:ImageBehavior.AnimatedSource" Value="pack://siteoforigin:,,,/Themes/Nielk1-CriticalZone/Resources/SteamInstalled.png"/> <Setter Property="Visibility" Value="Visible"/> </DataTrigger> <DataTrigger Binding="{Binding ElementName=SteamData, Path=IsInstalled}" Value="False"> <Setter Property="gif:ImageBehavior.AnimatedSource" Value="pack://siteoforigin:,,,/Themes/Nielk1-CriticalZone/Resources/SteamNotInstalled.png"/> <Setter Property="Visibility" Value="Visible"/> </DataTrigger> </Style.Triggers> </Style> </Image.Style> </Image> </DockPanel> </Grid> </UserControl> Source Code: https://github.com/Nielk1/LaunchBoxSteamToolsPlugin Submitter Nielk1 Submitted 05/19/2017 Category Third-party Apps and Plugins  
  6. Add To Games DB View File *** Updated for Initial Support for LaunchBox v.Next *** AddToGamesDb: A plugin to help automate the process of submitting all of your game information and images from your collection to the LaunchBox Games Database. About the Plugin This plugin makes use of an application traditionally used in automated testing (Selenium) to automate the process of submitting games to the LaunchBox Games Database. It will open an instance of your default browser (provided that browser is either Chrome or Firefox. If some other browser is your default, it will try to open Chrome), and attempt to submit the selected game to the LaunchBox Games Database based on the information provided in your collection. If the game does not exist in the database, it will create a new game entry and submit it to the database. If you have added additional information or images to a game that already exists in the database, it will enter the title and platform, then pause to let you choose the existing game, then add any additional information from your collection to the LaunchBox Games Database. Installation Instructions Note: For this plugin to work, you will need to have either Chrome or Firefox installed. If you have both installed, it will use whichever you have set as your default browser. If you are using Firefox as your default browser and have enabled Firefox Profiles, please note that this will run under the default profile. For any and all other cases, Chrome is the preferred browser. Unzip everything to the Plugins folder. Usage Instructions Note: If, in editing your collection, you are prompted to download an update for the LaunchBox Games Database, afterward you will need to close and re-open LaunchBox for the plugin to detect the changes. Open LaunchBox and browse to a game that is either missing from the Games Database, has additional information not in the database, or has images not in the database -- right click that game, and select the appropriate option, it will show either: Add Game to LaunchBox Games Database Update Game in LaunchBox Games Database Add New Images to LaunchBox Games Database The first time you run the plugin, you may be prompted to login to LaunchBox Games Database. If so, the plugin will pause here to allow you to login as normal. Check "Remember Me" to skip this step going forward. Your login information is not read or stored in the code, it is stored in Chrome or Firefox's normal AppData cache on your system. If you do not login, the plugin will time-out after 5 minutes and close the browser. Depending on the game, you may be prompted with a screen that identifies similar titles and you will be asked to either select the correct title, or click the button to add a new game. If so, the plugin will pause here until you make your desired selection, then automation will resume for the remainder of the process. Logging By default, the logging is only set to a general "Info" level and up that contains generic start and submission successful messages, along with any errors encountered. If you continue to encounter an error somewhere along the way, please take the following steps: Browse to the plugin's folder -- LaunchBox\Plugins\AddToGamesDb Open NLog.dll.nlog in Notepad or another text editor. Scroll down to the bottom and find the <rules> section of the configuration. Find this line: <logger name="*" minlevel="Info" writeTo="file" /> And change it to this: <logger name="*" minlevel="Trace" writeTo="file" /> Try to submit the problem game, if it is a particular game causing the issue, or another game in general otherwise. Browse to the log file in the plugin's folder -- LaunchBox\Plugins\AddToGamesDb\log\AddToGamesDb.log Feel free to post the error and preceding trace either on the plugin's support page or PM me either the entire log or the part pertaining to the last issue, whichever is easier for you. From there, I'll investigate and make any updates necessary. Supported Fields Auto-population of the following fields is currently supported: Name/Title Platform Release Date ESRB Developers Publishers Genres Wikipedia URL Overview Max Players Cooperative Images Known Issues Context Menu (right-click menu) does not refresh on Audit window. If you update the information for a game in LaunchBox (clicking Edit from the right-click menu for the game), you will need to click away from the game (click some other game, for example), and then right-click on the updated game again for the context menu to update. Even without doing so, however, the correct process should run even though the text and icon on the menu haven't yet updated. A lot of work has gone into stabilizing the initial release and this latest release, but if you encounter any issues, please let me know and I will be glad to work with you to update the plugin accordingly. Thanks, Jason, for providing your amazing software and thanks again to Jason, the LaunchBox staff and the community for your support in developing this plugin. Submitter UnderwoodNC Submitted 05/20/2017 Category Third-party Apps and Plugins  
  7. Version 1.1.0

    19 downloads

    Use this plugin to filter and import MAME Software Lists into LaunchBox. Features: - Choose to import clones as Additional Apps, separately or not at all - Skip Prototypes (filter option) - Skip Non Supported games (filter option) - Import the selected (filtered) Console/Computer games into LaunchBox - Adds the appropriate command to each imported games' Command Line (ex. a2600 -cart) - Copy the filtered selection of roms to a separate folder (optional) (After copying files, they will automatically be imported) What's needed: - (2) dll files included in the zip file - MAME Software List hash files (located in the "hash" sub folder of your Mame's main folder) - MAME Software List roms and BIOS files (only if you want to actually play them) What it won't do: - Filter/Sort by Region (it's a MAME hash file limitation) - Determine if/what BIOS files are needed - Import Metadata and Media (just use LaunchBoxs' built-in Tool) How to: - Copy the "ImportMameSoftwareLists" folder from the zip file to your ..\LaunchBox\Plugins folder. - Navigate to that folder and unblock the 2 dll files. (Right click, Properties, and click Unblock) - Start LaunchBox. Right click on any game (doesn't matter which one) and Select "Import MAME Software Lists". Note: - The "Destination Folder" is required even if you don't plan to copy the files. It's needed to set up the Application Folder for the games when Importing. - Before being able to run the games, you will need to add the roms folder path [Destination Folder] to MAME. Start mame64.exe - Configure Options - Configure Directories - ROMs - Add Folder *** Unlike with Arcade machines, mame.ini does NOT need to have Software List rom folders added to "rompath". (The exception is any necessary bios files which are not included in the Copy process) This assumes the MAME emulator does NOT have "Don't use quotes" and "Use filename only" checked. (Both boxes unchecked)
  8. MAME Software Lists Import Tool - plugin View File Use this plugin to filter and import MAME Software Lists into LaunchBox. Features: - Choose to import clones as Additional Apps, separately or not at all - Skip Prototypes (filter option) - Skip Non Supported games (filter option) - Import the selected (filtered) Console/Computer games into LaunchBox - Adds the appropriate command to each imported games' Command Line (ex. a2600 -cart) - Copy the filtered selection of roms to a separate folder (optional) (After copying files, they will automatically be imported) What's needed: - (2) dll files included in the zip file - MAME Software List hash files (located in the "hash" sub folder of your Mame's main folder) - MAME Software List roms and BIOS files (only if you want to actually play them) What it won't do: - Filter/Sort by Region (it's a MAME hash file limitation) - Determine if/what BIOS files are needed - Import Metadata and Media (just use LaunchBoxs' built-in Tool) How to: - Copy the "ImportMameSoftwareLists" folder from the zip file to your ..\LaunchBox\Plugins folder. - Navigate to that folder and unblock the 2 dll files. (Right click, Properties, and click Unblock) - Start LaunchBox. Right click on any game (doesn't matter which one) and Select "Import MAME Software Lists". Note: - The "Destination Folder" is required even if you don't plan to copy the files. It's needed to set up the Application Folder for the games when Importing. - Before being able to run the games, you will need to add the roms folder path [Destination Folder] to MAME. Start mame64.exe - Configure Options - Configure Directories - ROMs - Add Folder *** Unlike with Arcade machines, mame.ini does NOT need to have Software List rom folders added to "rompath". (The exception is any necessary bios files which are not included in the Copy process) This assumes the MAME emulator does NOT have "Don't use quotes" and "Use filename only" checked. (Both boxes unchecked) Submitter JoeViking245 Submitted 09/08/2019 Category Third-party Apps and Plugins  
  9. Don't know if anybody would be interested in this but I am working on a little plugin/EXE to help sort out Images for games in the Launchbox collection. It's been written in VB.net and there is nothing special about it, it just does the job it was written for, or at least it does on my system. I will say this is my very first post in any forum so please be gentle with me, I have no idea what I am doing here, just making it up as I go...……. WooHoo a you-tube video I am also learning VB.net while writing the plugin, used VB6 in the past and now on VB.net 2017 so a big leap, Would anybody be interested in testing it on there system? If I can figure out how to get it out there. Butler_Soft.zip
  10. Version Beta 0.9.3.0

    672 downloads

    SteamLauncher Plugin for LaunchBox Introduction SteamLauncher is a LaunchBox plugin designed to allow roms/emulators to easily be launched through Steam, directly from the LaunchBox/BigBox interface, without any complicated setup or technical know-how. Simply follow the instructions for installation (see Installation section), enable the plugin (see How to Use section), and then launch any game as you normally would. Updates/Notices If you have ANY problems with the plugin, I want to know about them. While you are free to post on the plugin thread or send me a PM, the most effective/fastest way to speak with me personally is via Steam. If I am at my computer, I will answer your message immediately. My Steam alias is lahma0. You can click on my alias to open my Steam profile to add me as a friend, or you can copy/paste the following URL into your address bar: steam://friends/add/76561198237461630 MAME Compatibility Fix It was recently observed that MAME crashes when launched through a non-Steam shortcut in the latest version of the Steam client. This problem is not directly related to this plugin but being that this plugin relies upon non-Steam shortcuts, it meant that launching MAME via this plugin no longer worked. After a lot of investigation and tinkering by @cammelspit and @JedExodus, @JedExodus managed to find a fix for the issue. Whether launching MAME directly in Steam via a non-Steam shortcut or via LaunchBox/BigBox using this plugin, the fix is to simply modify the launch parameters to include the following: -joystickprovider xinput -keyboardprovider win32 If one of these parameters already exists when modifying MAME within LaunchBox, you will obviously need to replace it (don't just add a 2nd instance of '-joystickprovider' or '-keyboardprovider'). You can safely ignore any popups/warnings that LaunchBox displays about pause screen compatibility. If you have any problems, feel free to join the plugin support thread by clicking the 'Get Support' button on the right hand side of this page. 6/18/2019 - New Update Adds Resilient Method for Resolving VTable Offsets (Beta v0.9.3.0) This update makes some significant changes in the way the plugin finds the needed vtable offsets when interfacing with the Steam client DLL. This should finally solve the problem of Steam updates breaking compatibility with the plugin. 5/13/2019 - A New Beta Update is Available (Beta v0.9.2.0) This new update to the March 2019 Beta fixes some reported issues and contains many small optimizations. If you are new to the plugin, please read the "March 2019 Beta" notice below as well as the rest of the documentation. For a list of changes, please see the Change Log at the bottom of the page. REMEMBER, if you're updating from an old version and want to back it up before replacing it with the update, it must be moved ENTIRELY outside of the LaunchBox root directory or ANY of its subdirectories. Having 2 copies of the plugin ANYWHERE within the LaunchBox directory structure simultaneously WILL cause big problems. 3/16/2019 - Major Overhaul of SteamLauncher - New Beta Available for Download (Beta v0.9.1.0) There is a new beta version of the plugin available for download. I’ve been working hard over the last few months to complete this major overhaul of the plugin, and I’ve decided to release this beta for those wanting an early peek at the new features. This new version works in a fundamentally different way when compared to the old version. The biggest change is that there is now a universal toggle to enable/disable the plugin, and when enabled, any game/emulator launched through LaunchBox/BigBox will now be launched via Steam, without the need to select the “Launch via Steam” context menu item. Nearly all of the limitations of the old plugin are now eliminated, enabling features such as compressed rom support, non-default emulator configs (“Launch with [...]”), and startup/shutdown screen support. The old version of the plugin will still be available for those who prefer to wait for a stable release. However, the current beta still retains the old “Launch via Steam” context menu item whenever the universal Steam launching toggle is disabled. This should make it easy to switch between the old plugin’s Steam launching feature and the new beta’s universal Steam launching feature. A moderate amount of testing has been done on the new version, but seeing as this is a beta, there may still be some bugs under certain edge cases. If you find anything, please report your findings in the plugin’s forum thread. Before using the new beta, please read the new “How to Use” section in the documentation below. While in transition to the new plugin, please excuse the messy, unorganized documentation. It will be completely overhauled once a stable release of the new plugin is available. If you want to back up your existing "SteamLauncher" directory prior to installing the beta, MAKE SURE you do NOT leave it inside of the "Plugins" directory OR ANYWHERE ELSE within the directory structure of LaunchBox.. Move it outside of the LaunchBox directory entirely.. If you have 2 copies of "SteamLauncher.dll" ANYWHERE within the LaunchBox directory structure simultaneously, VERY WEIRD THINGS WILL HAPPEN. Strictly speaking, you probably do not have to delete your existing config.xml file before upgrading to the beta, but if you have any problems, close LaunchBox, delete config.xml, and then run LaunchBox again (it will create a new config.xml file when the plugin loads.) 5/26/2018 As of v0.9.0.2, the plugin now supports PC/Windows games, DOSBox games, and ScummVM games in addition to emulated games (roms). UNBLOCK DLL AFTER DOWNLOADING @neil9000 reminded me that Windows automatically "blocks" DLL files that are downloaded from the internet, so after following the instructions and placing the plugin DLL in your LaunchBox plugins directory, you need to right click the DLL, click 'Properties', and check the box at the bottom of the dialog that is labeled 'Unblock'. Features Here are just a few of the features or benefits provided by using this plugin: Allow LaunchBox to do what its good at - be the sole organizer and maintainer of your rom collection, without having to duplicate its functionality in Steam (something it was not designed for) Keep your Steam library clean and uncluttered by hundreds of emulator/rom shortcuts Get all of the benefits of Steam's excellent overlay system while playing any rom or emulator Take advantage of Steam's infinitely customizable controller configuration (bindings) for both the Steam Controller and nearly all other DirectInput/XInput controllers Use per-rom or per-emulator controller configurations that are automatically remembered between gaming sessions (without having to create convoluted Steam shortcuts for every rom) Bypass or improve upon many emulators' extremely limited controller bindings and hotkey options Share your "currently playing" status with Steam friends for whatever rom you launched from LaunchBox/BigBox. Example: “YourSteamAlias is currently playing 'Super Metroid (SNES)'” Features (New/Current Version) Here are a list of the features added in the March 2019 beta update: Compressed rom files are now supported (should work the same as when the plugin is not enabled) Startup/shutdown screens should work normally (as they do when the plugin is not enabled) Non-default emulator configurations are now supported (when you right click a game and choose a “Launch with” option) There are other additional features included with the new beta that will be explained at a later date or upon release of a stable/final version. Requirements .NET Framework 4.7+ Steam for Windows LaunchBox Installation Extract the 'SteamLauncher' directory from the compressed package into your LaunchBox plugins directory Right click the SteamLauncher.dll file, click 'Properties', and look at the bottom of the dialog (on the 'General' tab) for a checkbox labeled 'Unblock'; if you see it, check that checkbox and click 'OK'; if you don't see it, then you are done Example: If LaunchBox is located at 'C:\LaunchBox', you would copy the 'SteamLauncher' directory to 'C:\LaunchBox\Plugins'. This would result in 'SteamLauncher.dll' and any additional files (if any) being inside the directory 'C:\LaunchBox\Plugins\SteamLauncher'. It would be greatly appreciated if you would leave a comment/review on this page with a bit of feedback after installing the plugin and trying it out. Even just a short comment such as, "It works for me" or "Not working" would help out a lot. The plugin was tested on a very limited number of setups and environments prior to release, so any small amount of feedback will help in gauging whether the plugin generally works for most people or whether more testing is needed. How to Use New/Current Version After installing the plugin, there is now a simple ON/OFF toggle to enable the new functionality. In LaunchBox, this toggle can be found at the bottom of the “Tools” menu. In BigBox, this toggle can be found near the bottom of the root system menu (go back one level after starting BigBox). The new functionality is OFF by default. To turn it ON, simply click the menu item. When enabled, the menu item text will end with “(ON)” as displayed in the image below. When this option is turned ON, the old plugin’s “Launch via Steam” context menu item will be unavailable. LaunchBox BigBox Original/Old Plugin (Deprecated Information - For new users, simply ignore this. The current version no longer requires this.) Simply bring up the rom's context menu in LaunchBox (in BigBox or normal mode) and click the option at the bottom of the menu labeled "Launch via Steam" Note: Currently SteamLauncher will only launch the rom using its default emulator. If you wish to use a different emulator with that particular rom, you will have to go into that rom's settings and change its default emulator (or change the default emulator for the entire platform associated with that rom.) Customize Platform Names When roms are launched with the plugin, the title of the game, as Steam sees it, will be in the format of: "Game Title (Platform Name)" Example: Super Mario Bros. (Nintendo Entertainment System) For whatever reason, you may want to keep the long "official" name of the platform in LaunchBox, but use a shortened, abbreviated, or different platform name inside of Steam. The plugin has this functionality available, and it can be enabled by following these instructions: Open the SteamLauncher directory and look for a file named 'config.xml' If you do not see the file, you need to launch at least 1 game with the plugin, and then manually close LaunchBox, and the file should then appear in the directory Open the file with a text editor, and look for the line labeled, '<CustomPlatformNames>' Anywhere under this line, and before the line labeled, '</CustomPlatformNames>', you can add as many new lines as desired in the format of: <Platform Name="Original LaunchBox Platform Name" Custom="Custom Platform Name" /> You may already see a couple of example lines in place with fake platform names which you can copy/paste and modify to add your own custom platform names After making your changes, simply save the file, close it, and then reopen LaunchBox The next time you launch a game, you should see your new custom platform name substituting the real platform name in Steam (an easy place to see the title of the game you're playing is in the Steam overlay) Just to reiterate, here is an example of what the aforementioned lines look like in my config file: <CustomPlatformNames> <Platform Name="Super Nintendo Entertainment System" Custom="SNES" /> <Platform Name="Nintendo Entertainment System" Custom="NES" /> <Platform Name="Nintendo Game Boy Advance" Custom="Nintendo GBA" /> <Platform Name="Nintendo Game Boy Color" Custom="Nintendo GBC" /> </CustomPlatformNames> Known Issues There appears to be a significant bug in the Steam Client right now that can cause problems with controller bindings under a variety of situations for certain users. If you launch a rom/emulator with LaunchBox and your controller bindings don't seem to be working, simply exit the game and launch it again. This may happen the very first time you try to launch a game using the SteamLauncher plugin (one time total after freshly installing the plugin, not on every new session in LaunchBox). If it happens frequently, please report the problem so further workarounds can be investigated. Support Unfortunately I don't run a dedicated call center to provide technical support... However, if you need help with any technical issues or bugs (see 'Debug Logs'), want to suggest a new feature (I am very open to any ideas), just want to chat, or anything else related to the plugin, feel free to send me a PM or shoot me an email at the address listed below. Contact Information Alias: Lahma Email: lahma0@gmail.com GitHub Project URL: https://github.com/lahma69/SteamLauncher (Does not yet reflect the changes made in the March 2019 Beta or newer versions. I will be updating the GitHub as soon as I can.) LaunchBox Community Forums Profile: https://forums.launchbox-app.com/profile/89710-lahma/ Debug Logs To provide help with any technical problems or to investigate a bug, I will need a copy of the debug log that is generated whenever debug logs are enabled in the configuration file. To enable debug logs follow these instructions: Close LaunchBox/BigBox (this is important.. changes to the config while LB/BB is running will be overwritten) Locate the file named 'config.xml' in the SteamLauncher directory and open it with a text editor Find the line that looks like this: <DebugLogEnabled>false</DebugLogEnabled> Change the word 'false' to 'true' (do not include the quotation marks) Save the file and close it Now simply repeat whatever behavior was causing the issue and/or bug, and after you're sure you've replicated the behavior, manually close LaunchBox Again, look inside the SteamLauncher directory, but this time looks for a file named 'debug.log' (there may be more than one sequentially named log files if there was an enormous amount of output, but this is unlikely if debugging was turned on just briefly) Zip up the one or more log files and attach them to your message, along with the details of your particular setup (Windows version, 32-bit or 64-bit, LaunchBox version, Steam version, SteamLauncher plugin version, etc). The more information the better. Source Code https://github.com/lahma69/SteamLauncher Legal Stuff ©2017 Valve Corporation. Steam and the Steam logo are trademarks and/or registered trademarks of Valve Corporation in the U.S. and/or other countries.
  11. EpicFail ScummVM Launcher NEW View File Version 3.4.0 Big changes in this one. Some may like it, some may hate it. I now rewrite your ini file to help you out and maintain portability. New game menu item to Configure ScummVM. ScummVM will open with that game selected. No need to scroll through a big list to find/guess the specific game to configure. When using my menu items to configure scummvm, I will automatically rewrite absolute paths as relative paths to your ini file. I also gave you the Configure ScummVM from the Tools drop down. During generation of the *.bat launchers I will check that you have the emulator set up, if not I will fix it for you. Can't change ScummVM path or launcher path now. Just go with it, life will be better. Simple and Advanced modes. Advanced mode is what your used to. Simple mode is one click setup, creates full list of launchers, and emulator creation. It will ask if you want to filter the non english languages. It should be easy if it works the way I intend. click on the Tools->ScummVM Import Tool (simple) click on the Tools->Import->Rom Files to import the bat files as ScummVM games. Now scummvm can be portable easily in 3.3.1-plugin, you can rewriting the ini file. One click will read every single setting out of the ini file and find all absolute paths, check if the path is valid, than convert then to be relative to the launchbox directory. I owe you guys some new instructions. Updated with relative path for better travel! ONLY the DLL is updated... See the update note below lots of new stuff. uses launchbox built in ScummVM by default uses a local scummvm.ini by default, import existing to a local or create new fresh local scummvm.ini, all built in find and remove existing epicfail files. better rom names for smoother mass import BatRunner.exe installed from gui, must stay in your launchbox folder, point to it as your scummvm emulator. (BatRunner.exe is just the ScummVMimport.dll renamed and move to the launchbox main directory. Will prompt you when you create your launcher bat files. So its automatic you won't have do any thing to create it) Just point to it as the application for you scummvm emulator if your using the bat files. Updated filtering with priority duplicate control. ------------------------------------------------------------------------------------------------------------------ Older Version 2.0.5 from the videos ScummVMLauncher.exe NEW AND IMPROVED - NOW WITH RETROARCH FEATURE This is the scummvm launching system I use with launchbox. Most importantly this allows you to get art and videos for BB. It works for me, so I'm sharing it. SETUP LAUNCHERS: Put these ScummVMLauncher.exe files in your scummvm directory same directory as your scummvm.exe. I'm using 1.9.0.2-win32 currently. If you already setup my old launcher you can just delete the files and the launchers folder. This is how I use it. 1st is to open your ScummVM and do a "Mass Add" if you don't know what that is hold the shift button down and the add button on scummvm will change. You could skip this if you already have your games loaded in scummvm, but I recommend starting fresh. After that close the scummvm program and assuming you have the microsoft .net framework installed run the ScummVMLauncher.exe. From the window, select Tools->load scummvm.ini this will attempt to automatically find your file in %appdata%ScummVM/, if its not there just navigate to the directory that you keep it and select your scummvm.ini file, then select open. This will grab the scummvm.ini file selected and parse it. You should see the gui populate and look similar to the screenshot. The gui should be intuitive. Filter the games the way you want to. Select Tools->Generate Launchers SETUP IN LAUNCHBOX: Setup the emulator for ScummVM and pick the ScummVMLauncher.exe file as the executable. import roms - pick the launchers folder to import. Enjoy in BB, with art and videos! Submitter epicfail Submitted 02/17/2017 Category Third-party Apps and Plugins  
  12. Reset Play Count to zero - Plugin View File Resets a games Play Count to 0 (zero). Place the "ResetPlayCount.dll" file into your ..\LaunchBox\Plugins\ folder. *edit* Right click ResetPlayCount.dll, select Properties and click "Unblock". Start LaunchBox. Select just one, multiple or all (Ctrl+A) games. Right-click and then click on "Reset Play Count" located at (or near) the bottom of the popup menu. There is no "Please Confirm" nor "Play Counts have been reset to 0 (zero)" message boxes. It just does it as soon as you click it. (V1.0) *edit* Version 1.1 adds a confirmation message box. ResetPlayCount.dll - 6KB Submitter JoeViking245 Submitted 06/22/2019 Category Third-party Apps and Plugins  
  13. How Long To Beat - Game Length Plugin View File About Plugin that scrapes information from HowLongToBeat.com and adds custom fields with game lengths information. I made this plugin to add length information for certain games, mostly rpgs. This adds 3 custom fields for Main Story, Main + Extra and Completionist length. You can configure which ones you want to add by editing the file HLTBPlugin.xml. Because there's no oficial API from HLTB, I had to parse the HTML, which means that as soon as they change something on the HTML this plugin probably will stop working... Install Extract files (dll + xml) to : Launchbox/Plugins/HLTBPlugin. Config (HLTBPlugin.xml) MainStoryLength: Enable/disable main story length update. Default: true. MainExtraLength: Enable/disable main story + extra length update. Default: true. CompletionistLength: Enable/disable completionist length update. Default: true. MainStoryFieldName: Change main story length custom field name. Default: Main Story Length MainExtraFieldName: Change main story + extra length custom field name. Default: Main + Extra Length CompletionistFieldName: Change completionist length custom field name. Default: Completionist Length Note: If you change the fields names it will not update the games that already have information, so you will end up with duplicated fields with different names and you will have to manually delete them (edit game -> custom fields tab). So config the first time and stick with that. Usage Access the option by right-click a game (only one game, no massive update yet). A window will popup with all the games found and you can choose which one correspond to your game. If there's no results you can manually change the search words (e.g. Metal Gear Ac!d will get no results but you can then change the search to Metal Gear Acid). You can use the "Arrange By" option to order the games by length. Lengths are shown with leading zeroes because is the only way to properly order the games since custom fields are strings and not integers. Tested on version 8.9. I think you need a premium license because custom fields are not supported in free license (not sure). I have no relation with HowLongToBeat.com, if you like their work please go and support them. Submitter matiaspons Submitted 10/26/2018 Category Third-party Apps and Plugins  
  14. Version AddToGamesDb v.Next

    1,420 downloads

    *** Updated for Initial Support for LaunchBox v.Next *** AddToGamesDb: A plugin to help automate the process of submitting all of your game information and images from your collection to the LaunchBox Games Database. About the Plugin This plugin makes use of an application traditionally used in automated testing (Selenium) to automate the process of submitting games to the LaunchBox Games Database. It will open an instance of your default browser (provided that browser is either Chrome or Firefox. If some other browser is your default, it will try to open Chrome), and attempt to submit the selected game to the LaunchBox Games Database based on the information provided in your collection. If the game does not exist in the database, it will create a new game entry and submit it to the database. If you have added additional information or images to a game that already exists in the database, it will enter the title and platform, then pause to let you choose the existing game, then add any additional information from your collection to the LaunchBox Games Database. Installation Instructions Note: For this plugin to work, you will need to have either Chrome or Firefox installed. If you have both installed, it will use whichever you have set as your default browser. If you are using Firefox as your default browser and have enabled Firefox Profiles, please note that this will run under the default profile. For any and all other cases, Chrome is the preferred browser. Unzip everything to the Plugins folder. Usage Instructions Note: If, in editing your collection, you are prompted to download an update for the LaunchBox Games Database, afterward you will need to close and re-open LaunchBox for the plugin to detect the changes. Open LaunchBox and browse to a game that is either missing from the Games Database, has additional information not in the database, or has images not in the database -- right click that game, and select the appropriate option, it will show either: Add Game to LaunchBox Games Database Update Game in LaunchBox Games Database Add New Images to LaunchBox Games Database The first time you run the plugin, you may be prompted to login to LaunchBox Games Database. If so, the plugin will pause here to allow you to login as normal. Check "Remember Me" to skip this step going forward. Your login information is not read or stored in the code, it is stored in Chrome or Firefox's normal AppData cache on your system. If you do not login, the plugin will time-out after 5 minutes and close the browser. Depending on the game, you may be prompted with a screen that identifies similar titles and you will be asked to either select the correct title, or click the button to add a new game. If so, the plugin will pause here until you make your desired selection, then automation will resume for the remainder of the process. Logging By default, the logging is only set to a general "Info" level and up that contains generic start and submission successful messages, along with any errors encountered. If you continue to encounter an error somewhere along the way, please take the following steps: Browse to the plugin's folder -- LaunchBox\Plugins\AddToGamesDb Open NLog.dll.nlog in Notepad or another text editor. Scroll down to the bottom and find the <rules> section of the configuration. Find this line: <logger name="*" minlevel="Info" writeTo="file" /> And change it to this: <logger name="*" minlevel="Trace" writeTo="file" /> Try to submit the problem game, if it is a particular game causing the issue, or another game in general otherwise. Browse to the log file in the plugin's folder -- LaunchBox\Plugins\AddToGamesDb\log\AddToGamesDb.log Feel free to post the error and preceding trace either on the plugin's support page or PM me either the entire log or the part pertaining to the last issue, whichever is easier for you. From there, I'll investigate and make any updates necessary. Supported Fields Auto-population of the following fields is currently supported: Name/Title Platform Release Date ESRB Developers Publishers Genres Wikipedia URL Overview Max Players Cooperative Images Known Issues Context Menu (right-click menu) does not refresh on Audit window. If you update the information for a game in LaunchBox (clicking Edit from the right-click menu for the game), you will need to click away from the game (click some other game, for example), and then right-click on the updated game again for the context menu to update. Even without doing so, however, the correct process should run even though the text and icon on the menu haven't yet updated. A lot of work has gone into stabilizing the initial release and this latest release, but if you encounter any issues, please let me know and I will be glad to work with you to update the plugin accordingly. Thanks, Jason, for providing your amazing software and thanks again to Jason, the LaunchBox staff and the community for your support in developing this plugin.
  15. Version 3.4.0-plugin

    3,244 downloads

    Version 3.4.0 Big changes in this one. Some may like it, some may hate it. I now rewrite your ini file to help you out and maintain portability. New game menu item to Configure ScummVM. ScummVM will open with that game selected. No need to scroll through a big list to find/guess the specific game to configure. When using my menu items to configure scummvm, I will automatically rewrite absolute paths as relative paths to your ini file. I also gave you the Configure ScummVM from the Tools drop down. During generation of the *.bat launchers I will check that you have the emulator set up, if not I will fix it for you. Can't change ScummVM path or launcher path now. Just go with it, life will be better. Simple and Advanced modes. Advanced mode is what your used to. Simple mode is one click setup, creates full list of launchers, and emulator creation. It will ask if you want to filter the non english languages. It should be easy if it works the way I intend. click on the Tools->ScummVM Import Tool (simple) click on the Tools->Import->Rom Files to import the bat files as ScummVM games. Now scummvm can be portable easily in 3.3.1-plugin, you can rewriting the ini file. One click will read every single setting out of the ini file and find all absolute paths, check if the path is valid, than convert then to be relative to the launchbox directory. I owe you guys some new instructions. Updated with relative path for better travel! ONLY the DLL is updated... See the update note below lots of new stuff. uses launchbox built in ScummVM by default uses a local scummvm.ini by default, import existing to a local or create new fresh local scummvm.ini, all built in find and remove existing epicfail files. better rom names for smoother mass import BatRunner.exe installed from gui, must stay in your launchbox folder, point to it as your scummvm emulator. (BatRunner.exe is just the ScummVMimport.dll renamed and move to the launchbox main directory. Will prompt you when you create your launcher bat files. So its automatic you won't have do any thing to create it) Just point to it as the application for you scummvm emulator if your using the bat files. Updated filtering with priority duplicate control. ------------------------------------------------------------------------------------------------------------------ Older Version 2.0.5 from the videos ScummVMLauncher.exe NEW AND IMPROVED - NOW WITH RETROARCH FEATURE This is the scummvm launching system I use with launchbox. Most importantly this allows you to get art and videos for BB. It works for me, so I'm sharing it. SETUP LAUNCHERS: Put these ScummVMLauncher.exe files in your scummvm directory same directory as your scummvm.exe. I'm using 1.9.0.2-win32 currently. If you already setup my old launcher you can just delete the files and the launchers folder. This is how I use it. 1st is to open your ScummVM and do a "Mass Add" if you don't know what that is hold the shift button down and the add button on scummvm will change. You could skip this if you already have your games loaded in scummvm, but I recommend starting fresh. After that close the scummvm program and assuming you have the microsoft .net framework installed run the ScummVMLauncher.exe. From the window, select Tools->load scummvm.ini this will attempt to automatically find your file in %appdata%ScummVM/, if its not there just navigate to the directory that you keep it and select your scummvm.ini file, then select open. This will grab the scummvm.ini file selected and parse it. You should see the gui populate and look similar to the screenshot. The gui should be intuitive. Filter the games the way you want to. Select Tools->Generate Launchers SETUP IN LAUNCHBOX: Setup the emulator for ScummVM and pick the ScummVMLauncher.exe file as the executable. import roms - pick the launchers folder to import. Enjoy in BB, with art and videos!
  16. Version 0.3.0.0

    373 downloads

    This is a test release of Steam Tools for LaunchBox. To install, unzip the contents of the ZIP into LaunchBox's Plugins folder. This plugin now supports being in a subfolder. Current Features: Basic Steam game import functionality Install with Steam function for games (with custom Menu in BigBox) Provided SteamTools.BigBox.DataElement available for inclusion in themes to access SteamTools.Core data Options Menu Automatic custom field if using LB Premium for use in playlists Optional automatic Hiding of uninstalled Steam games Optional automatic Un-Hiding of installed Steam games Background task for automatic updating of Installed/Uninstalled fields Future Features: Steam game Metadata and Media system (requires external database) Current Test Targets: Stable Steam instance detection if Steam is opened after LaunchBox or closed and reopened while LaunchBox is open Import Stability Example use of the SteamTools.BigBox.DataElement plugin in a theme: <UserControl xmlns:st="clr-namespace:SteamTools;assembly=SteamTools.BigBox.DataElement" xmlns:gif="clr-namespace:WpfAnimatedGif;assembly=Unbroken.LaunchBox.Wpf"> <Grid> <st:SteamTools.BigBox.DataElement x:Name="SteamData" SetOnce="True"/> <DockPanel> <Image Name="SteamInstallStatus" DockPanel.Dock="Left" Margin="0,0,5,0" RenderOptions.BitmapScalingMode="HighQuality"> <Image.Style> <Style TargetType="Image"> <Setter Property="Visibility" Value="Collapsed"/> <Setter Property="gif:ImageBehavior.AnimatedSource" Value="pack://siteoforigin:,,,/Themes/Nielk1-CriticalZone/Resources/RatingLoading.gif"/> <Style.Triggers> <DataTrigger Binding="{Binding ElementName=SteamData, Path=IsSteamGame}" Value="True"> <Setter Property="Visibility" Value="Visible"/> </DataTrigger> <DataTrigger Binding="{Binding ElementName=SteamData, Path=IsInstalled}" Value="True"> <Setter Property="gif:ImageBehavior.AnimatedSource" Value="pack://siteoforigin:,,,/Themes/Nielk1-CriticalZone/Resources/SteamInstalled.png"/> <Setter Property="Visibility" Value="Visible"/> </DataTrigger> <DataTrigger Binding="{Binding ElementName=SteamData, Path=IsInstalled}" Value="False"> <Setter Property="gif:ImageBehavior.AnimatedSource" Value="pack://siteoforigin:,,,/Themes/Nielk1-CriticalZone/Resources/SteamNotInstalled.png"/> <Setter Property="Visibility" Value="Visible"/> </DataTrigger> </Style.Triggers> </Style> </Image.Style> </Image> </DockPanel> </Grid> </UserControl> Source Code: https://github.com/Nielk1/LaunchBoxSteamToolsPlugin
  17. Version 2.3.0

    655 downloads

    ***** Now Supporting Random Startup Videos ***** Startup Video Manager: A plugin to manage Startup videos for the user through a clean, simple interface. About the Plugin This plugin provides a menu item that will open a window to allow users to manage their startup videos, and optionally, to activate random startup videos. Random startup videos will be switched out as LaunchBox closes and Big Box opens. New and Returning Features: Reads from a "Startups" folder in LaunchBox\Videos to let the user select their desired startup video. Clicking "Preview" will let the user preview the selected Startup video through a custom VLC player with options for play/pause/stop, forward and backward, volume control and full-screen viewing. Double-clicking the video will also take you to and from fullscreen viewing. Pressing Esc while in fullscreen will also take you back to the normal view. Another way to get back while in fullscreen is to move the mouse to the bottom of the screen where a menu with the video name and a back button will appear. Copies the selected video in LaunchBox\VIdeos\Startups to LaunchBox\Videos and renames it to startup.mp4 so that BigBox will recognize it. Before replacing your existing startup.mp4 file, it checks to see whether or not your current startup.mp4 exists in the Startups folder. If not, it will copy your current startup.mp4 to the Startups folder, adding the Unix timestamp to the filename, to make sure you do not lose any startup video you may not have backed up. New in 2.0.0: Optionally lets the user select Randomize Startup Videos to have the plugin randomly select a startup video and adjust the minimum startup duration each time Big Box is started from LaunchBox. New in 2.0.0: With my system, I found that I needed to slightly tweak the minimum startup time from the actual length of the video. If you find you need to do this as well, in PluginConfig.xml for this that will be covered below. New in 2.1.0: Optionally lets the user update a configuration setting to match their actual load time of Big Box so that random videos will be limited to videos that are at least that long (no looping video on startup). Installation Instructions If you have the old version, BigBoxStartupSelector, delete that folder and unzip the new folder into the LaunchBox\Plugins folder. Create a folder named Startups in the LaunchBox\Videos folder and move all of your startup videos there. You may rename the startup videos in this folder to whatever name you prefer to help you remember each video. Optional Configuration These optional configuration settings can be applied by opening the included PluginConfig.xml in your favorite text editor and changing the appropriate number. StartupTimeOffsetInSeconds: In my case, I found that when setting the Minimum Startup Video Duration to the actual length of the video, even for longer videos, caused the video to start to loop for about a couple seconds. To accommodate this, you can tweak the number of seconds being set as the minimum startup duration for videos through this configuration setting. I had to adjust mine by -2 seconds, but this is 0 by default, which will set the minimum startup duration to the actual length of the video. If you notice that after setting a video through this tool, the video either stops early or starts to loop, you can set this time to adjust all videos accordingly. ActualStartupTimeInSeconds: This setting only applies to randomly-selected videos. If you set this to something other than the default of 0, only videos with at least this startup time will be considered for random selection. How to find out your actual startup time? Get the stopwatch app on your phone ready, go into the Big Box options and set Minimum Startup Video Duration to "No Delay". Now go back to LaunchBox, and as soon as you click to switch back to Big Box mode, start the stopwatch. Stop the stopwatch as soon as Big Box has finished loading. That time, rounded to the nearest second, is the value you should put as your actual startup time. But again, this only applies to randomly-selected videos. If you leave it as the default of 0, all videos will be considered for randomization, but you may have looping if the randomly-selected video is shorter than your actual load time. Usage Instructions Open LaunchBox or BigBox and browse to the Startup Video Manager plugin. Choose the Startup Video you would like to set, then if desired, click Preview to watch the video and make sure that's the one you want. If you'd like random startup videos going forward, make sure to check Randomize Startup Videos in the bottom-left corner. Note: the random selection setting saves as soon as you check or uncheck it. You can click Cancel or close the window from there. The Save button is only if you want to manually select a video to set as your startup video. Once you've decided on a video, click Save and the magic will happen. Otherwise, click Cancel. Enjoy! Please let me know if you run into any issues. Special thanks to angelobodetti for the random startup video idea! Thanks, Jason, for providing your amazing software and thanks again to Jason, the LaunchBox staff and the community for your support in developing this plugin.
  18. PCSX2 Configurator View File PCSX2 Configurator v0.995 Alpha This is a configuration plugin for games being run in PCSX2 through Launchbox. It allows users to configure their games on a per-game basis, and download pre-optimized configurations, from right with LaunchBox. This version is an Alpha, Meaning it has some bugs that I will work with the community to resolve over time. Installation You will first need to have PCSX2 (>1.5.0-dev) setup as an emulator in LaunchBox. If you have used any previous version of PCSX2 Configurator, it is advised that you remove them before installing this version. After this has been setup simply download and extract the zip file, place the "PCSX2 Configurator" folder in your LaunchBox Plugins Directory. Then Start LaunchBox and the plugin will be installed. General Usage Straight out of the box, configs will automatically be downloaded and applied (also updated) for known games, without you (the user) really needing to do much at all. You can disable this on a per game basis using the "Use Remote Settings" flag from a games context (right click) menu in LaunchBox, in the "PCSX2 Configurator" Sub Menu. To create your own config for a game that does not have known settings, you simply use the "Configure" option from within LaunchBox, and then PCSX2 will be started allowing you to configure the settings that you want for that game. You can also use "Configure" to make changes to an existing config (Including Downloaded Ones), though currently any changes made will be overwritten if the config for the game is updated (The Plugin will notify you if this is the case). Settings The Plugin Settings Menu is located in LaunchBox's tools Menu. All settings with "Current" in the name are referring to how the base instance of PCSX2 is currently configured. The default settings make sense in most cases, and these settings should only really be tweaked if you fully understand what the setting actually does. Settings are applied by simply closing the settings window. These Settings will make no meaningful difference to downloaded Configs, and are in-part personal preference. Each of the options is explained breifly below: Use Independant Memory Cards? (default: On) - create a new formatted memory card (In Slot 1) for each game that is configured Use Current Plugin & Bios Files? (default: On) - retains current plugin and bios selection when configuring a game (un-checking this will require them to be re-configured for each game) Use Current GS Window Settings? (default: On) - retains current GS Window Settings (Vsync/Aspect Ratio/Custom Window Size) Use Current Program Log Settings? (default: On) - retains current Program Log Settings, The main purpose of this is to show/hide the console window Use Current Folder Settings? (default: Off) - retains current Folder Settings, This is generally only needed if default folders are not in use (e.g. your folders are in documents, but PCSX2 is in program files) Use Current VM Settings? (default: On) - retains current VM Settings, This Mostly denotes what custom patches/hacks/cheats are enabled, and will usually be overidden by downloaded configs Use Current GSdx Plugin Settings? (default: On) - retains current GSdx (Graphics Plugin) Settings, This will be overidden by downloaded configs Use Current SPU2-X Plugin Settings? (default : Off) - retains current SPU2-X (Sound Plugin) Settings, Not needed in most cases, may be overidden by downloaded configs Use Current LilyPad Plugin Settings? (default: Off) - retains current LilyPad (Controller Plugin) Settings, Not needed in most cases, could be useful if you like to play with a non-standard controller layout for some games Configuartions Directory (default: $PCSX2Dir\inis) - the loaction where per-game configurations are stored, This is in the Emulators ini folder by default though can be changed. you will need to chnage this if your PCSX2 Directory is in Program Files and you are not running LB as Admin This file also contains hidden settings: AllowAllSettings - ensures Presets are disabled and Game Fixes and Speed Hacks are enabled in PCSX2 EnableRemoteSettingsByDefault - Will Disable the "Use Remote Settings" flag for all newly imported games Alpha Testing & Bug Reporting As alluded to earlier this is an Alpha version (I originally wanted to call this release Beta but I don't have that much confidence in my code) and still has a multitude of issues. Most of these are known quantities and are listed in the "Issues" section on Github. If you have experience or notes about any of the known issues, or you feel that a known issue is affecting your experience, please leave a comment on the issue to start a discuission about a potential fix. If you find any other issues or have any other problems please post on the LaunchBox forums or contact me directly. All issues will be fixed/resolved eventually and then this will finally be repackaged as a stable 1.0 release. Credit & History This plugin was created by myself (alec100_94), and began life sometime in June 2017, when I was frustrated with not having a sensible solution for using different Settings with PS2 Games that integrated nicely with LaunchBox. Later that year fellow LaunchBox user Zombeaver messaged me, asking if it was possible to use his pre-made PCSX2 configs with my plugin, so I decided to work with him and add full support for them as a part of the plugin. The plugin has since gained popularity through the LaunchBox community and has evolved into something much more than what is was originally envisoned as. A lot of time and effort has gone into creating this plugin and I would like to say a massive thank you to everyone that has given it a shot. I would also like to say a special thank you to a few (awesome) members of the LaunchBox community who have been great and helped shape this plugin into what it currently is: Zombeaver Spectral ckp neil9000 kmoney Submitter alec100_94 Submitted 05/28/2017 Category Third-party Apps and Plugins  
  19. ImageSearch View File Overview Find Images on the web associated with your Platform and Game combo from AOL, Google, Bing, PicSearch and Yahoo Instructions Unzip ImageSearch and keep the folder ImageSearch and move this to your plugins folder in LaunchBox. What it does Adds Image Search to game detail in BigBox Adds Image Search to the game context menu in LaunchBox Adds an Image Search Configuration to Tools in LaunchBox How it Works Select a game from within LaunchBox and right click to bring up your context menu. choose Image Search and your default browser will display the images from AOL, Google, Bing, PicSearch and Yahoo. Find an image you like and then copy the URL and Paste it in the download form that has also opened and paste the URL. Click download to save your file. The file will be the renamed to the selected Title and save in the Plugin/ImageSearch/downloads folder. In BigBox make sure you have the details screen turned on. select a game and in the details screen choose Image Search and your default browser will display the images from AOL, Google, Bing, PicSearch and Yahoo. Find an image you like and then copy the URL and Paste it in the download form that has also opened and paste the URL. Click download to save your file. The file will be the renamed to the selected Title and save in the Plugin/ImageSearch/downloads folder. Under tools in LaunchBox only you can access the Image Search Configuration. Here you can make various changes 1. Choose if you want to display this in LaunchBox or BigBox 2. Select which Search engines you like to use 3. Change the default path of your Downloaded images. *note if you are using this in BigBox unhide the mouse pointer. Submitter NJDave71 Submitted 05/17/2017 Category Third-party Apps and Plugins  
  20. Startup Video Manager View File ***** Now Supporting Random Startup Videos ***** Startup Video Manager: A plugin to manage Startup videos for the user through a clean, simple interface. About the Plugin This plugin provides a menu item that will open a window to allow users to manage their startup videos, and optionally, to activate random startup videos. Random startup videos will be switched out as LaunchBox closes and Big Box opens. New and Returning Features: Reads from a "Startups" folder in LaunchBox\Videos to let the user select their desired startup video. Clicking "Preview" will let the user preview the selected Startup video through a custom VLC player with options for play/pause/stop, forward and backward, volume control and full-screen viewing. Double-clicking the video will also take you to and from fullscreen viewing. Pressing Esc while in fullscreen will also take you back to the normal view. Another way to get back while in fullscreen is to move the mouse to the bottom of the screen where a menu with the video name and a back button will appear. Copies the selected video in LaunchBox\VIdeos\Startups to LaunchBox\Videos and renames it to startup.mp4 so that BigBox will recognize it. Before replacing your existing startup.mp4 file, it checks to see whether or not your current startup.mp4 exists in the Startups folder. If not, it will copy your current startup.mp4 to the Startups folder, adding the Unix timestamp to the filename, to make sure you do not lose any startup video you may not have backed up. New in 2.0.0: Optionally lets the user select Randomize Startup Videos to have the plugin randomly select a startup video and adjust the minimum startup duration each time Big Box is started from LaunchBox. New in 2.0.0: With my system, I found that I needed to slightly tweak the minimum startup time from the actual length of the video. If you find you need to do this as well, in PluginConfig.xml for this that will be covered below. New in 2.1.0: Optionally lets the user update a configuration setting to match their actual load time of Big Box so that random videos will be limited to videos that are at least that long (no looping video on startup). Installation Instructions If you have the old version, BigBoxStartupSelector, delete that folder and unzip the new folder into the LaunchBox\Plugins folder. Create a folder named Startups in the LaunchBox\Videos folder and move all of your startup videos there. You may rename the startup videos in this folder to whatever name you prefer to help you remember each video. Optional Configuration These optional configuration settings can be applied by opening the included PluginConfig.xml in your favorite text editor and changing the appropriate number. StartupTimeOffsetInSeconds: In my case, I found that when setting the Minimum Startup Video Duration to the actual length of the video, even for longer videos, caused the video to start to loop for about a couple seconds. To accommodate this, you can tweak the number of seconds being set as the minimum startup duration for videos through this configuration setting. I had to adjust mine by -2 seconds, but this is 0 by default, which will set the minimum startup duration to the actual length of the video. If you notice that after setting a video through this tool, the video either stops early or starts to loop, you can set this time to adjust all videos accordingly. ActualStartupTimeInSeconds: This setting only applies to randomly-selected videos. If you set this to something other than the default of 0, only videos with at least this startup time will be considered for random selection. How to find out your actual startup time? Get the stopwatch app on your phone ready, go into the Big Box options and set Minimum Startup Video Duration to "No Delay". Now go back to LaunchBox, and as soon as you click to switch back to Big Box mode, start the stopwatch. Stop the stopwatch as soon as Big Box has finished loading. That time, rounded to the nearest second, is the value you should put as your actual startup time. But again, this only applies to randomly-selected videos. If you leave it as the default of 0, all videos will be considered for randomization, but you may have looping if the randomly-selected video is shorter than your actual load time. Usage Instructions Open LaunchBox or BigBox and browse to the Startup Video Manager plugin. Choose the Startup Video you would like to set, then if desired, click Preview to watch the video and make sure that's the one you want. If you'd like random startup videos going forward, make sure to check Randomize Startup Videos in the bottom-left corner. Note: the random selection setting saves as soon as you check or uncheck it. You can click Cancel or close the window from there. The Save button is only if you want to manually select a video to set as your startup video. Once you've decided on a video, click Save and the magic will happen. Otherwise, click Cancel. Enjoy! Please let me know if you run into any issues. Special thanks to angelobodetti for the random startup video idea! Thanks, Jason, for providing your amazing software and thanks again to Jason, the LaunchBox staff and the community for your support in developing this plugin. Submitter UnderwoodNC Submitted 05/25/2017 Category Third-party Apps and Plugins  
  21. If anyone could help me with a quick question on my plugin download page, I would greatly appreciate it. I'm the author of the "SteamLauncher" plugin, and I just spent the last hour trying to help a user with an issue he was having with my plugin. I finally figured out what the problem was, and it had nothing to do with my plugin, and was quite unexpected. After the Steam client updated, I had to make some changes to my plugin to maintain compatibility, so I uploaded an updated version (v0.9.0.1). The problem is, the main "Download" button on the plugin page still downloads the old version of the plugin, which for all intents and purposes is totally non-functional now. Although a link to the updated version of the plugin is available at the bottom of the plugin page, most people by default are just going to click the download button and not pay attention to anything else. Am I doing something wrong here, and if so, how do I change the version that the download button points to. If I'm not doing anything wrong, is there some way to fix this? Thanks!
  22. Hiya , i have been working on this plugin for a while now , it was showing and working earlier today , now my plugin which is around 1000 lines of code will not show when i click it? any ideas anyone please? Superfurry
  23. I'm not sure if this is really the right place to inquire about such a thing, but I'm simply trying to gauge if there is any interest amongst the LaunchBox community for a Steam launcher/proxy plugin for LaunchBox. If anyone has used Nielk's "GameLaunchProxy" or my more recent fork of it (to make it work again after Steam API changes broke it), it would be similar, but with a much more narrow focus... and instead of being an external application, I would wrap the functionality into a LaunchBox plugin that would require no prior setup or even knowledge of how it works or what it is doing. You would basically just right click the game you want to play in LaunchBox and click "Play via Steam" (or something similar). For anyone who hasn't used GameLaunchProxy before, let me briefly explain the concept so that you can tell me if it would be of use to you or not. Steam has the ability to add non-Steam shortcuts (games) to its interface, so that you can launch games through Steam that you didn't buy/download via Steam. There are a lot of reasons/benefits one might want to do this, but a few of the primary reasons are Steam's EXCELLENT and wholly unique controller binding abilities through the Steam Overlay (allow you to create multi-tiered radial menus, touch menus, multi-layered advanced controller configurations, and probably most importantly, per-game controller configurations), to keep track of gameplay statistics (last played, total time played, etc), and to share gameplay status with friends (ex: when you're playing Super Mario Bros (NES), it displays that as your status to all of your friends on Steam). For any hardcore emulator/rom players who have ever tried to take advantage of this behavior, they will know there is a problem however. You must add a separate shortcut to Steam for each and every emulator+rom that you want to play through Steam. For some of us with collections of thousands of roms (and the desire sometimes to play a single rom in different emulators), this becomes tedious and impractical very quickly. What this plugin would allow is for you to keep your entire collection of roms/emulators organized in LaunchBox, and without having to add a single shortcut to Steam, you would be able to launch any combination of emulator+rom through Steam, giving you access to the Steam overlay, per-rom/emulator/game controller configurations (that are saved/remembered automatically). The plugin will use Launchbox metadata for the rom/game name and platform name in order to "label" your current Steam gaming session. For example, if you are playing "Super Mario Bros." on the NES, when you pull up the Steam overlay, you (and your Steam friends) will see the following as the name of your current play session (your controller profiles will be labeled as such too): "Super Mario Bros. (NES)" Additionally, your Steam client won't be littered with a thousand shortcuts (the plugin will only add 1 hidden shortcut that it will change dynamically to "proxy" launches between LaunchBox and Steam). Like I said previously, you would only need to bring up the context menu in Launchbox on whatever game/rom you want to play, and you would be able to click either "Play via Steam", or you could go into the "Launch With" menu and choose to launch the rom with any of the other emulators you have configured through Steam. Currently, you can accomplish this using my current build of GameLaunchProxy, but it requires a lot of setup, configuration, and quite-frankly complicated understanding of what is going on under the hood (gets even more complicated when you start considering relative paths to roms and emulators). I suspect that a lot of people would find this plugin useful if they knew of the benefits and if it was extremely simple to use, but maybe I'm wrong. That is why I'm here. I simply want some feedback from people in the community if they would find this useful and if they would actually use it. I've already rewritten the core of GameLaunchProxy from scratch, and I was going to implement this into a new app that majorly simplifies the entire app's concept, but as I thought it over, I decided it may be much more useful to just write the functionality directly into a LaunchBox plugin (accomplishing the ultimate level of simplicity). Anyways, if any of you made it though that doctoral thesis, please give me some feedback and let me know what y'all think. Since I've already written most of the core functionality, it shouldn't take a lot of time for me to implement it into a plugin if I get positive feedback from enough people. Thanks!
  24. While playing around with RetroArch 1.60 at work today, i threw this plugin together to quickly launch netplay sessions. It works great in lan but i haven't tested it via WAN... you'll probably need a good connection for it to work decently over wan for now. I haven't added the framesettings etc. yet, it's as simple as can be. If you want to test it, make sure that the host and client both use the same core in retroarch and EXACTLY the same rom, retroarch will say nope otherwise Here's a short video of me testing it locally with mk2(pool fatality, pit fatality, fatality!) f yeah : If there's any interest i'll update this with more features and saving of the nickname etc. LBP_SimpleRetroarchMultiplayer.dll
  25. Hi, I'm working on a BigBox plugin and an associated Android app to enable a tablet to be used as a side screen / auxiliary screen to show marquees / banners / control layouts and pdf manuals for the game that is currently selected in Big Box. The idea is that the tablet would be automatically synchronized via WiFi to the selected game in Big Box, and it would show relevant data for that game. This could be especially handy to show the control layout and manual for a game when using Big Box in a cabinet. I was wondering how much interest there would be in the community for me to release this plug in to everybody? Also, @Jason Carr, can I use the Big Box logo, or a derivative of it as the icon for the Android app? Thanks!
×
×
  • Create New...