Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'controller'.



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

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 61 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 copy/paste the following URL into your address bar: steam://friends/add/76561198237461630 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'. 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. Version Beta 0.9.3.0

    508 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 copy/paste the following URL into your address bar: steam://friends/add/76561198237461630 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'. 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.
  3. Hi guys, i have a problem with the controller order on W10. I built a retrogame consolle (it's just a PC with a nice case) with BigBox and lot of things inside. Pretty good, what's the matter.... sometimes, randomly but most of time when i move my consolle from on TV to another, W10 changes the controller order.... 1 becomes 2 and viceversa. Is there a way to finally fix the controller order in W10? I searched on web but nothing usefull. Thank you very much.
  4. Version 1.0.0

    115 downloads

    Here are images I Googled/edited/took pictures myself of close up controllers for each platform. When put into the individual Fanart folders under "Images\Platforms" they will be used in the startup and shutdown screens if there is no fanart for the game selected. Platforms Include: Arcade Atari 2600 Atari 5200 Atari 7800 Atari Jaguar Atari Jaguar CD Atari Lynx Nintendo Entertainment System Nintendo Famicom Nintendo Famicom Disk System Nintendo Satellaview Super Nintendo Nintendo 64 Nintendo Gamecube Nintendo Wii Nintendo Wii U Nintendo Game Boy Nintendo Game Boy Color Nintendo Game Boy Advance Nintendo DS Nintendo 3DS Nintendo Virtual Boy Sega SG-1000 Sega Master System Sega Genesis Sega 32X Sega CD Sega Saturn Sega Dreamcast Sega Game Gear Sony Playstation Sony Playstation 2 Sony PSP NEC TurboGrafx-16 NEC TurboGrafx-CD 3DO Interactive Multiplayer Philips CD-i SNK Neo Geo Pocket SNK Neo Geo Pocket Color Installation: Just extract the zip file into the "Images" folder in your Launchbox directory.
  5. Hi! I've built a bartop arcade cabinet ( https://www.youtube.com/watch?v=CgrQeYAnecY ) to play retrogames and steam games on, but i'm having trouble making Steam play well with my "Sinoarcade" control interface (i really don't want to use xboxce360) . What control interface would you recommend that would 100% work with steam? If i remember correctly, you should be able to map any d-input controller i Steam settings "controls" and enable "Use Generic gamepad"-option in order to make Steam do the "conversion" from here. I tried mapping my Sinoarcade, but had problems mapping the analog stick x and y axis
  6. Platform Fanart for Startup & Shutdown Screens View File Here are images I Googled/edited/took pictures myself of close up controllers for each platform. When put into the individual Fanart folders under "Images\Platforms" they will be used in the startup and shutdown screens if there is no fanart for the game selected. Platforms Include: Arcade Atari 2600 Atari 5200 Atari 7800 Atari Jaguar Atari Jaguar CD Atari Lynx Nintendo Entertainment System Nintendo Famicom Nintendo Famicom Disk System Nintendo Satellaview Super Nintendo Nintendo 64 Nintendo Gamecube Nintendo Wii Nintendo Wii U Nintendo Game Boy Nintendo Game Boy Color Nintendo Game Boy Advance Nintendo DS Nintendo 3DS Nintendo Virtual Boy Sega SG-1000 Sega Master System Sega Genesis Sega 32X Sega CD Sega Saturn Sega Dreamcast Sega Game Gear Sony Playstation Sony Playstation 2 Sony PSP NEC TurboGrafx-16 NEC TurboGrafx-CD 3DO Interactive Multiplayer Philips CD-i SNK Neo Geo Pocket SNK Neo Geo Pocket Color Installation: Just extract the zip file into the "Images" folder in your Launchbox directory. Submitter BlazingRyuu Submitted 03/16/2019 Category Platform Backgrounds  
  7. Ok. I don't know if I classify as a noob since I have been dabbling in MAME, Hyperspin, RocketLauncher, etc.. a little here and there for many years. However, I feel this should be a noob question but I can' t figure it out. Every time I start down the path of building / rebuilding an emulation system, the reason that I always quit is controller issues. Lets face it... It doesn't matter how pretty we make it, if it is not easy to use.... As I think back... every time I have failed or quit is because I can't,or don't, have the fortitude to make even the simplest xbox360 controllers work with MAME and/or everything else. I moved to BigBox a little while ago.. setup a few systems, with pretty good success, but MAME is the beast I really want to tame. I grew up in the arcade and I would love to have every quarter back that I ever plunked into a machine. I would love a magic bullet that already has all of the cntrlr settings set in a config file that I just have to drop somewhere and call it a day.... but based on what I have read, that may not be as easy at it sounds... I've read where people have done that and then it works until they reboot and the devices get all wonky. So, I'm breaking down and asking for help. I have an alienware alpha machine with 3 xbox 360 controllers hooked up via a USB port expansion device. ( the alpha only has so many usb ports and I use a keyboard and external hard drives) I try to map my player 1, 2 , 3 start and coin buttons but I cannot get Joy2, Joy 3 to map. Only my player1 xbox will map buttons in launchbox. I can use the keyboard, but I still cant start some multiplayer games correctly.. like Gauntlet II. Sorry for the long post. If you have an answer for that magic bullet and can help me load a cntrlr file and keep it working, I would love that, but at the least I need help with Joy2 and 3. Thanks!!!
  8. Hi all, First post, new Bigbox license owner. When I launch a MAME game from Launch box, it works great with my PS4 controller. I spent the last hour mapping everything. All is good. However, in Bigbox, when I launch the same game, the controller doesn't work. In MAME, when I press TAB and edit the controls, and I try to map the control to my controller, it's not sensing I pressed a button. For example, I select P1 UP, I press enter, and then UP on the controller.... nothing... I quit Bigbox, boot Launchbox, and it works perfect. Any ideas? Sorry if this is a repeat question.
  9. Pre-configured SumatraPDF + JoyToKey to view PDF's with a controller in LaunchBox View File This is a pre-configured SumatraPDF and JoyToKey to use for viewing PDF manuals in LaunchBox with a controller. It was setup with a DS3 using ScpTools Reloaded so it should also be compatible with a Xbox 360 controller. I have not tested it with any other controllers. The zip file contains SumatraPDF, JoyToKey and a AHK script that will launch JoyToKey in a hidden state, then SumatraPDF and when SumatraPDF is closed it will kill JoyToKey. For it to display PDF's in LaunchBox you need to configure the Windows default PDF viewer as 'SumatraPDF-JoyToKey.exe'. You can update either SumatraPDF or JoyToKey by placing the contents of the portable installs in the root directory. Script usage outside of LB is: "c:\path\to\SumatraPDF-JoyToKey.exe" "c:\path\to\pdf\file.pdf" Controls: D-Pad/Left analog stick: Up Down Left Right Right analog stick Up+Down/L+R triggers: Zoom in/out L+R bumpers: Go to First/Last page Cross (Green A on 360): Next page Square (Blue X on 360): Rotate image 90' Triangle (Yellow Y on 360): Cycle through zoom/fit to screen modes (reset zoom) Circle (Red B on 360): Exit SumatraPDF Forum thread Credits: JoyToKey SumatraPDF AutoHotKey Submitter teeedubb Submitted 03/22/2017 Category Third-party Apps and Plugins  
  10. So I just got going with BigBox and I'm loving everything so far. But I need one thing to work that I'm having a helluva time with. Basically I have an Xbox360 Arcade Stick plugged in at all times as my go-to player1 controller. Works great in BigBox/Emulators. Fantastic. Now, I also want a 2nd controller that I can keep plugged in as player2, which is a PS4 dualshock controller. It's working... kind of. I'm able to use the player2 (PS4) controller in BigBox, but the button mappings are off. In particular the start button is mapped to L2 and no button combos seem to execute the emulator shutdown command (set to back + start on my xbox360 player1 controller). So, that's a problem. Why don't i just launch games with the player1 controller, you ask? Well, because I don't only want the player2 controller for an ACTUAL player2, but also as an alternative controller (when I want to use the pad rather than arcade stick). If I can even sort this bit of business out, my next problem is in Retroarch. Retroarch registers the player2 (PS4) controller fine, but when I start a game with it, it apparently sets it as player1, but of course I want to have different button mappings which I would set to player2 in Retroarch, but it's forcing player1's mappings. Any help with any of this would be greatlly appreciated.
  11. Hi guys, i have a premium LB account and have seen the option to be able to exit games inside big box but I don’t have a clue of how to set it up or if this affects on the current game controls. For instance, I’d like something like in RetroArch when you can configure going back to main menu via start+select buttons. Thanks in advance
  12. Hi guys, I have just watched the tutorial on how to play Game Cube and Wii games on LaunchBox and what I don't get is the way to layout the xbox 360 controller. I have done it as in the video but I suspect maybe when selecting "classic" instead of nunchuk you go under a sub-setup, not the main layout on the controller section? I have attached a couple of pics showing my configuration. Hope you guys can help Many thanks in advance!
  13. Hello, i installed Launchbox, RetroArch und the Stella Core for Atari 2600. I would like to use the left stick instead of the directional pad. I tried to change the settings in RetroArch, but it had no effect. What is my mistake?
  14. Hi everyone, I am having some difficulties with getting my X-Arcade Tankstick to work in BigBox. I have not long converted from Hyperspin, where the X-Arcade was self explanatory and a breeze. Though, unfortunately I am not finding it so here. I have gone to BigBox > Options > Controller > and ticked "Enable Game Controllers" and "Use All Controllers". Where it says "Device:" there is nothing there. Is that because these options only apply to an actual game-pad controller instead of the X-Arcade which is mapped as a keyboard? If so, does that mean in the options I do not worry about "Controller Buttons" but just "Keyboard Mappings" instead? Also, regarding controls, using Nestopia as an example. I have gotten to the stage with BigBox where I can launch Nestopia full-screen into a chosen game but have no idea how to exit out of the emulator back into BigBox. Is someone able to point me in the right direction? Because at least to me it certainly is not obvious how (I am probable just a doofus). I have found other topics in the forum here about the X-Arcade from years ago but there were of little help as they were from a time where LaunchBox/BigBox seemed to not have compatibility issues with the X-Arcade? Thank you in advanced.
  15. Hey guys I’m going to build my own 4 player joystick so I’m selling my 2 player recroommasters xtension emulator edition “nes” version to raise some extra dough. Its in great shape, have only had it about 6 months. With 3 young kids and a full time job it hasn’t seen much use. here’s the link on Ebay: https://m.ebay.com/itm/Xtension-Two-Player-Control-Board-Emulator-Edition/272920879451?hash=item3f8b5a215b:g:Ew4AAOSwsYpaAxEv if you’d rather make an offer directly you can email me pattonthompson@gmail.com
  16. one problem I run into all the time with emulators and pc games is if the controller isn't turned on \ plugged in before I start said application then it doesn't see it at all after I do turn on the controller. This was the main reason I went to retroarch for emulation and also why I also started using retroarch for mame. There are still other emulators and plenty of pc games I play. But having to quit then restart or if a second player wants to join just to get the controllers recognized. Sometimes the controller settings get wiped and I have to set it up all over again. Is there a program like x360ce but for dinput so I can setup a "virtual" controller then emulator/game thinks is always plugged in? Like x360ce setup multiple controllers player1, player2, etc. So I can just start these applications then pick up my wireless Xbox 360 controller turn it on and start playing?
  17. Ok, just getting Retroarch 1.4.1 configured. I have a few custom setups for controls, all with the usual xInput controller (XB1). Some changes I've noticed: - Control input changes now apply to the Retroarch UI. Has this always been the case? For instance when configuring NES control, I prefer to have left button (x) be NES B and down (A) be NES A. This makes it more comfortable as the right thumb rests on the inside buttons. This also appears to be changing the "confirm" and "cancel" buttons in the UI as well to X as confirm and A as cancel. I don't recall this happening in 1.3.6. - I can't seem to double up controls. I have NES directional control mapped to the d-pad, but I would also like the left analog stick mapped to NES directional control. This gives the player (my guests) the choice of using either the joystick or d-pad. It worked fine in 1.3.6 but I can't seem to figure out how to do this in the new version.
  18. Hey guys, I have a PS4 controller and a Gamecube controller. I like to play Dolphin with the Gamecube controller, but once it's wired sometimes I give up to play to avoid the chance to fall, hit my head, and die when connecting the cable (or just to avoid fatigue). So I like to play with the wireless PS4 controller sometimes as well. For now I have two separated folders for dolphin (using the portable.txt) and I have 2 emulators set on Launchbox, each one with one config for controller. The problem is: I couldn't figure out how to merge the save files. Does anyone knows any other way that can I have 2 controller settings for dolphin and use on Launchbox/BB quickly?
  19. JoyToKey Profiles for LaunchBox and Rocket Launcher View File What's New for Version 1.1.0: ADDED 7 New Systems (80 TOTAL) + LB/HS/RL/Default profiles. New systems include Sega Model 1, Sega System 16, Sega System 24, , Sega X Board, Sega Y Board, Pop-Cap, and Microsoft MS-DOS. Changed the ESC key functionality to buttons 7 + 8 (COIN+START). You must now press both to exit the game. Placed the ESC key location on Button 25 (a dummy location good for using combo buttons). Changed Button 5 to TAB. Changed Button 6 to P (PAUSE). Changed Button 9 to C. Changed Button 10 to V. Changed Button 11 to Z. Changed Button 12 to X. I'll see how this configuration works for me for the time being. If it's a pain or something is not quite right, I'll continue tweaking it until I find what's best. *********** BACK UP YOUR OLD PROFILES IN CASE YOU DON'T LIKE THE CHANGES *********** If you use Rocket Launcher as the primary emulator for Launch Box then this is for you. I created about 75 profiles for various systems, added them to a RAR archive, and attached to this post. All you have to do is unrar and place the folders within the archive into your ..\RocketLauncher\Profiles\JoyToKey directory. For example, mine is -- ..\RocketLauncher\Profiles\JoyToKey. You may need to edit the profiles so they are more to your liking or work correctly with your setup. I use the default MAME setup for everything. If you want to change one or all of them, all you have to do is edit only one CFG file, copy the CFG file to every other folder, and rename the CFG file and FOLDER to the name of the emulator you're using for the system. For example -- I use Rocket Launcher as the emulator for ALL my systems but, once RL starts, I use Stella for the Atari 2600. My path is then ..\RocketLauncher\Profiles\JoyToKey\Atari 2600\Stella\Stella.cfg Maybe you don't use Stella for the Atari 2600 but use RetroArch. Here's how to change it: You would simply rename ..\RocketLauncher\Profiles\JoyToKey\Atari 2600\Stella\Stella.cfg to ..\RocketLauncher\Profiles\JoyToKey\Atari 2600\RetroArch\RetroArch.cfg.It's the same path\folder\file but the innermost folder and cfg file have simply been renamed to match the emulator being used. It's tedious to copy, paste, and rename but it doesn't take too long. I've copied these files to from my Hyperspin machine to another PC that uses Launch Box, set up JoyToKey in Rocket Launcher via the tutorial link below, and found it working beautifully. MAME is a bit of a jerk, however. Sometimes it works straight away and sometimes you still have to map the game within the MAME TAB menu. I ONLY HAVE CONTROLLER 1 MAPPED IN THESE FILES! NOTE: There are NO games or programs within this archive. There are, however, 2 other files -- a BAT file for killing the JoyToKey process and a shortcut that gives that BAT file ADMIN privileges. As I use Hyperspin for my main machine, I am not yet sure if there is a way to have Launch Box use the JoyToKey.exe as the startup program and JoyToKeyKill.lnk as a shutdown program. Once I find out a way to get them to function, I will update this post. In the meantime, there shouldn't be too much trouble with it. You can always exit JoyToKey manually if it causes you any issues. All files were created manually by me so there's no copyright issue. Launch Box doesn't need a JoyToKey profile as, from my testing, it has its own ability to use a joystick/controller. **** Here is a very good tutorial on how to set up JoyToKey with Rocket Launcher - READ IT CAREFULLY!: http://bit.ly/2oA2CJ4 Here's a tutorial on how to use Rocket Launcher with LaunchBox: ----------------------------------- ONLY FOR THOSE USING A MOGA PRO CONTROLLER----------------------------------- In case you have a Moga Controller, download and install the Moga Serial program: https://github.com/Zel-os/MogaSerial NOTE: I can only get it to work in Mode A on the PRO Controller but it works great! Your computer will also need BlueTooth enabled and successfully linked to the MOGA. Here is where you can get the latest vJoy USB Controller Driver (you'll need this for the MOGA Controller): http://vjoystick.sourceforge.net/site/ Submitter malarrya Submitted 05/02/2017 Category Third-party Apps and Plugins  
  20. Version 1.1.0

    227 downloads

    What's New for Version 1.1.0: ADDED 7 New Systems (80 TOTAL) + LB/HS/RL/Default profiles. New systems include Sega Model 1, Sega System 16, Sega System 24, , Sega X Board, Sega Y Board, Pop-Cap, and Microsoft MS-DOS. Changed the ESC key functionality to buttons 7 + 8 (COIN+START). You must now press both to exit the game. Placed the ESC key location on Button 25 (a dummy location good for using combo buttons). Changed Button 5 to TAB. Changed Button 6 to P (PAUSE). Changed Button 9 to C. Changed Button 10 to V. Changed Button 11 to Z. Changed Button 12 to X. I'll see how this configuration works for me for the time being. If it's a pain or something is not quite right, I'll continue tweaking it until I find what's best. *********** BACK UP YOUR OLD PROFILES IN CASE YOU DON'T LIKE THE CHANGES *********** If you use Rocket Launcher as the primary emulator for Launch Box then this is for you. I created about 75 profiles for various systems, added them to a RAR archive, and attached to this post. All you have to do is unrar and place the folders within the archive into your ..\RocketLauncher\Profiles\JoyToKey directory. For example, mine is -- ..\RocketLauncher\Profiles\JoyToKey. You may need to edit the profiles so they are more to your liking or work correctly with your setup. I use the default MAME setup for everything. If you want to change one or all of them, all you have to do is edit only one CFG file, copy the CFG file to every other folder, and rename the CFG file and FOLDER to the name of the emulator you're using for the system. For example -- I use Rocket Launcher as the emulator for ALL my systems but, once RL starts, I use Stella for the Atari 2600. My path is then ..\RocketLauncher\Profiles\JoyToKey\Atari 2600\Stella\Stella.cfg Maybe you don't use Stella for the Atari 2600 but use RetroArch. Here's how to change it: You would simply rename ..\RocketLauncher\Profiles\JoyToKey\Atari 2600\Stella\Stella.cfg to ..\RocketLauncher\Profiles\JoyToKey\Atari 2600\RetroArch\RetroArch.cfg.It's the same path\folder\file but the innermost folder and cfg file have simply been renamed to match the emulator being used. It's tedious to copy, paste, and rename but it doesn't take too long. I've copied these files to from my Hyperspin machine to another PC that uses Launch Box, set up JoyToKey in Rocket Launcher via the tutorial link below, and found it working beautifully. MAME is a bit of a jerk, however. Sometimes it works straight away and sometimes you still have to map the game within the MAME TAB menu. I ONLY HAVE CONTROLLER 1 MAPPED IN THESE FILES! NOTE: There are NO games or programs within this archive. There are, however, 2 other files -- a BAT file for killing the JoyToKey process and a shortcut that gives that BAT file ADMIN privileges. As I use Hyperspin for my main machine, I am not yet sure if there is a way to have Launch Box use the JoyToKey.exe as the startup program and JoyToKeyKill.lnk as a shutdown program. Once I find out a way to get them to function, I will update this post. In the meantime, there shouldn't be too much trouble with it. You can always exit JoyToKey manually if it causes you any issues. All files were created manually by me so there's no copyright issue. Launch Box doesn't need a JoyToKey profile as, from my testing, it has its own ability to use a joystick/controller. **** Here is a very good tutorial on how to set up JoyToKey with Rocket Launcher - READ IT CAREFULLY!: http://bit.ly/2oA2CJ4 Here's a tutorial on how to use Rocket Launcher with LaunchBox: ----------------------------------- ONLY FOR THOSE USING A MOGA PRO CONTROLLER----------------------------------- In case you have a Moga Controller, download and install the Moga Serial program: https://github.com/Zel-os/MogaSerial NOTE: I can only get it to work in Mode A on the PRO Controller but it works great! Your computer will also need BlueTooth enabled and successfully linked to the MOGA. Here is where you can get the latest vJoy USB Controller Driver (you'll need this for the MOGA Controller): http://vjoystick.sourceforge.net/site/
  21. Noredor

    Trial

    Hi there! Came across your wonderful product and a friend of mine bought a license back in the day, although he has no longer access to his registered email and has not gotten a reply from these fine folk yet about how to proceed I thought I would ask for myself how to test the full BigBox version. I recentely discovered the joy of a SteamLink and emulation, oh such joy! Now most of the features I am looking for are locked behind the bigbox paid app so I cannot test them. Is there any way to test these features? Perhaps a 7 day trial or in an extreme case a refund if it doesn't work as expected? I am looking to buy your product I just want to make sure it works as I expect it to, SteamLink and all. How would one proceed? Thanx!
  22. I'm looking to purchase a pandora's box with the 2 arcade joystick panel. Is it as simple as me connecting the pandora's box to my pc via usb and configuring the buttons from there? Has anyone tried this before?
  23. Hi guys so for about a year now im into emulation, slowly building my collection of games and systems. So yesterday i thought it was time to step it up a little bit. for the past i've been using a ps4 controller to control my games. I had a idea to buy system specific controllers. so yesterday i bought a usb nes controller and a snes controller. So while is was setting up i notiched that for one system it worked but once i changed the controller and system it all got messed up again. so thats where i find out asbout custom configs. But now a other problem pops up. i've got all the buttons that are needed mapped properly and saved to the right config but somehow once i go ingame all the buttons mess up again. for example i just have my nes controller mapped as button b to button b button a to button a ect. but ingame button a is fast forward and my start key is exiting the game . I only changed the buttons that where needed everything else is still default. What did i do wrong
  24. Ok so currently I have 2 zero second encoder (Bought here), as well as a bliss-box 4-play (purchased here), which is an all in 1 usb controller adapter. It allows you to use any systems controller on the pc. Anyway back to my trouble. My problem is primarily based on the Zero second encoders, as sometimes when I load them they come up as controller 1 and 2, but sometimes they come up as controller 3 and 4. How do I set these up, so that they don't change. I would like to set them up so that they always get 1 and 2 and the bliss-box grabs 3,4,5,6. I was trying to play mame yesterday and earned of this issue, I then reloaded everything and then I got 1 and 2 again.
  25. Obligatory I'm brand new to LaunchBox / Big Box. Just bought my license a couple weeks ago to go along with the Rec Room Masters arcade cabinet I got along with the Xtension Control Board "Emulator Edition Plus" joystick controller. The controller comes preconfigured mapped to work great with MAME "out of the box", however I'm having a lot of trouble figuring out how to do mapping for other systems. I attempted to configure the controls in individual Emulators I'm launching (like Kega Fusion) however after exiting out and letting LaunchBox run a game with it, it's as if it forgets all controls I just mapped. I've attempted using launchers like RetroArch (which seems more geared toward gaming pads like RetroPad) and Rocket Launcher (which is a bit confusing, though even if I used something like AutoHotKey, I'm not sure what keys the Emulators use to map to). I would appreciate any help / guidance I could get on the topic, especially anything in regards to this specific controller. It'd be nice to keep it simple and not have to use external launchers, but at this point I really just want to get up and running...
×
×
  • Create New...