Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'launcher'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LaunchBox
    • 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
    • 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
  • 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

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Found 14 results

  1. SteamLauncher View File SteamLauncher Plugin for LaunchBox 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 click the following link: Send Friend Request to lahma0 (steam://friends/add/76561198237461630) 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'. Introduction SteamLauncher is a LaunchBox plugin designed to allow roms/emulators to easily be launched within Steam, directly from the LaunchBox/BigBox interface, without any complicated setup or technical know-how. Simply open the LaunchBox/BigBox context menu for any title and select the option labeled, "Launch via Steam". March 2019 Beta: The new beta works differently than described above. Please read the new “How to Use” section in the documentation below. 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 (March 2019 Beta) 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.6.1+ .NET Framework 4.7+ (March 2019 Beta) 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 Original/Old Plugin 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.) March 2019 Beta 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 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) 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: 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  
  2. Kodi addon for LaunchBox View File Launches LaunchBox in Big Box mode from within Kodi - It will close or minimize Kodi, launch LaunchBox in Big Box mode and when Big Box is exited Kodi will restart or maximize, with the option to run programs pre/post LaunchBox. It works with Windows only. Features: BigBox Startup video and splash screen support BigBox Updater support Pre/Post scripts Minimize or close Kodi option Launcher Helper script version check Supports Kodi 16, Kodi 17, Kodi 18 and Kodi Windows Store versions. Requirements: Windows PC LaunchBox Premium Kodi 16, 17, 18 or Kodi Windows Store for Windows Known Issues: Due to Windows Store's UWA security restrictions, user must set a save directory under the plugin's Advanced Settings to a directory of the user choice where the plugin's ahk helper script and icon file can be saved. Install instructions: Use 'Install from Zip' in Kodi and browse to the directory the plugin's zip was downloaded to and select it. Configuration: This plugin requires the user to set the location of their LaunchBox directory in the addon settings before first use. eg. C:\Users\<username>\LaunchBox\ PLEASE NOTE: THIS PLUGIN WILL PRODUCE AN ERROR DURING INSTALL IN KODI ON ANY OPERATING SYSTEM THAT CANNOT RUN LAUNCHBOX. SINCE LAUNCHBOX IS CURRENTLY WINDOWS ONLY THAT IS THE ONLY OPERATING SYSTEM THE PLUGIN CURRENTLY SUPPORTS. ATTENTION: WILL NOT WORK ON ANDROID (BOX, SMART TV, ETC.), IOS or MAC AND LINUX. Submitter CoinTos Submitted 01/25/2017 Category Third-party Apps and Plugins  
  3. Version Beta 0.9.1.0

    405 downloads

    SteamLauncher Plugin for LaunchBox 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 click the following link: Send Friend Request to lahma0 (steam://friends/add/76561198237461630) 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'. Introduction SteamLauncher is a LaunchBox plugin designed to allow roms/emulators to easily be launched within Steam, directly from the LaunchBox/BigBox interface, without any complicated setup or technical know-how. Simply open the LaunchBox/BigBox context menu for any title and select the option labeled, "Launch via Steam". March 2019 Beta: The new beta works differently than described above. Please read the new “How to Use” section in the documentation below. 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 (March 2019 Beta) 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.6.1+ .NET Framework 4.7+ (March 2019 Beta) 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 Original/Old Plugin 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.) March 2019 Beta 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 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) 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: 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.
  4. Version 1.5.4

    7,742 downloads

    Launches LaunchBox in Big Box mode from within Kodi - It will close or minimize Kodi, launch LaunchBox in Big Box mode and when Big Box is exited Kodi will restart or maximize, with the option to run programs pre/post LaunchBox. It works with Windows only. Features: BigBox Startup video and splash screen support BigBox Updater support Pre/Post scripts Minimize or close Kodi option Launcher Helper script version check Supports Kodi 16, Kodi 17, Kodi 18 and Kodi Windows Store versions. Requirements: Windows PC LaunchBox Premium Kodi 16, 17, 18 or Kodi Windows Store for Windows Known Issues: Due to Windows Store's UWA security restrictions, user must set a save directory under the plugin's Advanced Settings to a directory of the user choice where the plugin's ahk helper script and icon file can be saved. Install instructions: Use 'Install from Zip' in Kodi and browse to the directory the plugin's zip was downloaded to and select it. Configuration: This plugin requires the user to set the location of their LaunchBox directory in the addon settings before first use. eg. C:\Users\<username>\LaunchBox\ PLEASE NOTE: THIS PLUGIN WILL PRODUCE AN ERROR DURING INSTALL IN KODI ON ANY OPERATING SYSTEM THAT CANNOT RUN LAUNCHBOX. SINCE LAUNCHBOX IS CURRENTLY WINDOWS ONLY THAT IS THE ONLY OPERATING SYSTEM THE PLUGIN CURRENTLY SUPPORTS. ATTENTION: WILL NOT WORK ON ANDROID (BOX, SMART TV, ETC.), IOS or MAC AND LINUX.
  5. 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  
  6. Version 3.4.0-plugin

    2,222 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!
  7. Overview TypeXtra was designed to make setting up TypeX and Nesica Systems more straightforward. There are lots of different game sets out in the wild, so setup can be quite a confusing job. This aims to make it a few clicks job. TypeXtra does not come with any "ROMS." That would be illegal. If you own the system you are aiming to emulate, then you can secure a "ROM" image of the game to emulate on your PC. Once you have the ROM/s you want, TypeXtra aims to make setup a 3 step process: Point it to the directory/s in which your ROM/s reside Click "Autoscan." It will automatically identify most games if their folders contain a game.inf file (some roms don't) Click "Setup Games" to install an assured set of support files which will make the game run. This does depend on your ROM files Features Import other "Game Service" sets - ones that are designed to ensure games boot OK. Some of these have modified game executables, therefore they're not included with this distribution. However, see elsewhere for instructions on obtaining and importing. Import "HD Exe" sets. The original game executables ran at lower resolutions. Some modified executables have been produced to have these games work at higher resolutions (not just stetch to fill your display, but to actually render at higher resolutions). Customise what files launch the game, what file to monitor for the game ending and what controls setting application to use on a game-per-game basis. Runs invisibly from command line - once you have your games set up, send it the short ort long game name and it will boot the game and close itself once the game executable has stopped. This helps with front end setups, where the front end will monitor for the temrination of the launch application (in this case, TypeXtra). Create shortcuts pointing towards the game launch files in either the 'long' or 'short' game format. This can be used to have a front end launch a file directly by executing the shortcut, or, more helpfully, get the correct command line parameter to pass to TypeXtra to launch the game. Audits the exe files and compares against a database of known working vs known rubbish roms (database in early stages) Screenshot Video Download and further info https://sites.google.com/view/magoarcade/software/typextra
  8. Version 1.1

    17 downloads

    GamestreamLauncher is a simpler launcher application to help assist with operations to be completed before and after a gamestream session. This can be used to launch any application, but I find it works great with BigBox as a launch point for my PC and emulator games. Workflow on Gamestream Session start: Disable GPU Miner through Awesome Miner if running Disable non-primary monitors if present Run a custom script Launch Game (BigBox) Workflow on Session end: Run a custom script Enable non-primary monitors that were previously disabled Enable the GPU Miner through Awesome Miner if it was previously disabled Close the Gamestream session gracefully Installation: Copy the extracted folder to your desired location. Run GamestreamLauncher.exe to configure the launcher. Add a custom game in Geforce Experience that points to GamestreamLauncher.exe. The launcher is configured with the config utility when launching it for the first time. You can run the config utility again by deleting the user.config file that can be found at %localappdata%\GamestreamLauncher under the proper version. Known NVidia GameStream issues this launcher will resolve: Launching a game while a miner is active GameStream will "flicker" when multiple monitors are active during the stream - https://forums.geforce.com/default/topic/1022778/gamestream/flickering-with-gamestreaming-on-new-windows-builds-/ The launcher is open source and can be found on github here: https://github.com/loueradun/GamestreamLauncher
  9. GamestreamLauncher (For Custom Scripts, Multiple Monitors, Miners, etc) View File GamestreamLauncher is a simpler launcher application to help assist with operations to be completed before and after a gamestream session. This can be used to launch any application, but I find it works great with BigBox as a launch point for my PC and emulator games. Workflow on Gamestream Session start: Disable GPU Miner through Awesome Miner if running Disable non-primary monitors if present Run a custom script Launch Game (BigBox) Workflow on Session end: Run a custom script Enable non-primary monitors that were previously disabled Enable the GPU Miner through Awesome Miner if it was previously disabled Close the Gamestream session gracefully Installation: Copy the extracted folder to your desired location. Run GamestreamLauncher.exe to configure the launcher. Add a custom game in Geforce Experience that points to GamestreamLauncher.exe. The launcher is configured with the config utility when launching it for the first time. You can run the config utility again by deleting the user.config file that can be found at %localappdata%\GamestreamLauncher under the proper version. The launcher is open source and can be found on github here: https://github.com/loueradun/GamestreamLauncher Known NVidia GameStream issues this launcher will resolve: Launching a game while a miner is active GameStream will "flicker" when multiple monitors are active during the stream - https://forums.geforce.com/default/topic/1022778/gamestream/flickering-with-gamestreaming-on-new-windows-builds-/ Submitter loueradun Submitted 10/12/2018 Category Third-party Apps and Plugins  
  10. uPlayService_Killer.7z View File Running uPlay from a non administrator account requires yuo to enter a password everytime you launch a game, also leaving a game brings the uPlay ui forward blocking launchbox access. I created a few scripts to get around this. There is some preperation required for each of the uPlay games, i only have one Assassin's Creed Origins and it works perfectly for me. The only downside i can see using these scripts is that your saved games are not synced to the cloud. Lets me know how the scripts work for other uPlay games. Autoit is required to edit and build the required exe file You can download that here AutoIt Download 1: Right Click "uPlayService_Killer.au3" and edit script. amend "F:\Program Files (x86)\uPlay\Ubisoft Game Launcher\UplayService.exe"to the location of your local copy is installed, save the changes and complie to an exe file. 2: Right click rungame.bat and amend the name of the game/exe you want to run. 3: Locate and open the install folder of were you installed uPlay. 4: Locate the file "UplayService.exe" and rename it to anything i.e "UplayService.ex" 5: Copy both rungame.bat and uPlayService_Killer.exe to the game folder. 6: Double click rungame.bat to run the game or point launchbox to the rungame.bat file. Submitter xiaumaster Submitted 04/14/2018 Category Third-party Apps and Plugins  
  11. Version 1.0.0

    8 downloads

    Running uPlay from a non administrator account requires yuo to enter a password everytime you launch a game, also leaving a game brings the uPlay ui forward blocking launchbox access. I created a few scripts to get around this. There is some preperation required for each of the uPlay games, i only have one Assassin's Creed Origins and it works perfectly for me. The only downside i can see using these scripts is that your saved games are not synced to the cloud. Lets me know how the scripts work for other uPlay games. Autoit is required to edit and build the required exe file You can download that here AutoIt Download 1: Right Click "uPlayService_Killer.au3" and edit script. amend "F:\Program Files (x86)\uPlay\Ubisoft Game Launcher\UplayService.exe"to the location of your local copy is installed, save the changes and complie to an exe file. 2: Right click rungame.bat and amend the name of the game/exe you want to run. 3: Locate and open the install folder of were you installed uPlay. 4: Locate the file "UplayService.exe" and rename it to anything i.e "UplayService.ex" 5: Copy both rungame.bat and uPlayService_Killer.exe to the game folder. 6: Double click rungame.bat to run the game or point launchbox to the rungame.bat file.
  12. 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!
  13. knightCrawler

    Command lines help

    I have a nesicaxlive game which uses two files one to decrypt the game and the other to launch the game so I want to know if there is a way to launch the two files 1 then 2 Thanks
  14. First of all I only recently purchased a premium license and this is my first post to the forum. So hello everyone! I'm excited for learning about how to make launchbox/bigbox work for me. It's already working pretty good. I'll have some tips/tricks and/or scripts to contribute in the near future My question is about some Windows/Steam games using non-skippable launchers (Final Fantasy IV for Steam being my first example found). There's a FF4.exe as well as a launcher.exe (I don't have it in front of me, close enough) but the FF4.exe just brings up the launcher anyway. I remembered that autohotkey had a feature that will search the screen for a match to a given image and perform actions based on a match (like move mouse there/left click). I even found a user created ahk function that's supposed to make this really easy to do. All I'm really asking is if anyone knows of an existing script like this in the forum or some place else? I mean a drop-in-and-works sort of a thing. Doesn't have to be AHK of course. Windows game click-play-on-the-launcher scripts generically, not necessarily the FF4 one specifically. I thought I should ask since figuring it out on my own with the AHK function will take probably between 1 and 10 hours of effort to figure out. That is what this sort of thing usually takes me at least. No need for that if the thing already exists. Here's the thread for the AHK function I mentioned. If anybody was interested: https://autohotkey.com/boards/viewtopic.php?f=6&t=18719
×