Jump to content
LaunchBox Community Forums

PCSX2 Configurator Next Beta 2

   (18 reviews)

2 Screenshots

About This File

PCSX2 Configurator Next for LaunchBox
PCSX2 Configuartor Next is a plugin for LaunchBox that allows users to easily configure PCSX2 on a per-game basis. The plugin also allows for pre-optimised configs to be downloaded from right within LaunchBox for a whole host of popular PS2 games, from Zombeaver's excellent PS2 Configuration Project.

Installation
The plugin is easy to install and simply needs to be downloaded and extracted. The archive contains a folder called "PCSX2 Configurator Next", this should be placed in the root of the "Plugins" in the user's LaunchBox directory. Any previous versions of the plugin should be removed before attempting to install this version.

General Usage
The plugin is relatively straight forward to use, but has been changed significantly from previous versions. You will first need to have PCSX2 (1.5.0 development build) setup as an emulator in LaunchBox. Then right click on a PS2 Game and choose "PCSX2 Configurator" from near the bottom of the context menu. This will present a menu of options:

"Create Config" - Creates a new config for the game in question based on the users current PCSX2 settings, If a config already exists this will overwrite that config with a new one.

"Download Config" - This will download one of Zombeaver's Config and set it up to be ready to play for the selected game, this will be greyed out if now config is available, and will change to "Update Config" if a new update is available for the downloaded config.

"Remove Config" - This will remove the current config for the selected game, and will be greyed out if there is no current config.

