alec100_94

Ok, so it is probably possible to get the plugin working, I already have a vague idea of how it could potentially work. You should be able to make it work manually by just downloading and replacing the settings (and editing slightly). Maybe you could fill me in with some info and i'll try and i'll try and work something out. It's probably easier if we do that over PM to avoid filling up this thread with a bunch of useless information, and so I can send you in development builds to test. I also cannot promise that this will be fixed straight away, as the current build is pretty stable and is working quite well for 90% of people.

I think there might be a way of making it work, though it may be harder than I initially thought. I am going to ask what is possibly a stupid, What real advantage does using RocketLauncher for PS2 games provide? I personally never really saw the point in RocketLauncher, as it just another in between program that ultimately does very little. One of the main reasons I originally developed this plugin was to achieve a good per-game config solution without using an in-between program like RocketLauncher.

@kmoney Thanks for that it might be useful, but let me word my previous question in a way you'll understand. Please post a screenshot of your Tools > Manage Emulators > RocketLauncher > Edit > Associated Platforms Window that displays PS2 and the full Default Command-Line Parameters column.

@kmoney, could you tell me a little more about how RocketLauncher takes commandline arguments for PS2 games?

Does RocketLauncher not offer it's own solution for per game configs anyway? Though I imagine my plugin might give the superior experience at this stage. I've got a couple of other relatively minor issues that need fixing anyway, so I'm probably doing a revision 2 release later, so I'll try and add in a RocketLauncher fix.

@kmoney, Then yeh that'll be the problem, This emulator expects PCSX2 to be the associated emulator. I'll try and think of an appropriate fix for RocketLauncher but personally I am not a fan of it.

@kmoney Ok, So where are your PCSX2 folder and launchbox folder located on your computer? Also post a screenshot of your PCSX2 folder.

The updated version of this, with the fancy new features is now released and fully functional. See original post for more information.

I'll add a readme in the next update, lol. Just to clarify the "PCSX2 Configurator" Folder should go in LB's "Plugins" folder. That should make config clickable on PS2 games and add a "PCSX2 Configurator Settings" to the tools menu. I am currently working on the next update, which will allow optimised settings (courtesy of @Zombeaver) to be downloaded directly from the plugin.

@Darkcloud Ok then the plugin is not still installed, the configure option is supposed to be there (greyed out) and is there for every game in launchbox and has nothing to do with my plugin (My plugin just gives it a purpose). Now for the actual problem, you say it just crashes with no error on a steam game, so what differentiates a steam game from a GOG game on your setup? Are the steam games pointed to a steam style shortcut instead of an executable, If so try changing the location to the executable directory for a couple of games and see if the problem still occurs (though steam shortcuts seem fine for me), Is there anything I can do to try and replicate your problem?

Ok, The naming shouldn't really make a difference. It sounds completely wrong that the plugin should stay install, even if removed. Please paste a screenshot of your launchbox plugin directory. Also when does it actually crash, is it on trying to start the game or simply on selecting it?

Could you please post what error you are getting, what do you mean by using libraries with custom names? The folder contained in the zip file (containing DLL, ahk, ini) should be placed in the plugin folder as is.

@UnderwoodNC, you could definitely try and implement it like that if you wanted and see what results you get, and the current method isn't as visually jarring as it sounds. I'll mess around with it more when I'm developing my next plugin, as the plugin I am currently working on (PCSX2 Configurator) just has the item hidden all the time with no action. If your confused to how that is useful look for my next release of said plugin, which will be released with full source code.

I fixed a bug in the above code, where it may not have hidden the separator properly. It should be pretty much ready for plug and play use (with the minor annoyance of sometimes being able to see items hide, if anyone knows a solution that would be great). This got me thinking that there are a lot of really cool things Launchbox has the potential to do, but not really particularly easily through the exposed plugin system. If @Jason Carr is not planning on extending the plugin system any time soon, then I was thinking of starting a community created helper library, primarily focused on reflection (to access non-exposed methods/fields), allowing a less experienced programmer to do some of the more complicated tasks in Launchbox, and ultimately make the plugins they want.

