Lahma

Just wanted to touch base here and say that I will be responding to this thread and giving some more technical insight into what cammelspit is asking for a timeline on. It will probably take a good while for me to collect and organize my thoughts into a coherent response that will make it easy for Jason to understand (from a programming perspective) what cammelspit (and I) are hoping will be added into the plugin API in future releases. I will try to post a detailed synopsis tomorrow if possible, but I might not get to it until Monday. Thanks cammelspit and Jason!

Thanks for your help. I was able to resolve the issue. I gotta say however that the whole process isn't exactly intuitive... When I initially posted the new version, I followed the correct procedure, except instead of adding the updated version via the "Choose Files" button under the "Upload Your Files" heading, I instead dragged my file into the "Drag files here to attach" box under the "What's New" text box (as you correctly stated above). Now that I understand how the whole process works, and what fields apply to what (specifically to the "Download" button), it clearly won't be a problem moving forward, but I think the process could be made a lot clearer for new users. I'm sure the forum uses an off-the-shelf product, but I also imagine it can be modified fairly easily. It might be worth the time to simply indicate on that page (that you provided a screenshot of) that the file listed under the "Choose Files" button is the default file that will be downloaded when users click on the main "Download" button on the plugin page. Just a friendly suggestion. Oh and one more thing that wasn't at all clear to me after initially posting my plugin was that there was a forum thread automatically created for people to comment and ask questions on. I was actually a bit confused after I added the plugin, because my expectation was that the plugin download page would actually be the forum thread itself, with all subsequent posts showing up below the main plugin description. Whenever I saw that there wasn't any "Reply" button or anything (only "Reviews" and "Comments"), I just figured there must not be any forum thread automatically created for the plugin. Only later after receiving notifications and such did I realize that a thread had indeed been automatically created, but I still didn't know how to find that thread independently outside of the link in my notifications. I never would have guessed that the "Get Support" button would be a link to that thread until someone told me, as I guess I just assumed that button would send the author of the plugin a PM or something... Perhaps I'm the only person to ever post a plugin that has been a bit confused by these things, but somehow I doubt that. With just a couple of quick, easy changes, I think things could be greatly clarified. If I'm just a blind idiot and the only one that feels this way, then by all means, just disregard my long-winded suggestions and move on with your day I'm just trying to be helpful! Thanks again CriticalCid!

I've already uploaded a new version, and I removed reference to the old version. That isn't the problem. The problem is, the main "Download" button on the page still downloads the old 0.9.0.0 version. Try it yourself and you will see what I'm talking about. Then browse to the bottom of the page, and you will see the only version available at the bottom of the page is 0.9.0.1.

If anyone could help me with a quick question on my plugin download page, I would greatly appreciate it. I'm the author of the "SteamLauncher" plugin, and I just spent the last hour trying to help a user with an issue he was having with my plugin. I finally figured out what the problem was, and it had nothing to do with my plugin, and was quite unexpected. After the Steam client updated, I had to make some changes to my plugin to maintain compatibility, so I uploaded an updated version (v0.9.0.1). The problem is, the main "Download" button on the plugin page still downloads the old version of the plugin, which for all intents and purposes is totally non-functional now. Although a link to the updated version of the plugin is available at the bottom of the plugin page, most people by default are just going to click the download button and not pay attention to anything else. Am I doing something wrong here, and if so, how do I change the version that the download button points to. If I'm not doing anything wrong, is there some way to fix this? Thanks!