"Configure With PCSX2" - This will open PCSX2 with the config for the selected game loaded, allowing you to customise your config for the selected game (Downloaded Config's can also be tweaked). Once a game has a created config this can also be done using LaunchBox's built in "Configure" from the games context menu. Both these options will be greyed out if there is no config for the selected game.

There is also a "settings.ini" file created in the plugins folder ("%LaunchBoxDir%/Plugins/PCSX2 Configurator Next"), this can be tweaked manually but most settings don't need to be touched in most cases. Some people may wish to change the "GameConfigsDir" which is where the created configs are stored, this deafults to the users PCSX2 "inis" directory. There is currently no inteface to modify these settings, but that is planned in a future version.

Version Info and The Next in The Name
This version of the plugin is the successor to the original PCSX2 Configurator plugin, with a completely re-worked codebase from that version, and full compatibility with LaunchBox.Next (which is now the current version of LaunchBox). The main reason "Next" was added to the name is to initially seperate it from that (now discontinued) verison of the plugin. This release is currently in Beta and the "Next" from the name will probably be dropped eventually for a stable release with more features.

Credit and Support
I have personally put a lot of time and effort into all versions of this plugin, with it essentially being my free-time pet project for the last year and a half. Though I know the plugin would not be what it is today without Zombeaver who really helped me to bring this plugin to the next level, by allow me to integrate his PS2 configurations into it as well as creating artwork and helping me test the plugin. I would also like to say a big thank you to spectral, neil9000, and kmoney for helping me out with testing, and of course Jason Carr for making LaunchBox and implementing some of my requested changes into the plugin engine. I intend to keep working on this plugin, and fix any reported bugs as well as update the plugin with new features. So if you have any problem or feature request's hop over to the plugins thread on the forums and let me know. The project is also open sourced under the MIT license and can be found on my github.

 

UPDATE (JUNE 2020): This Plugin is now in maintenance mode, and is nearing end of life. I am currently working on a standalone version that will serve the same purpose, which will also be made to work with LaunchBox. The progress of that can be found here


What's New in Version Beta 2   See changelog

Released

New in This Release:

  • Custom Command Line Parameters can now be specified a part of a config. A file called "cli.txt" should be placed in config directory with parameters separated by commas and/or line breaks.
  • User can now have multiple versions of PSCX2. The Title of the version that the plugin will use can now be specified in Settings.ini (Pcsx2BuildTitle).
  • Nicer handling of Absolute Paths. All Absolute paths are qualified from the drive's root and no longer reference the LaunchBox directory.
  • Configs directory can now be relative to the PCSX2 directory. This is now the default behaviour
  • No error will be shown if a non critical PCSX2 base config file is missing when downloading a config, before this crashed the plugin.
  • Custom command line parameters will now always update when wrong and/or missing information, but if all information provided is correct edits can still be made.
  • Nicer Drop Shadow on Title Text, also added text-wrap for longer titles.
  • Plugin now uses the PCSX2 Icon.
  • Major Code changes and refactor (Does not affect User).
  • Just a quick note about Updating from a previous release. I advise you first delete your Settings.ini file from the plugins directory, and let the plugin recreate it, as this version handles some of the settings slightly differently.

HOTFIX September 2020 - fix for new versions of Launchbox (11.4+), with new folder structure

HOTFIX June 2020 - fixes issue with issue with pnach files not overwriting existing files, also adds widescreen as default for remote configs

HOTFIX April 2020 - fixes issue with 7zip being moved to third party folder

  • Like 22
  • Thanks 18
  • Unusual Gem 4

User Feedback

Recommended Comments



Hey, guys. I'm still getting the "The system cannot find the file specified" error even when downloading the dll file from this comments section. I've noticed it only happens on new games i add to launchbox, old games work as intended. I can play the new games so it's just the plugin that appears top be the issue. I've got version 9.2 of launchbox which is the one I payed for so maybe I need an older plugin but I can't find it. thanks in advanced.

EDIT:- Ok i've updated launchbox and still getting errors, I don't know what to do anymore.

r8hN5Vi.png

Edited by RogerioX
Link to comment
Share on other sites

@alec100_94

I can't get PCSX2.Configurator.Next.Beta.2.Hotfix.2 works with the latest beta of LB. I've unlocked the zip and the dll, extracted the folder in the root of the Plugins folder of LB but when i right click in to a PS2 game, the "PCSX2 Configurator" does not shows up. LB creates the "Settings.ini" file in \LaunchBox\Plugins\PCSX2 Configurator Next so i think is not LB related issue. Any tips?

Thanks

Link to comment
Share on other sites

I just did a launchbox update and the pcsx2 configurator no longer appears as a selection when I right click.  Also, when I right click on a game in LB that had a configuration set up and select Configure it tells me there is no path to it.  I double checked, all the config info is still in the inis folder of the pcsx2 directory so that did keep me from jumping out a window.  I tried to reinstall the configurator but it didn't change anything.  Should I just wait for the new version you're working on to be released and put my configurating on hold for now?  Thank you so much for the hard work on this stuff! - mike

  • Like 1
Link to comment
Share on other sites

Hi, I hope this is still in maintaince mode until the release of the much anticipated stand alone version being fully ready for its debut, because as of the latest version of Launchbox as Mike above has said it doesnt show the configure selection and as far as im concerned has rendered PCSX2 redundant until this functionality is replaced (and i mean that with the utmost gratitude to its creator) without this configurator or its successor (or indeed "in-house" per game settings configuration provided by PCSX2 itself) PCSX2 is simply unusable as having to remember, test and re-test, and re-apply setting for every game as and when starting to play each title is beyond excruciating. Please release a hotfix until the new version is ready or if the new version is oh so almost ready let us now an eta. Thank you. :)

Edited by W4rCh1ld
Link to comment
Share on other sites

I don't know what the problem is with Launchbox and why the new update suddenly breaks it. It might be an issue to take up with @Jason Carr rather than myself as it did work perfectly fine in older versions and doesn't really do anything none standard that a plugin wouldn't be expected to. The new version is in development although I have kind of put that on hold for now, and not sure when I'll get back around to finishing it. The current version of the new app can be downloaded from here  (also linked on my github, above). It is not quite complete yet It, but works reasonably well for general use (I use it myself to launch and play PS2 games). It is a standalone app and the Launchbox integration is one of the big features that is missing currently. I can't make any promises on when I'll get back around to working on this again (some other things came up), but will try and have a stable release at some point before the end of the year. As for this legacy version, again I am not sure. If it's something relatively simple I can fix it otherwise it's not really worth my (limited) time.

Edited by alec100_94
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

18 minutes ago, alec100_94 said:

I don't know what the problem is with Launchbox and why the new update suddenly breaks it. It might be an issue to take up with @Jason Carr rather than myself as it did work perfectly fine in older versions and doesn't really do anything none standard that a plugin wouldn't be expected to. The new version is in development although I have kind of put that on hold for now, and not sure when I'll get back around to finishing it. The current version of the new app can be downloaded from here  (also linked on my github, above). It is not quite complete yet It, but works reasonably well for general use (I use it myself to launch and play PS2 games). It is a standalone app and the Launchbox integration is one of the big features that is missing currently. I can't make any promises on when I'll get back around to working on this again (some other things came up), but will try and have a stable release at some point before the end of the year. As for this legacy version, again I am not sure. If it's something relatively simple I can fix it otherwise it's not really worth my (limited) time.

Stuff was moved around, new folders exist. Plugin needs updating or removing.

image.thumb.png.b9c2fe78b5752c059b3445012c4c17a1.png

Link to comment
Share on other sites

12 minutes ago, alec100_94 said:

@neil9000 Any idea of the details on what's actually changed and needs to be updated?

Im not sure exactly, but 11.3 has moved to .net core instead of Standard .NET, and that necessitated moving a lot of files as .net core requires the .dll's and .exe's to be in the same folder, so a few files and folders in the Launchbox folder are now just links to the same files in the Launchbox/core folder.

image.thumb.png.3e6f2c8410c61c95ce3d526f4f88f223.pngimage.thumb.png.767c64c1780851979c1a17a9bfc347b0.png

Link to comment
Share on other sites

Ah okay, makes sense now, thanks for that. Dot Net Core is a much nicer solution over Dot Net Framework anyway. I'll see if I can easily re-target this legacy version of the plugin for dot net core. Also means I'll be able to build the new plugin based on Dot Net Core too, which is a plus.

Edited by alec100_94
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

21 hours ago, alec100_94 said:

Ah okay, makes sense now, thanks for that. Dot Net Core is a much nicer solution over Dot Net Framework anyway. I'll see if I can easily re-target this legacy version of the plugin for dot net core. Also means I'll be able to build the new plugin based on Dot Net Core too, which is a plus.

Thanks for your efforts. If we could get another hotfix for the existing plugin that would be much appreciated! Also this is unrelated but I noticed that since the update my memory cards (i.e. save files) are not found either. Is this because the plugin no longer inserts/ejects game-specific memory cards?

If you don't have time to update the plugin (which is totally understandable) do you know of a way to use previously created configs in PCSX2?

Edited by Thornback
  • Like 1
Link to comment
Share on other sites

Adding my voice that the PCSX2 Configurator no longer works in 11.3 and up; and, since (I'm pretty sure that) it hooks the running of the actual emulator to point to the individual config files, they are not loaded - therefore the memory cards are also not loaded.

I do very much appreciate your work, Alec! This utility/plugin is a GODSEND for enthusiasts like me who just find juggling PS2 configurations a big hassle. Keep up the wonderful work!

Link to comment
Share on other sites

On 8/29/2020 at 8:37 AM, EazyCheeze1978 said:

 (I'm pretty sure that) it hooks the running of the actual emulator to point to the individual config files, they are not loaded - therefore the memory cards are also not loaded.

It adds a custom command line to load the specific config file in LB. Should still load fine.

Edit: Looks like I had some of my titles still using RocketLauncher which can do the same thing, doh.

Edited by Headrush69
  • Like 1
Link to comment
Share on other sites

20 hours ago, Headrush69 said:

It adds a custom command line to load the specific config file in LB. Should still load fine.

Well, shoot... seems that none of those were written... I don't know exactly why, but it should be no problem to recreate them... now just need to look up the command line to put in there manually. Thanks for putting me on to that solution! :)

Okay something I have discovered, maybe a bug with LB but: apparently, while the Emulation custom command line that I enter for each game is saved and used, every time I open the Edit dialog to change it, the custom command line field is wiped, so once I've changed it to the right command line, if I want to change it again, I'll have to enter it all over again. Not sure if that's by design, but it's no biggie either way. Thanks again :)

Edited by EazyCheeze1978
Link to comment
Share on other sites

1 hour ago, EazyCheeze1978 said:

Okay something I have discovered, maybe a bug with LB but: apparently, while the Emulation custom command line that I enter for each game is saved and used, every time I open the Edit dialog to change it, the custom command line field is wiped, so once I've changed it to the right command line, if I want to change it again, I'll have to enter it all over again. Not sure if that's by design, but it's no biggie either way. Thanks again :)

