Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'launcher'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • LaunchBox
    • Android
    • Beta Testing
    • Collections and Builds
    • Features
    • Linux
    • News and Updates
    • Noobs
    • Troubleshooting
    • Website/Forum Support
  • User-Created Content and Downloads
    • Big Box Custom Themes
    • Big Box Sound Packs
    • Big Box Startup Videos
    • Custom Theme Tutorials
    • Game Media
    • LaunchBox for Android Custom Themes
    • LaunchBox for Windows 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
    • Startup Themes
    • Pause Themes
    • Sound Packs
    • Startup Videos
  • LaunchBox for Windows
    • Custom Themes
    • Custom Badges
  • LaunchBox for Android
    • Custom Themes
  • Third-party Apps and Plugins
  • Game Media
    • 3DO Interactive Multiplayer
    • Aamber Pegasus
    • Acorn Achimedes
    • Acorn Atom
    • Acorn Electron
    • ALF TV Game
    • Amstrad CPC
    • Amstrad GX4000
    • Android
    • APF Imagination Machine
    • Apogee BK-01
    • Apple II
    • Apple IIGS
    • Apple Mac OS
    • Arcade
    • Atari 800
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Jaguar
    • Atari Jaguar CD
    • Atari Lynx
    • Atari ST
    • Atari XEGS
    • Bally Astrocade
    • Bandai Super Vision 8000
    • BBC Microcomputer System
    • Camputers Lynx
    • Casio Loopy
    • Casio PV-1000
    • Coleco ADAM
    • ColecoVision
    • Commodore 64
    • Commodore 128
    • Commodore Amiga
    • Commodore Amiga CD32
    • Commodore CDTV
    • Commodore MAX Machine
    • Commodore PET
    • Commodore Plus 4
    • Commodore VIC-20
    • Dragon 32/64
    • EACA EG2000 Colour Genie
    • Elektronika BK
    • Emerson Arcadia 2001
    • Enterprise
    • Entex Adventure Vision
    • Epoch Game Pocket Computer
    • Epoch Super Cassette Vision
    • Exelvision EXL 100
    • Exidy Sorcerer
    • Fairchild Channel F
    • Fujitsu FM Towns Marty
    • Fujitsu FM-7
    • Funtech Super Acan
    • Game Wave Family Entertainment System
    • GamePark GP32
    • GameWave
    • GCE Vectrex
    • Hartung Game Master
    • Hector HRX
    • Interton VC 4000
    • Jupiter Ace
    • Lviv PC-01
    • Magnavox Odyssey
    • Magnavox Odyssey 2
    • Matra and Hachette Alice
    • Mattel Aquarius
    • Mattel HyperScan
    • Mattel Intellivision
    • Mega Duck
    • Memotech MTX512
    • Microsoft MSX
    • Microsoft MSX2
    • Microsoft MSX2+
    • Microsoft Xbox
    • Microsoft Xbox 360
    • MS-DOS
    • MUGEN
    • Namco System 22
    • NEC PC-8801
    • NEC PC-9801
    • NEC PC-FX
    • NEC TurboGrafx-16
    • NEC TurboGrafx-CD
    • Nintendo 3DS
    • Nintendo 64
    • Nintendo 64DD
    • Nintendo DS
    • Nintendo Entertainment System
    • Nintendo Famicom Disk System
    • Nintendo Game & Watch
    • Nintendo Game Boy
    • Nintendo Game Boy Advance
    • Nintendo Game Boy Color
    • Nintendo GameCube
    • Nintendo Pokemon Mini
    • Nintendo Satellaview
    • Nintendo Switch
    • Nintendo Virtual Boy
    • Nintendo Wii
    • Nintendo Wii U
    • Nokia N-Gage
    • Nuon
    • OpenBOR
    • Oric Atmos
    • Orion-128
    • Othello Multivision
    • PC Engine SuperGrafx
    • Philips CD-i
    • Philips VG 5000
    • Philips Videopac+
    • Pinball
    • Radio-86RK Mikrosha
    • RCA Studio II
    • SAM Coupé
    • Sammy Atomiswave
    • ScummVM
    • Sega 32X
    • Sega CD
    • Sega CD 32X
    • Sega Dreamcast
    • Sega Dreamcast VMU
    • Sega Game Gear
    • Sega Genesis
    • Sega Hikaru
    • Sega Master System
    • Sega Model 1
    • Sega Model 2
    • Sega Model 3
    • Sega Naomi
    • Sega Naomi 2
    • Sega Pico
    • Sega Saturn
    • Sega SC-3000
    • Sega SG-1000
    • Sega ST-V
    • Sega System 16
    • Sega System 32
    • Sega Triforce
    • Sharp MZ-2500
    • Sharp X1
    • Sharp X68000
    • Sinclair ZX Spectrum
    • Sinclair ZX-81
    • SNK Neo Geo AES
    • SNK Neo Geo CD
    • SNK Neo Geo MVS
    • SNK Neo Geo Pocket
    • SNK Neo Geo Pocket Color
    • Sony Playstation
    • Sony Playstation 2
    • Sony Playstation 3
    • Sony PocketStation
    • Sony PSP
    • Sony PSP Minis
    • Sord M5
    • Spectravideo
    • Super Nintendo Entertainment System
    • Taito Type X
    • Tandy TRS-80
    • Tapwave Zodiac
    • Texas Instruments TI 99/4A
    • Thomson MO/TO
    • Tiger Electronics Handheld
    • Tiger Game.com
    • Tomy Tutor
    • Touhou Project
    • TRS-80 Color Computer
    • Vector-06C
    • VTech CreatiVision
    • VTech Socrates
    • Watara Supervision
    • Web Browser
    • Windows
    • Windows 3.X
    • WonderSwan
    • WonderSwan Color
    • WoW Action Max
    • XaviXPORT
    • ZiNc
  • Platform Media
    • Platform Theme Videos
    • Platform Console Images
    • Platform Backgrounds
    • Platform Banners
    • Platform Clear Logos
    • Platform Bezels/Overlays
    • Platform Media Packs
    • Platform Default Image Packs
    • Platform Templates
  • Playlists & Playlist Media
    • Playlists
    • Playlist Theme Videos
    • Playlist Backgrounds
    • Playlist Banners
    • Playlist Clear Logos
    • Playlist Media Packs
  • LaunchBox/Big Box Media