Hey CosmicDan, Sorry it has taken me so long to respond.. I've just been really busy lately. You're absolutely right, I never posted the source to GitHub, and there is really no excuse for that. If I had any indication that anyone actually wanted to look at and/or use the source code, I definitely would not have procrastinated so long. Since it seems that you are indeed interested though, I will go ahead and get it done. I will try to have it posted by the end of the day today or tomorrow (April 8th or April 9th). I tend to get a little nitpicky about cleaning up the code before posting it publicly, so the process never goes as quickly as I would like Now, on to your other comments/questions... Where to start? The thing you are describing (with the standalone stub EXE) is exactly what this project was created to do away with. I'm not sure if you've heard of "GameLaunchProxy", but it is essentially exactly what you're describing. It was originally created by another user on these forms, Nielk1. However, when I came upon it, it was no longer functioning due to changes in the Steam API, and Nielk1 was no longer updating the project. I took it upon myself to fork his code and update it so that it would function again with current Steam versions. You can find my fork here: https://github.com/lahma69/GameLaunchProxy I haven't used it recently, and I can't recall at this moment if any major changes have been made to the Steam API since I last updated it that would cause it to no longer function, but if it isn't working, it would be very easy for me to fix the problem... So, if its something you are interested in using, give it a shot, and let me know if you have any problems and I can push out a quick update for you. Wrapping your head around how it works is initially might be a little bit difficult, but it shouldn't be too hard to figure out. To be perfectly honest though, the entire project got very little attention, and seemed to have very few, if any, users. I think the difficulty required to set it up and use it properly (which is an inherent problem to any generalized approach that can work with basically any launcher) is probably what kept it from being widely utilized. That is exactly why I created this LaunchBox plugin. Its intent was to greatly simplify things and essentially make the entire process a zero configuration, 1-click affair. The last point I'll address is about making "Launch via Steam" the default launch option. While this would be extremely valuable, and has been requested by other users besides you, it is unfortunately not possible using the built-in LaunchBox plugin API. Unfortunately the API is extremely limited. I won't go too far into the details, as if you're interested, you can take a look at the API yourself to get an idea of what I'm talking about. There is actually much more versatility I would have liked to have added into the plugin, but the API at this point just isn't versatile enough to do much else. This isn't to say that adding such features through other means such as code injection would be totally impossible, but due to LaunchBox using the .NET Framework, practices such as code injection are actually not at all straightforward or simple. I've actually done a lot of experimentation as far as adding additional features that fall outside of the plugin API's supported abilities, but at this point, the only success I've really had is with deobfuscation and modification of LaunchBox EXE/DLL files themselves. I'm pretty sure Jason, the author of LaunchBox, would not be a happy camper if someone starts releasing modified versions of his code without his permission however, so unfortunately that path is a no-go for public release. Hopefully Jason will make extensibility updates to the plugin API a priority sometime in the near future though, and maybe at that point I can add some of the additional functionality people have been requesting. Anyways, thanks for the kind words CosmicDan. Its always nice to know that someone is enjoying the result of all the time put into creating such a project (and keeping it updated and functioning with all of Valve's erratic constant changes to the Steam API). If I failed to answer any of your questions or if you have anything else you'd like to discuss, feel free to post a response, and I will try to respond a bit quicker this time! Thanks again.

Just wanted to note for future reference that we talked on Steam and got the problem resolved (not an issue with the plugin).

Lol, you did tell me that didn't you.... Ugh.. I'm an idiot.

Percy, will you enable debug logging (see the plugin info under 'Debug Logs') and then try the plugin again (you might try it a couple of times in BigBox and in normal mode just so we get more than enough data in the log). Once you've done that, if you could send me a copy of the debug log and a copy of your configuration file, I think we can probably figure out what your problem is and get you up and running again.

Nielk1, thanks for helping out with some of the questions and stuff prior to me realizing this thread even existed. I really appreciate it.

Musungo, were you using the beta Steam client and v0.9.0.0 of this plugin when you were having the problems? If so, I would recommend updating to v0.9.0.1, as I fixed the plugin to work with the new Steam beta that was pushed out on Feb 14th. If the new version of the plugin still isn't working, I would be happy to look into the problems for you. Look at the plugin info under the heading 'Debug Logs' and follow the instructions to enable debug logging, and then send me a copy of the logs after you try the plugin again and it crashes.

Again, like I've told everyone else, I'm really sorry for not seeing your question earlier.. I'm a moron and didn't realize this thread existed. However, to answer your question, no, unfortunately there is no way to set SteamLauncher to be the default option for running your roms in LaunchBox. The plugin API simply doesn't support doing such a thing, so it would require doing some ugly hacks like code injection. If enough people wanted such a thing, I could look into it, but it would never be a "clean" solution, as LaunchBox updates would always have the possibility of breaking the plugin. Sorry.

Hey Percy, so I'm using LaunchBox 8.1 and I just tested v0.9.0.1 of the plugin with both the non-beta and beta Steam client and both the regular LaunchBox and BigBox are both working fine for me. Did you try "unblocking" the DLL as Neil9000 suggested? If you look at the plugin info page under 'Debug Logs', it describes how you can enable debug logging for the plugin. If you continue to have problems, enable the debug logs and send me a copy of them and I'll take a look to see if I can figure out what's going on. I suspect there is some other problem at play here though if the plugin was working fine before and only stopped working after you updated LaunchBox (cause like I said, I'm running LaunchBox 8.1 as well).

Neil, I totally forgot about that, and I wish I would have seen your post earlier (see my previous post for why I did not). I will definitely add this info at the top of the plugin page. Thanks for the heads up.

Wow, so I'm a total moron... I didn't even know there was a separate forum thread associated with the plugin download page (which I thought was really strange actually). I've had my own plugin bookmarked at https://forums.launchbox-app.com/files/file/972-steamlauncher/ instead of this URL, so I didn't even realize this thread existed lol. So sorry everyone.