I highly doubt that is by design.

What version of LB are you running?

I haven’t updated to 11.3/4 yet, so maybe it’s related to new version. Is it possible that some how your PS2 xml file in LB is read only?

Link to comment
Share on other sites

53 minutes ago, Headrush69 said:

I highly doubt that is by design.

What version of LB are you running?

I haven’t updated to 11.3/4 yet, so maybe it’s related to new version. Is it possible that some how your PS2 xml file in LB is read only?

The newest so I guess 11.4. No, I just checked and it's not read-only.

Link to comment
Share on other sites

2 hours ago, EazyCheeze1978 said:

Well, shoot... seems that none of those were written... I don't know exactly why, but it should be no problem to recreate them... now just need to look up the command line to put in there manually. Thanks for putting me on to that solution! :)

Not written for me either.. What custom command line are you using?

Link to comment
Share on other sites

So I tried to re-target this for Dot Net Core, and I got it to build fine but didn't seem to be working in LaunchBox at all, it didn't even say "Loading Plugins" when starting LaunchBox, so I don't really know what I'm missing. As for the custom command line it will never work properly without the plugin or some sort of other custom script. That setting (along with the configure button) is generally only made for PC games and LaunchBox will unhelpfully delete it from anything that isn't PC or DOS. The plugin dealt with that so the command line was retained. For anyone just wanting to launch and play PS2 games I strongly recommend using the new (in-development version) linked above. Doesn't work with LaunchBox yet but has most of the other features.

Edited by alec100_94
  • Like 1
Link to comment
Share on other sites

5 minutes ago, Thornback said:

Not written for me either.. What custom command line are you using?

IIRC, "--fullscreen --cfg_path="inis\[Game Name Here]""

The games' paths will be there if the Configurator worked for them before, but you'll need to create them, copy existing INI files over and modify them manually if you have any new games since the Configurator stopped working.

  • Thanks 1
Link to comment
Share on other sites

13 minutes ago, alec100_94 said:

So I tried to re-target this for Dot Net Core, and I got it to build fine but didn't seem to be working in LaunchBox at all, it didn't even say "Loading Plugins" when starting LaunchBox, so I don't really know what I'm missing. As for the custom command line it will never work properly without the plugin or some sort of other custom script. That setting (along with the configure button) is generally only made for PC games and LaunchBox will unhelpfully delete it from anything that isn't PC or DOS. The plugin dealt with that so the command line was retained.

Oh no! Yes, this I just discovered... the command line works within the same session of LaunchBox, but they are removed in the next one. Yes, definitely a bug.

And I really wish you luck in addressing this issue - seems something very profound that I don't understand has changed in the supported plugin structure of LaunchBox (the different version of .NET probably, changes more than just the expected path). Strangely, the old "Image Search" plugin by NJDave71 shows up in the menu, when the DLL is in its place in the plugins folder. But it doesn't work when one clicks on it.

Edited by EazyCheeze1978
Link to comment
Share on other sites

Well Im keeping an eye on the progress of this while trying to decide if... going back to LB 11.2 where it worked fine, or going to the stand alone that works outside of launchbox is the better option, is there a guide on the in deveopment version as from what i can tell at a glance is that the PCSX2 folding is located inside the stand alone configuarator file, would be nice to see a set up video (Looking at you Unbroken Software or ETA prime... lol). :)

Link to comment
Share on other sites

Updated now with a version that works it wasn't really that much of a change tbh (actually didn't need to re-target anything). Credit to @JoeViking245 for helping me find a fix quickly. For anyone confused about the in-development version, it can be downloaded under Artifacts on the linked appveyor page  (and that will be updated with new builds, whenever I add new stuff). It is still in development so liable to change, hence a tutorial video may not be a good idea at this point. The basic idea of what's going on is that the program manages PCSX2 versions for you, so you don't ever have to worry about installing it yourself. To install a PCSX2 version you click the cog (in the program) and select version manager and it will give you a drop drown (I'd recommend 1,6.0 for most people). Full Launchbox support for the new standalone version is coming, I've just been busy with other things so not got around to working on it recently.

Edited by alec100_94
  • Like 1
  • Thanks 1
  • Unusual Gem 1
Link to comment
Share on other sites


Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Add a comment...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...