Miraculously after spending about six hours trying to figure this out I was able to come up with a solution that appears to mostly work, with the small caveat that you can see the item being hidden/displayed very briefly (if used like described above), this may be possible to fix in the future, but for now this seems to work fine. The solution is quite complex (making use of reflection), but is wrapped up into an easy to use function that can be copy + pasted into virtually any IGameMenuItemPlugin. If there is a bug that I've not discovered yet, report it and it will get fixed. It seems most things with the context menu (and probably other things) can be done if you know what your doing. Though better built in support for this would be nice, I kind of understand why it's not in there. private void HideContextMenuItem(bool hide) { // Gets the context menu from Launchbox Main Form var contextMenuStripField = PluginHelper.LaunchBoxMainForm.GetType().GetField("contextMenuStrip", BindingFlags.NonPublic | BindingFlags.Instance); var contextMenuStrip = (ContextMenuStrip)contextMenuStripField.GetValue(PluginHelper.LaunchBoxMainForm); // Hides or shows the menu item with this plugins caption for (int i = 0; i < contextMenuStrip.Items.Count; ++i) { if (contextMenuStrip.Items[i].Text == Caption) { contextMenuStrip.Items[i].Visible = !hide; break; } } // If all plugins in context menu are hidden, also hide the last seperator for (int i = contextMenuStrip.Items.Count - 1, itemsHidden = 0; i > -1; --i) { if (contextMenuStrip.Items[i].GetType() == typeof(ToolStripSeparator)) { contextMenuStrip.Items[i].Visible = (itemsHidden == contextMenuStrip.Items.Count - i - 1) ? false : true; break; } if (!contextMenuStrip.Items[i].Visible) itemsHidden++; } // Write the changes to the context menu back to Launchbox Main Form contextMenuStripField.SetValue(PluginHelper.LaunchBoxMainForm, contextMenuStrip); }

I know the above code works, I am actually trying to hide the item (not just disable). I was trying to do it by accessing the children of the main form, I was able to access the container window (image view), but not the individual games (hence not the context menu). To me no way of manipulating the context menus, if the developer desires, seems like a pretty big omission and could lead to some much cleaner plugins if used properly. I have joined the discord channel and posted in the plugin development section, which seems like an awesome community of LB developers. Hopefully someone on there will at least be able to clarify if it is even possible or not with the current system.

The bug with windows games is now fixed. A new version with more options should be done within the next couple of weeks.

The initial post I made does seem a bit unclear reading it back, so basically all I am trying to do is hide the IGameMenuItem when it is not valid (i.e. greyed out). I want to do something like shown below, however am unsure how to actually go about hiding/showing the Menu Item. I will also check out the discord channel. public bool GetIsValidForGame(IGame selectedGame) { var emulator = PluginHelper.DataManager.GetEmulatorById(selectedGame.EmulatorId); if (emulator != null && emulator.Title == "PCSX2") { // Show Menu Item return true; } // Hide Menu Item return false; }

Hi, I have mentioned this a couple of times to no response, so after spending a long time trying to figure it out, I thought I would make a new topic about it as it's starting to annoy me. Essentially what I am trying to do is have a custom menu item (IGameMenuItem) be hidden or removed when a game that does not meet a criteria is required. I am aware that there is no built in method in the plugin system that will conveniently do this (with Show In Launch Box, only appearing to trigger on startup) and I am also aware this may be deliberate. But I feel like this should be able to work somehow, without modifying launchbox, so I attempted to access the selected games context menus directly, using the built in form features. My problem was I couldn't find where the controls were for the games, I was able to access the view that the games appear in, but this control had no relevant child controls. This has left me a little baffled as to how the primary form window in Launchbox is actually structured, and how to manipulate it. Adding a reference to the control or context menu for each game to the plugin system would be extremely useful for more advanced users, but I feel that there is probably a way to solve my problem under the current system and I'm just missing it. Knowing if this can be achieved and how to achieve it would be much appreciated. And if manipulation of the context menu has indeed been deliberately left out, and not just overlooked, I would like to know why. Launchbox is really really great software, but I have always felt it has always had these small, minor but annoying limitations, that usually make doing certain things cumbersome, and it appears this also extends to coding with the plugin system.

I was wondering if it would be possible (perhaps via the plugin system), to create custom Theme Settings (Maybe as Bindings), that could then be conditionally queried through the XAML files, and what the syntax for accessing them would be. I am currently creating a Theme that could really do with some changeable settings.

Implementation-wise this seems like it would be pretty straight forward to do, though i'm not entirely sure how you could achieve the sub menu with the current setup (or if its even possible), giving access to the underlying MenuItem (Presumably System.Windows.Forms.MenuItem) would fix this and a bunch of other minor annoyances. Please correct me if it is already possible to get the underlying MenuItem.

This is a plugin I am developing with the goal of enhancing and adding additional functionality to the way LaunhBox handles CommandLine parameters, all suggestions and feedback are totally welcome and will probably be implemented if deemed appropriate and possible. This will act as a replacement for the other plugin I created (AutoHotkey Manager), which was kind of a hacky solution, and relevant functionality of that plugin should eventually be implemented. The current build of this plugin will silently append a games custom CommandLine parameter to use the emulators default CommandLine and Platform specific default command line (where applicable), if no other custom CommandLine is specified, this works extremely well for multi system emulators (like retroarch), to apply a global setting for all systems. All custom CommandLine's can still be tweaked and no custom CommandLine's will be overwritten by this plugin. The current version of this plugin is attached, and progress (and updates), on this plugin and my other launchbox content, can be found on my GitHub. It will be uploaded to the files section when deemed ready. I also have a few questions/suggestions about plugin development, mostly for @Jason Carr, Can I / Will it be possible to: Move Game Menu items, Having plugins unordered at the bottom of the list is a minor annoyance, I know this has already been raised. Hide Game Menu items when they are not applicable, it's always seemed dumb to me that "Configure" shows up on every game despite it only being useful for windows and dos games, though having my other plugin (PCSX2 Configurator) show up on every game is extremely dumb as it is emulator specific, it would be great if it were possible to have these options not show up when they cannot be used (at least for plugins). Capture which game triggered an On-Game start event, right now we know a game started but not which one, rendering the information far less useful. I wanted to do something like this in this plugin, however ended up just looping though all games (which may be slow in a big library), and may as well be an On-Launch event without knowing which game was started. Overall the plugin system seems good, easy to develop for, and easy to use, keep up the good work. Better CommandLine.dll

The bug was fixed before, but it appears I made a mistake when uploading the new version (added it as an attachment, instead of replacing the original), This has now been fixed and downloading the file will be the latest version. It's recommended that anyone using the plugins downloads it again to ensure a bug free experience. You may also need to unblock the .dll in windows for launchbox to launch it, I'll upload the next version as a zip file.

The colon bug is fixed in v0.91, try re-downloading the file from the files section, it should be the updated version.

I'll look into this error later, in the meantime try running launchbox as admin and let me know where your launchbox and pcsx2 are located.