Jump to content
LaunchBox Community Forums

Search the Community

Showing results for tags 'launch'.

  • 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

  • Articles

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

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. Version NETCore 0.9.8.3

    1,833 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.
  3. I've had this issue for a little while now. Whenever I launch a game installed on Origin from LB an Origin box pops up asking to active unknown product. If I launch through Origin or a desktop shortcut it's fine. I've tried to use the shortcut as the application path in LB but that doesn't work either. This is multiple games but not all, for some reason Titanfall 2 works. No idea why's it's different.
  4. I added some new roms and when I tried to launch them from launch box using retroarch it does nothing. No error, no anything. I tried it from big box and it went from "now loading" back to the game page. But if I load it directly through retroarch it works fine. I checked the path to make sure It wasn't loading up a previous version, and it isn't. Not sure how to fix this.
  5. I am trying to create as close as i can to a seamless transition from startup into big box, but when i put the exe file into shell:startup like the LB video says it did nothing on start up. can someone help point me in the right direction?
  6. Anyone else having .net errors when attempting to launch Bigbox or LaunchBox? I get the .net error in the event viewer, followed by the application error. It worked yesterday, and last updates were installed on 11/12. Event Viewer logs have been attached. Launchbox version was 11.7. I did opt to install 11.8 at a later date. It is portable running off an external HD. No issues prior to today. My .net build is currently listed as 528372, which is 4.8 (source: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed#detect-net-framework-45-and-later-versions) Tried the following so far: Restarting Disabling .net in Windows Features. Followed by restart, checking for updates, reenabling .net, and another restart. Can't find too much documentation on reinstalling .net, and I don't want to try to reinstall Launchbox at this point. Any assistance would be greatly appreciated. Thank you in advance Edit: new troubleshooting step I did download updated LB files from the site and extracted them to a temp location on the c: drive. LB does launch successfully. Also was able to successfully apply my license. I overwrote the .exe, and .dat files on the external drive (did not copy the folders), but unable to run directly from the external, as I am greeted with the same .net errors. Instead I created a new subfolder on the external drive, and am now able to successfully launch LB / BB from the ext. drive. I restored from a previous backup in the older folder, and copied my Emulator / rom folder into the new, working folder. And everything is back in working order. Not sure what happened. But now I am moving over things like images, and the like to the new folder structure. Not sure what went wrong with the original folder structure, but will continue to move files from the old directory to the new one. I'll update my progress, as I complete. Maybe a corrupt file? Not sure, but at least I'm somewhat up... limping, but not down. Last edit. Ok. Well. I guess redownloading resolved it. Again, just redownloaded, restored from a previous backup, and moved folders (images, themes, emulators, roms, etc) from the old location to the new one, and everything is back up and running. Not sure what happened. Game on! launchBoxErrors.evtx
  7. Hi guys, Unsure if this is the right topic area.... New to launchbox and been emulating for some time now, but still very much a noob. I ran into an issue where i try to launch Battletoads under my Arcade, using Retroarch, yet when it opens retroarch, it sits there and the program stops responding. I am unsure what it is I am doing wrong what i need to do different to get it working. any helpful advice would be appreciated. Thnx ? (I provided pictures of what happens when launching, as well as the contents of my game zip)
  8. Hi everyone! Just as a brief context: I'm currently in a let's-learn-new-things type of project and the main goal is to build an Arcade + an App. Using the app, the player will choose a game and will get a QR-Code. The arcade will read this code and launch the game. Is there anyway to create some kind of integration with LaunchBox so that i can start a game systematically? thanks in advance! Best regards, Breno.
  9. This started with me wanting to launch the Sharp X68000 emu (xm6g) in fullscreen. Now, in the options menu there are no box to check and so on, so i needed to make a script and convert it to a new .exe with some commands baked into it. I know there are many ways to achieve this but i decided to go with the free to use tool called Autoit. After installation run SciTE script editor Create your script, mine looks like this: 1. run("C:\Emulators\sharpx68000\xm6g.exe") - path to the original *.EXE 2. Sleep (900) - Give some time for the emu to start 3. Send("{ALTDOWN}") - Press and hold ALT 4. Send("{ENTER}") - Press ENTER 5. Send("{ALTUP}") - Release ALT Save the script Now Run Compile script to exe... 1. Add your script 2. Choose destination for your new exe 3. You can add icons. i usually use 7-zip to open the original emulator.exe and extract the icon. I have only used 32x32 sized .ico files... Click "Convert" DONE! In Launchbox just replace the emulator.exe with your new one
  10. I have MESSUI64 set as my default emulator for Genesis roms and when using the MESS program on its own, without Launchbox, I can get my Genesis roms to run just the way I want, with correct full screen 4:3 ratio and really nice looking scanlines and saves states and preset volume control and everything I love about Mame that I can never get working properly on other Genesis emulators. So I was really dissapointed when I tried launcing some roms through LB. I can get them to run (using: genesis -cart -skip_gameinfo -nowindow as the command line prompt) but it will not use any of the settings I have stored in MESS and it gives me ugly stretched looking games that are in the wrong ratio, plus all the controller and keyboard settings are totally messed up. I have tried adding extra command line prompts (like -effect Scanlines75dx4_J4.png etc) but none of these seem to work or maybe I have the syntax wrong? I really want to work this out because because I'm hoping to run other systems like NES and SNES through MESS as well, because I prefer the usability and options in MESS a lot. Does anyone know how to do this? Thanks
  11. Hello, I know that Lanchbox has a feature for changing the emulator on the fly at launch. But is there anyway to change the core per launch? Some of my n64 and psx games run better with different cores, it would be awesome if i could change them on the fly as well.
  12. I originally setup my default emulator as retroarch. But i decided with the issues i have had with some of the emulations to just go with independent emulators for my systems...(ex: zsnesw). However when i play an SNES ROM, it defaults to retroarch. I have deselected retroarch in the "Manage Emulator" Menu, but it has not removed it. Once again to still defaults to retroarch. How do i permanently remove Retroarch from the "Launch With..." Menu. Thank you for your help in advance.
  13. I got a true noob question. What's the best way to update launch box/ Big Box to the newest version? I paid for the big box upgrade. Thank you.
  14. Hi all, I've been scouring the internet and watched Brad's tutorial on getting PS1 to work with Retroarch. I have everything I need as far as cue files, bin files, and bios files in the correct locations, but when I launch the game from LaunchBox or BigBox, nothing happens. However, if i scroll to "open RetroArch" and arrow over to History and hit the game i just tried from BigBox or LaunchBox, it fires up without any issues at all. Anyone that can shed some light on this? I think it might be in my history because i dragged the cue file into RetroArch to see if it would run and when it did I tried running it from BigBox with no success Thanks in advance for anyone who can help me. Additionally, I've been using the mednafen_psx_hw_libretro.dll and mednafen_psx_libretro.dll successfully in RetroArch, just not in Launch or Big Box. Thanks again! LG
  15. MovieLauncher v1.00 Hello again here i bring you my third plugin MovieLauncher. 1.Extract contents of zip file into your Launchbox/Plugins directory. 2.Add your films etc via a new platform. 2.Point Launchbox to Moviedummy.exe as emulator(optional). 3.Add artwork via edit menu(optional). 4. Right click Movie and launch with LaunchMovie. All feedback is much appreciated , thank-you Superfurry (Paul) MovieLauncherv1.00.rar
  16. Hi! I´m new with this awesome backend, and i´m suffering to do something. I have created a .bat file to edit a registry key in windows, "It contains controller configuration" and it´s needed for a game. I set the option Auto execute before the main application. The problem is, that, launchbox starts the game very soon, and the registry settings doesn´t take effect. I tested the .bat, and works perfect, changes the registry, the problem is that the .bat takes 1 second to take effect, but launchbox opens the game before. Any ideas to do this? i searched for an option to delay the launch of the main app before "x" seconds to help the registry to take effect, but launchbox not seem to have that. Thanks in advance, and congratulations to the devs with this marvelous backend
  17. Hi, i'm a long time launchbox user I just write here to know if someone else is having this "issue"... When i use launchbox, and i'm in my desktop PC, i would be able to choose if i want to run the game fullscreen or not... Here is the matter: Would have helped if other than Configure, there was another entrypoint linkable to the game. For example dosbox games, i generally use my own bat files which is good for pathing purposes, but i would like to have other than GAME.bat which loads GAME.CONF another one which is GAME_FS.bat (fs for fullscreen) which loads GAME_FS.CONF but i only see 2 fixed entrypoints: Game (CTRL+P) and Configure (CTRL+G)... Let's take for granted that "Game" runs it fullscreen then (because it would be simpler that way since bigbox maybe only launch the first entrypoint), it would be nice to have another entrypoint for launching a "Game Windowed" version... (It could be also handled in bigbox with a popup, but anyway that's not the major point ) Dunno if all of this makes senses to you... i hope so Just in case it is already doable, and i missed it, please show me the way p.s.: Thank you for your app Jason, it really shows how much do you care for it, and how much do you care for your customers
×
×
  • Create New...