For anyone that is interested, I finally got a public build of the plugin posted. Please give me some feedback on the project page if you can. Thanks everyone.

I finally got the plugin posted: I haven't uploaded the source to GitHub yet, but I will later today or tomorrow. The GitHub url will be on the project page posted above. Please give me some feedback if y'all can. Thanks everyone.

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  

I didn't really look over your plugin code, but from some forum posts I saw in passing, it sounds like you managed to overcome a lot of the inherent limitations of the plugin API. I need to take some time and look through your code. Hopefully at some point, some more advanced functionality will be built into the plugin API, because there is really so many more useful things that could be accomplished with just a bit more functionality built into the API. By the way, sorry I didn't get the plugin pushed out yesterday guys. I've been working feverishly on it... "Wrapping up" code for public release is always a bit more time consuming than you first recon it will be. I will definitely get it pushed out today though (hopefully here shortly).

I tried Steam Rom Manager, but I just hate cluttering up my Steam library with all of my roms and such... especially when LaunchBox already does such an excellent job of organizing my entire rom/emulator collection. I know the author (FrogTheFrog) of Steam Rom Manager, and he undoubtedly put a lot of time and effort into making that app, so I'm definitely not downplaying its usefulness. However, I think most of us who paid for a LaunchBox license did so because we appreciated the ease and customization that it provides for organizing a large rom collection... and that is something that Steam just wasn't made to do. My ultimate goal with this was to be able to continue using LaunchBox to manage my entire rom collection, but also be able to easily use the Steam overlay (and therefore Steam controller bindings) with anything launched from the LaunchBox UI. P.S. Speaking of FrogTheFrog, if you use the Wii U emulator Cemu, and also have a Steam controller, you should checkout his app 'Steam Gyro for CemuHook'. It is awesome!

That sounds like a neat setup! I use Nvidia gamestreaming occasionally with the Moonlight app on my Android phone or tablet. I have a GameSir G4S controller that has a built in phone mount, so I guess that sort of accomplishes the same thing as your ipega in a way. I usually only use it when I'm out of town though, rather than when I'm at home. I host a VPN server on my router which I connect into when I'm away from home, and as long as I have a decent internet connection wherever I'm at, it surprisingly works pretty well. I didn't even think about my plugin being useful for that.. but it certainly would make it easier to setup LaunchBox/BigBox as a GameStream application and just use that to launch everything through Steam (and therefore still be able to use my normal controller bindings). Anyways, I'm going to get back to finishing the public build of the plugin. Should be up here in a few hours.

Ok, sounds great. Once I'm done with the final touchups here in just a bit, I will do exactly that. Thanks for the info!

For anyone interested, I've created an entirely new app (well, plugin really) for launching roms/emulators from LaunchBox through Steam. It is a simple plugin for LaunchBox that only requires you to drop a DLL into the LaunchBox plugins directory and that's it.. everything is done automatically. You simply right click on the game you want to play in LaunchBox and select the menu option "Launch via Steam" and the emulator/rom will launch through Steam, giving you access to the Steam overlay, controller bindings, etc. CammelSpit has been helping me test it out a bit, and it appears that it is ready for public release. I am going make some final comments and cleanup the code a bit, then I will compile a final release and push it out onto GitHub. It should be up later today. Whenever its ready, I will make a new topic for it and post the topic URL here for anyone that is interested.

Quick question for anyone interested in this plugin. Do you use the "Launch with" option in a game's context menu often (meaning you use an emulator different than the one you have set as the default for that platform)? Right now, the way the plugin is working is that it is just using the default emulator in order to launch the game/rom in Steam (same as if you just double clicked on the game), and I'm trying to decide if that is good enough. I originally intended to add a 2nd expanding menu option, like LaunchBox's "Launch with" menu option, that would allow you to choose any other compatible emulator to launch the game in Steam, but I quickly learned the LaunchBox plugin architecture was not capable of such dynamic behavior. It essentially just allows you to have static menu options that are created at compile time, meaning you can't create a number of menu options dynamically based off of a user's particular configuration. In the regular LaunchBox interface (not BigBox), it would be possible to get around these limitations by introducing my own popup window that could dynamically display the different emulators available, but doing this in BigBox would be much more difficult and require its own separate implementation (due to the different UI type, controller input, etc). Regardless, I'm going to release the 1st version prior to implementing any of this more complex behavior (if I even decide to), but I just wanted to get some feedback to see if this is even wanted/needed before considering whether to put the time into it or not. Thanks.