Blogs

  • Jason's Devotions
  • Thatmans Blog
  • THAT NINTENDO SWITCH EARLY REVEAL WAS FROM A STOLEN CONSOLE
  • Version 8.8
  • Game Theme Videos
  • Exclusive Bezels
  • Save Up Your Time by Outsourcing Creative Graphic Design
  • cocktail mass settings mame 4 launchbox?
  • Bigg Homi
  • aj gaming2357
  • Adding the old 2004 version of sadx
  • gg
  • Ninjaman Blog

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 17 results

  1. SteamLauncher View File SteamLauncher A LaunchBox plugin designed to allow roms/emulators to easily be launched with Steam, directly from the LaunchBox/BigBox interface, without any complicated setup or technical know-how. Simply enable SteamLauncher and all LaunchBox/BigBox game/rom launches will be intercepted and launched via Steam. This will provide access to the Steam overlay, custom controller configurations, and will display the game/rom your are currently playing to any of your Steam friends. Features Here are a few of the features provided by SteamLauncher: Allow LaunchBox to do what its good at - be the sole organizer and maintainer of your rom/game collection, without having to duplicate its functionality in Steam (something it was not designed for). Keep the 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/per-emulator/per-game 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 the game/rom currently being played with Steam friends (ex: JohnDoe is currently playing 'Super Metroid (SNES)'). Requirements .NET Core 3.1 Steam for Windows LaunchBox/BigBox Getting Started Installation Download the latest plugin release from the LaunchBox forum plugin download page. This GitHub repository is meant as more of a resource for developers. While test builds and other pre-release packages may occassionally be posted on GitHub, the latest public release builds will always be posted on the LaunchBox forum plugin download page first: LaunchBox Plugin Download: https://forums.launchbox-app.com/files/file/972-steamlauncher/ Extract the 'SteamLauncher' directory from the compressed package into your LaunchBox plugins directory. 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 being inside the directory 'C:\LaunchBox\Plugins\SteamLauncher'. How to Use Note: Obviously, Steam must be running to launch games via Steam so one can either manually start Steam before opening LaunchBox/BigBox or SteamLauncher will automatically launch Steam when needed. To launch a game/rom/emulator in LaunchBox/BigBox via Steam: Ensure SteamLauncher is enabled by using 1 of the 2 following methods: Selecting the 'Tools' menu item and clicking 'Use SteamLauncher'. When SteamLauncher is enabled the menu item will be labeled '(ON)'. This menu item can also be found in BigBox. Selecting the 'Tools' menu item and clicking 'SteamLauncher Settings', resulting in the SteamLauncher settings dialog being displayed. By then checking the checkbox labeled 'Enable SteamLauncher' and clicking the 'Save' button, SteamLauncher will be enabled. The SteamLauncher settings dialog cannot be accessed in BigBox. Once SteamLauncher is enabled, all games/roms/emulators will be intercepted by SteamLauncher and launched through Steam. Customize Platform Names When games/roms are launched with SteamLauncher enabled, the title and platform of the game/rom will be displayed in one's Steam status in the format of: 'Game Title (Platform Name)'. Example: Super Mario Bros. (Nintendo Entertainment System) Friends on Steam will see this title in one's status whenever a particular game/rom is being played. If desired, the platform name displayed can be customized. For example, the platform 'Nintendo Entertainment System' can be changed to 'NES'. This customization can be performed by navigating to the 'Platform Names' tab in the SteamLauncher settings dialog. Note: To entirely omit a platform name from one's Steam status, leave the 'Custom Platform Name' entry blank (as seen in the 'Windows' entry in the screenshot below). Selective Use The 'Selective Use' feature allows one to precisely customize the circumstances under which SteamLauncher will be enabled/disabled. The settings for this feature can be found in the 'Selective Use' tab in the SteamLauncher settings dialog. Filter Mode 'Filter Mode' defines how the entries in the 'Filter List' will be applied. Blacklist: SteamLauncher will always be enabled except when a matching filter is found. Whitelist: SteamLauncher will always be disabled except when a matching filter is found. Off: Disable the 'Selective Use' feature entirely. Filters List The 'Filters List' is a list of user defined filters that control when SteamLauncher will be enabled/disabled. Enable: This checkbox must be checked for a particular filter list entry to be enabled. If not checked, it will be completely ignored. Description: Used purely as a means of helping the user describe what the filter list entry does. It is entirely optional and has no impact on the actual functionality of the entry. Filter String: This is the string which is matched against the target 'Filter Type', dictating whether or not this entry matches a particular game title, platform name, etc. The filter string is not case sensitive and it supports 2 types of wildcards: '*' Wilcard: matches one or more of any character. '?' Wildcard: matches any single character. Filter Type: Dicates what field the 'Filter String' is compared against. The 'Filter Type' options are: Game Title: Title of the game or rom (ex: Celeste, Super Mario World, Donkey Kong Country, etc). Platform Name: Name of the platform (ex: Windows, Nintendo 64, Sony Playstation, etc). Emulator Title: Title of the emulator (ex: Retroarch, Dolphin, Cemu, etc). Exe Path: The path of the game or emulator EXE file (ex: 'C:\PC_Games\GOG\*', 'D:\*', '*\DOSBox\*', etc). Additional Application Name: Name of an 'Additional App' (a LaunchBox feature which allows you to specify additional commands to run for a game). Status: A field in LaunchBox's metadata for games (right click game, 'Edit' -> 'Edit Metadata') which specifies what platform/launcher/store a game was imported from (ex: '*Xbox*', '*Microsoft Store*', '*GOG*', etc). Ignore Custom Fields: Enabling this feature causes SteamLauncher to ignore all 'SLEnabled' custom field entries. What are 'SLEnabled' custom field entries? Right click on a game in LaunchBox, click 'Edit' -> 'Edit Metadata', and then select the 'Custom Fields' menu item. By adding a new entry named 'SLEnabled' and setting its value to '1' or '0', SteamLauncher can be made to always be enabled for this game (1) or always be disabled for this game (0). This custom field value will always take precedent over all other filtering features (filter strings, filter modes, etc). The only exception to this is when 'Ignore Custom Fields' is enabled (which will cause all 'SLEnabled' custom field entries to be ignored). VTables 'Automatic Online Updates' 'Automatic Online Updates' of vtables definitions can be enabled/disabled in the 'Miscellaneous' tab of the SteamLauncher settings dialog. For SteamLauncher to properly work it has to access internal Steam features that are not meant to be accessed by developers outside of Valve. To access these undocumented, unexported functions, SteamLauncher uses a set of definitions which define what these functions are, their function signatures (their parameters, return values, and how to call them), and where to find them within the Steam client DLL. These definitions can change whenever Valve releases a new Steam update and if they change significantly, they can cause SteamLauncher to stop working correctly. In order for SteamLauncher to continue working properly, without the author manually patching the plugin and releasing a new SteamLauncher update every time this happens, an online database was created that can be updated when one of these changes happens, allowing SteamLauncher to continue functioning normally. If 'Automatic Online Updates' is enabled, SteamLauncher will automatically check for new updates every time LaunchBox/BigBox is launched. If new definitions are available, it will silently update and continue working normally. If automatic updates are not enabled, one can manually check for new updates by clicking the 'Force Update' button. Support If you have ANY problems with the plugin, I want to know about them. If you need help with any technical issue (see 'Logs'), want to suggest a new feature (I'm very open to any ideas), just want to chat, or anything else related to the plugin, visit the support thread at the link below. I am also available to chat on Steam for any urgent issues or if more direct help is needed. Plugin Support Thread: https://forums.launchbox-app.com/topic/43142-steamlauncher/ 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 'Log Level' is set to 'Verbose'. To enable and collect 'Verbose' debug logs, do the following: Open the SteamLauncher settings dialog. Click the dropdown box under 'Log Level' and select 'Verbose'. Click the 'Save' button. Restart LaunchBox/BigBox. Now simply repeat whatever behavior was causing the issue and/or bug, and after you're sure you've replicated the behavior, close LaunchBox/BigBox. Look inside of the SteamLauncher directory for a file named 'debug.log' (there may be more than one sequentially named log file if there was an enormous amount of output but this is unlikely if verbose logging was turned on just briefly). Open this 'debug.log' file in a text editor, copy its entire contents, and paste/upload it to pastebin.com. In the SteamLauncher support thread, provide the PasteBin URL, the details of the problem you encountered, and the particulars of your setup (Windows version, 32-bit or 64-bit, LaunchBox version, Steam version, SteamLauncher plugin version, etc). The more information the better. Contact Information Alias: Lahma Email: lahma0@gmail.com Steam Alias: lahma0 Friend me on Steam: You can click on my alias above or you can copy/paste the following URL into your address bar: steam://friends/add/76561198237461630 GitHub Project URL: https://github.com/lahma0/SteamLauncher LaunchBox Community Forums Profile: https://forums.launchbox-app.com/profile/89710-lahma/ Plugin Support Thread: https://forums.launchbox-app.com/topic/43142-steamlauncher/ Credits ChippiHeppu: Logo m4dengi: steamclient_tracker (unfortunately, no longer updated) cammelspit: Help with developing the idea and direction for the project Nielk1: Initial inspiration for the project and just a talented programmer to bounce ideas off of Helpful members of the LaunchBox community: The_Keeper86, JedExodus, FromLostDays, HTPCei, Corgana, Benuno, Neil9000 (sorry for anyone I'm forgetting) Known Issues MAME Compatibility Fix It has been observed that MAME crashes when launched through a non-Steam shortcut. This problem is not directly related to SteamLauncher, but since SteamLauncher relies on non-Steam shortcuts, launching MAME via SteamLauncher was no longer working. After a lot of investigation and tinkering by some dedicated users on the LaunchBox forums (cammelspit and JedExodus), a fix was eventually found for the issue. Whether launching MAME directly via a non-Steam shortcut or via SteamLauncher using LaunchBox/BigBox, the fix is simply to modify the launch parameters to include the following: -joystickprovider xinput -keyboardprovider win32 If one of these parameters already exists when modifying MAME within LaunchBox, you will obviously need to replace it (don't just add a 2nd instance of '-joystickprovider' or '-keyboardprovider'). You can safely ignore any popups/warnings that LaunchBox displays about pause screen compatibility. Legal Stuff ©2022 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, Kodi 19 and Kodi Windows Store versions. Requirements: Windows PC LaunchBox Premium Kodi 16, 17, 18, 19 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. Taskbar will flash on Kodi Windows Store version (UWA) using 1.5.4+. Current workaround is to switch to Kodi non-UWA or to minimize effects, enable hide taskbar in advance options, remove Cortana search bar and change taskbar to black. Starting with version 1.5.6, due to windows security restriction on SMB shares over IP (eg. \\192.168.1.1\shared-folder\), the addon will produce an error saying it is not supported. Current workaround is to enable SMB fix in Advance settings to replace IP with supplied server name or enable SMBv1 on server and computer to allow NetBIOS name resolutions in Kodi. Kodi-six package is now required with 1.5.6+, addon will fail if after first installation of Kodi-six package dependency, Kodi was not restarted. 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 1.5.9

    15,020 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, Kodi 19 and Kodi Windows Store versions. Requirements: Windows PC LaunchBox Premium Kodi 16, 17, 18, 19 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. Taskbar will flash on Kodi Windows Store version (UWA) using 1.5.4+. Current workaround is to switch to Kodi non-UWA or to minimize effects, enable hide taskbar in advance options, remove Cortana search bar and change taskbar to black. Starting with version 1.5.6, due to windows security restriction on SMB shares over IP (eg. \\192.168.1.1\shared-folder\), the addon will produce an error saying it is not supported. Current workaround is to enable SMB fix in Advance settings to replace IP with supplied server name or enable SMBv1 on server and computer to allow NetBIOS name resolutions in Kodi. Kodi-six package is now required with 1.5.6+, addon will fail if after first installation of Kodi-six package dependency, Kodi was not restarted. 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.
  4. Version 4.0.0-plugin

    9,219 downloads

    Version 4.0.0 Now works with the ThirdParty folder. Also added a way to convert the BatRunner roms to launch straight from Launchbox instead of running through the batrunner and bat files. This feature is new. 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!
  5. Version 1.0.0

    630 downloads

    Best theme for gaming on big box
  6. EpicFail ScummVM Launcher NEW View File Version 4.0.0 Now works with the ThirdParty folder. Also added a way to convert the BatRunner roms to launch straight from Launchbox instead of running through the batrunner and bat files. This feature is new. 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
  7. Version NETCore 0.9.8.3

    2,081 downloads

    SteamLauncher A LaunchBox plugin designed to allow roms/emulators to easily be launched with Steam, directly from the LaunchBox/BigBox interface, without any complicated setup or technical know-how. Simply enable SteamLauncher and all LaunchBox/BigBox game/rom launches will be intercepted and launched via Steam. This will provide access to the Steam overlay, custom controller configurations, and will display the game/rom your are currently playing to any of your Steam friends. Features Here are a few of the features provided by SteamLauncher: Allow LaunchBox to do what its good at - be the sole organizer and maintainer of your rom/game collection, without having to duplicate its functionality in Steam (something it was not designed for). Keep the 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/per-emulator/per-game 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 the game/rom currently being played with Steam friends (ex: JohnDoe is currently playing 'Super Metroid (SNES)'). Requirements .NET Core 3.1 Steam for Windows LaunchBox/BigBox Getting Started Installation Download the latest plugin release from the LaunchBox forum plugin download page. This GitHub repository is meant as more of a resource for developers. While test builds and other pre-release packages may occassionally be posted on GitHub, the latest public release builds will always be posted on the LaunchBox forum plugin download page first: LaunchBox Plugin Download: https://forums.launchbox-app.com/files/file/972-steamlauncher/ Extract the 'SteamLauncher' directory from the compressed package into your LaunchBox plugins directory. 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 being inside the directory 'C:\LaunchBox\Plugins\SteamLauncher'. How to Use Note: Obviously, Steam must be running to launch games via Steam so one can either manually start Steam before opening LaunchBox/BigBox or SteamLauncher will automatically launch Steam when needed. To launch a game/rom/emulator in LaunchBox/BigBox via Steam: Ensure SteamLauncher is enabled by using 1 of the 2 following methods: Selecting the 'Tools' menu item and clicking 'Use SteamLauncher'. When SteamLauncher is enabled the menu item will be labeled '(ON)'. This menu item can also be found in BigBox. Selecting the 'Tools' menu item and clicking 'SteamLauncher Settings', resulting in the SteamLauncher settings dialog being displayed. By then checking the checkbox labeled 'Enable SteamLauncher' and clicking the 'Save' button, SteamLauncher will be enabled. The SteamLauncher settings dialog cannot be accessed in BigBox. Once SteamLauncher is enabled, all games/roms/emulators will be intercepted by SteamLauncher and launched through Steam. Customize Platform Names When games/roms are launched with SteamLauncher enabled, the title and platform of the game/rom will be displayed in one's Steam status in the format of: 'Game Title (Platform Name)'. Example: Super Mario Bros. (Nintendo Entertainment System) Friends on Steam will see this title in one's status whenever a particular game/rom is being played. If desired, the platform name displayed can be customized. For example, the platform 'Nintendo Entertainment System' can be changed to 'NES'. This customization can be performed by navigating to the 'Platform Names' tab in the SteamLauncher settings dialog. Note: To entirely omit a platform name from one's Steam status, leave the 'Custom Platform Name' entry blank (as seen in the 'Windows' entry in the screenshot below). Selective Use The 'Selective Use' feature allows one to precisely customize the circumstances under which SteamLauncher will be enabled/disabled. The settings for this feature can be found in the 'Selective Use' tab in the SteamLauncher settings dialog. Filter Mode 'Filter Mode' defines how the entries in the 'Filter List' will be applied. Blacklist: SteamLauncher will always be enabled except when a matching filter is found. Whitelist: SteamLauncher will always be disabled except when a matching filter is found. Off: Disable the 'Selective Use' feature entirely. Filters List The 'Filters List' is a list of user defined filters that control when SteamLauncher will be enabled/disabled. Enable: This checkbox must be checked for a particular filter list entry to be enabled. If not checked, it will be completely ignored. Description: Used purely as a means of helping the user describe what the filter list entry does. It is entirely optional and has no impact on the actual functionality of the entry. Filter String: This is the string which is matched against the target 'Filter Type', dictating whether or not this entry matches a particular game title, platform name, etc. The filter string is not case sensitive and it supports 2 types of wildcards: '*' Wilcard: matches one or more of any character. '?' Wildcard: matches any single character. Filter Type: Dicates what field the 'Filter String' is compared against. The 'Filter Type' options are: Game Title: Title of the game or rom (ex: Celeste, Super Mario World, Donkey Kong Country, etc). Platform Name: Name of the platform (ex: Windows, Nintendo 64, Sony Playstation, etc). Emulator Title: Title of the emulator (ex: Retroarch, Dolphin, Cemu, etc). Exe Path: The path of the game or emulator EXE file (ex: 'C:\PC_Games\GOG\*', 'D:\*', '*\DOSBox\*', etc). Additional Application Name: Name of an 'Additional App' (a LaunchBox feature which allows you to specify additional commands to run for a game). Status: A field in LaunchBox's metadata for games (right click game, 'Edit' -> 'Edit Metadata') which specifies what platform/launcher/store a game was imported from (ex: '*Xbox*', '*Microsoft Store*', '*GOG*', etc). Ignore Custom Fields: Enabling this feature causes SteamLauncher to ignore all 'SLEnabled' custom field entries. What are 'SLEnabled' custom field entries? Right click on a game in LaunchBox, click 'Edit' -> 'Edit Metadata', and then select the 'Custom Fields' menu item. By adding a new entry named 'SLEnabled' and setting its value to '1' or '0', SteamLauncher can be made to always be enabled for this game (1) or always be disabled for this game (0). This custom field value will always take precedent over all other filtering features (filter strings, filter modes, etc). The only exception to this is when 'Ignore Custom Fields' is enabled (which will cause all 'SLEnabled' custom field entries to be ignored). VTables 'Automatic Online Updates' 'Automatic Online Updates' of vtables definitions can be enabled/disabled in the 'Miscellaneous' tab of the SteamLauncher settings dialog. For SteamLauncher to properly work it has to access internal Steam features that are not meant to be accessed by developers outside of Valve. To access these undocumented, unexported functions, SteamLauncher uses a set of definitions which define what these functions are, their function signatures (their parameters, return values, and how to call them), and where to find them within the Steam client DLL. These definitions can change whenever Valve releases a new Steam update and if they change significantly, they can cause SteamLauncher to stop working correctly. In order for SteamLauncher to continue working properly, without the author manually patching the plugin and releasing a new SteamLauncher update every time this happens, an online database was created that can be updated when one of these changes happens, allowing SteamLauncher to continue functioning normally. If 'Automatic Online Updates' is enabled, SteamLauncher will automatically check for new updates every time LaunchBox/BigBox is launched. If new definitions are available, it will silently update and continue working normally. If automatic updates are not enabled, one can manually check for new updates by clicking the 'Force Update' button. Support If you have ANY problems with the plugin, I want to know about them. If you need help with any technical issue (see 'Logs'), want to suggest a new feature (I'm very open to any ideas), just want to chat, or anything else related to the plugin, visit the support thread at the link below. I am also available to chat on Steam for any urgent issues or if more direct help is needed. Plugin Support Thread: https://forums.launchbox-app.com/topic/43142-steamlauncher/ 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 'Log Level' is set to 'Verbose'. To enable and collect 'Verbose' debug logs, do the following: Open the SteamLauncher settings dialog. Click the dropdown box under 'Log Level' and select 'Verbose'. Click the 'Save' button. Restart LaunchBox/BigBox. Now simply repeat whatever behavior was causing the issue and/or bug, and after you're sure you've replicated the behavior, close LaunchBox/BigBox. Look inside of the SteamLauncher directory for a file named 'debug.log' (there may be more than one sequentially named log file if there was an enormous amount of output but this is unlikely if verbose logging was turned on just briefly). Open this 'debug.log' file in a text editor, copy its entire contents, and paste/upload it to pastebin.com. In the SteamLauncher support thread, provide the PasteBin URL, the details of the problem you encountered, and the particulars of your setup (Windows version, 32-bit or 64-bit, LaunchBox version, Steam version, SteamLauncher plugin version, etc). The more information the better. Contact Information Alias: Lahma Email: lahma0@gmail.com Steam Alias: lahma0 Friend me on Steam: You can click on my alias above or you can copy/paste the following URL into your address bar: steam://friends/add/76561198237461630 GitHub Project URL: https://github.com/lahma0/SteamLauncher LaunchBox Community Forums Profile: https://forums.launchbox-app.com/profile/89710-lahma/ Plugin Support Thread: https://forums.launchbox-app.com/topic/43142-steamlauncher/ Credits ChippiHeppu: Logo m4dengi: steamclient_tracker (unfortunately, no longer updated) cammelspit: Help with developing the idea and direction for the project Nielk1: Initial inspiration for the project and just a talented programmer to bounce ideas off of Helpful members of the LaunchBox community: The_Keeper86, JedExodus, FromLostDays, HTPCei, Corgana, Benuno, Neil9000 (sorry for anyone I'm forgetting) Known Issues MAME Compatibility Fix It has been observed that MAME crashes when launched through a non-Steam shortcut. This problem is not directly related to SteamLauncher, but since SteamLauncher relies on non-Steam shortcuts, launching MAME via SteamLauncher was no longer working. After a lot of investigation and tinkering by some dedicated users on the LaunchBox forums (cammelspit and JedExodus), a fix was eventually found for the issue. Whether launching MAME directly via a non-Steam shortcut or via SteamLauncher using LaunchBox/BigBox, the fix is simply to modify the launch parameters to include the following: -joystickprovider xinput -keyboardprovider win32 If one of these parameters already exists when modifying MAME within LaunchBox, you will obviously need to replace it (don't just add a 2nd instance of '-joystickprovider' or '-keyboardprovider'). You can safely ignore any popups/warnings that LaunchBox displays about pause screen compatibility. Legal Stuff ©2022 Valve Corporation. Steam and the Steam logo are trademarks and/or registered trademarks of Valve Corporation in the U.S. and/or other countries.
  8. Ps5 Theme for Big box View File Best theme for gaming on big box Submitter ANASS RAKID Submitted 12/20/2021 Category Big Box Custom Themes  
  9. I have a launcher for BigBox. One of the important things it does is wait for BigBox to close before executing some cleanup scripts. I seem to no longer be able to wait for the BigBox process to finish. If I call BigBox like this from the command prompt: "start /wait C:\Games\Emulators\LaunchBox\BigBox.exe" one would expect it should wait for BigBox to close before continuing, but this no longer works as it did in prior versions. I can only assume it is because it is launching BigBox as another process and closing the initial one that launched it. Can anyone point me in the right direction? Is there a command I can pass to force it to not close the initial process? Any help would be appreciated so I can properly fix my launcher plugin.
  10. Version 1.3.0

    52 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
  11. 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
  12. 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. 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 Submitter loueradun Submitted 10/12/2018 Category Third-party Apps and Plugins  
  13. 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  
  14. Version 1.0.0

    14 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.
  15. 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!
  16. 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
  17. 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
×
×
  • Create New...