alec100_94

PCSX2 Configurator View File PCSX2 Configurator v0.995 Alpha This is a configuration plugin for games being run in PCSX2 through Launchbox. It allows users to configure their games on a per-game basis, and download pre-optimized configurations, from right with LaunchBox. This version is an Alpha, Meaning it has some bugs that I will work with the community to resolve over time. Installation You will first need to have PCSX2 (>1.5.0-dev) setup as an emulator in LaunchBox. If you have used any previous version of PCSX2 Configurator, it is advised that you remove them before installing this version. After this has been setup simply download and extract the zip file, place the "PCSX2 Configurator" folder in your LaunchBox Plugins Directory. Then Start LaunchBox and the plugin will be installed. General Usage Straight out of the box, configs will automatically be downloaded and applied (also updated) for known games, without you (the user) really needing to do much at all. You can disable this on a per game basis using the "Use Remote Settings" flag from a games context (right click) menu in LaunchBox, in the "PCSX2 Configurator" Sub Menu. To create your own config for a game that does not have known settings, you simply use the "Configure" option from within LaunchBox, and then PCSX2 will be started allowing you to configure the settings that you want for that game. You can also use "Configure" to make changes to an existing config (Including Downloaded Ones), though currently any changes made will be overwritten if the config for the game is updated (The Plugin will notify you if this is the case). Settings The Plugin Settings Menu is located in LaunchBox's tools Menu. All settings with "Current" in the name are referring to how the base instance of PCSX2 is currently configured. The default settings make sense in most cases, and these settings should only really be tweaked if you fully understand what the setting actually does. Settings are applied by simply closing the settings window. These Settings will make no meaningful difference to downloaded Configs, and are in-part personal preference. Each of the options is explained breifly below: Use Independant Memory Cards? (default: On) - create a new formatted memory card (In Slot 1) for each game that is configured Use Current Plugin & Bios Files? (default: On) - retains current plugin and bios selection when configuring a game (un-checking this will require them to be re-configured for each game) Use Current GS Window Settings? (default: On) - retains current GS Window Settings (Vsync/Aspect Ratio/Custom Window Size) Use Current Program Log Settings? (default: On) - retains current Program Log Settings, The main purpose of this is to show/hide the console window Use Current Folder Settings? (default: Off) - retains current Folder Settings, This is generally only needed if default folders are not in use (e.g. your folders are in documents, but PCSX2 is in program files) Use Current VM Settings? (default: On) - retains current VM Settings, This Mostly denotes what custom patches/hacks/cheats are enabled, and will usually be overidden by downloaded configs Use Current GSdx Plugin Settings? (default: On) - retains current GSdx (Graphics Plugin) Settings, This will be overidden by downloaded configs Use Current SPU2-X Plugin Settings? (default : Off) - retains current SPU2-X (Sound Plugin) Settings, Not needed in most cases, may be overidden by downloaded configs Use Current LilyPad Plugin Settings? (default: Off) - retains current LilyPad (Controller Plugin) Settings, Not needed in most cases, could be useful if you like to play with a non-standard controller layout for some games Configuartions Directory (default: $PCSX2Dir\inis) - the loaction where per-game configurations are stored, This is in the Emulators ini folder by default though can be changed. you will need to chnage this if your PCSX2 Directory is in Program Files and you are not running LB as Admin This file also contains hidden settings: AllowAllSettings - ensures Presets are disabled and Game Fixes and Speed Hacks are enabled in PCSX2 EnableRemoteSettingsByDefault - Will Disable the "Use Remote Settings" flag for all newly imported games Alpha Testing & Bug Reporting As alluded to earlier this is an Alpha version (I originally wanted to call this release Beta but I don't have that much confidence in my code) and still has a multitude of issues. Most of these are known quantities and are listed in the "Issues" section on Github. If you have experience or notes about any of the known issues, or you feel that a known issue is affecting your experience, please leave a comment on the issue to start a discuission about a potential fix. If you find any other issues or have any other problems please post on the LaunchBox forums or contact me directly. All issues will be fixed/resolved eventually and then this will finally be repackaged as a stable 1.0 release. Credit & History This plugin was created by myself (alec100_94), and began life sometime in June 2017, when I was frustrated with not having a sensible solution for using different Settings with PS2 Games that integrated nicely with LaunchBox. Later that year fellow LaunchBox user Zombeaver messaged me, asking if it was possible to use his pre-made PCSX2 configs with my plugin, so I decided to work with him and add full support for them as a part of the plugin. The plugin has since gained popularity through the LaunchBox community and has evolved into something much more than what is was originally envisoned as. A lot of time and effort has gone into creating this plugin and I would like to say a massive thank you to everyone that has given it a shot. I would also like to say a special thank you to a few (awesome) members of the LaunchBox community who have been great and helped shape this plugin into what it currently is: Zombeaver Spectral ckp neil9000 kmoney Submitter alec100_94 Submitted 05/28/2017 Category Third-party Apps and Plugins  

Here is an updated version, with some changes, allowing it to handle mounts and be compatible with Launchbox's built in DOS installer. I have also tried to make the documentation clearer for this release. I used the CD version of MegaRace for my testing, but going back to the point I made earlier, there is a DRM free version of the game available, which does not require a CD (as there is most DOS Games). Any more suggestions are welcome, and I am happy to try and fix any problems.

Ok, that must have just been an oversight. This release should work on 32-Bit systems, However I have not yet tested. There are no other changes to this version. Let me know how it works.

qwerty123 said Too bad this doesn't work with the 32 bits version of Windows :( It should do. If it doesn't it is probably a simple oversight with an easy fix, however I'm pretty sure it was compiled with the x86 instruction set, and doesn't have any 64-bit dependencies.

I've never actually looked at the mount settings in launchbox. Most games will work without additional mounts if you have the right files in the directory. And a custom dosbox.conf, with just an [Autoexec] section could be used instead. However If you explain in more detail, the problem you are having, I can probably write an updated version to address the issue. Also what game are you using that requires a mount so I can use it in my testing?

It probably was a little vague, you should rename "dosbox.exe" from the daum package to "dosbox_daum.exe" and "dosbox_x64.exe" to "dosbox_daum_x64.exe". If you have manually replaced "dosbox.exe" since running the version selector, I would advise a clean install of Dosbox. To then use Daum (x64) as the default you would replace the DefaultVersion in the ini file with "Dosbox_daum_x64.exe" (This is the version of Dosbox launched by default from launchbox). To launch a game with another version of Dosbox, from within launchbox; add the executable name without the extension (i.e to launch with 0.74 you would write "dosbox_0.74") to the end of the "Application Command-Line Parameters:", it is likely it will be the only parameter in most cases. It's nice to see someone else using this, let me know how it goes for you.

This is an interesting topic that I would like to give my perspective on. Discs are an obsolete format. Fact. Many people myself included don't even have a disc drive in their computers any more. But thankfully someone has already done the work to make sure these old games don't get lost. All of these games are readily available online if you search around enough. So even if you find yourself losing or destroying all of your discs, you can easily just download them within a few minutes, and these versions will function pretty much identically. This does create a legal grey area with downloading the games (which is unfortunate), but my view is that in general downloading old games is completely fine. What I love about Launchbox is that it allows one to completely digitalize their retro game collection, making these old mediums (most of which are not readable anyway) obsolete, kind of like a customizable version of steam for old games.

Hi, I have written a relatively complex AutoHotkey startup script for epsxe, which will always reset settings back to a default value (in the registry), it is working pretty much fine. My biggest problem is I have had to hard code the config file path as an absolute directory, as I am unsure what directory AutoHotkey works in by default when run through launchbox. Hopefully this is something with a simple(ish) answer. I will be doing a tutorial video over the weekend with how I have set up ePSXe through launch box, which includes the ability to load different games with different shaders, and more. *Edit - More testing shows my Auto HotKey Script isn't working properly at all, when run through launchbox. But it runs just fine from the .ahk file, does launchbox maybe use some limited subset of Auto Hotkey? Basic things like message boxes are even refusing to work for me. *Edit - Ok, from browsing around the AHK functionality in launchbox appears to be very limited (only respond to LB events), so I guess I basically picked up AHK for nothing lol (Never really used it before). However as a suggestion a pre launch custom script (or even executable) option would be useful, right now I've got around it by setting my custom script as the emulator and launching the emulator after running the setup process, though this feels like a hack. An option to just have launchbox run an application before the emulator (for setup scripts, etc.) would be great, and should be rather easy to implement too.

I'm also interested in this, I've been using .pbp's since the PSP days and usually use that format for all my PS1 games, However i've generally found that using the -nogui option (as launchbox does) in epsxe or pcsxr , stops you being able to change disc.

This should work reasonably well. Just put in your Launchbox\Dosbox directory then run it. It is written in AutoIt (My preferred scripting language), I have also included the source code. This lets you choose a default version of DosBox and override it on a per game basis, see the included readme for more information. If you have any problems with it, or suggestions let me know. The reasons for it not working with dosbox-x before, should be apparent from looking at the source code, If you need/want a further explanation let me know. *Edit - A minor problem with this is that it won't allow you to pass any parameters to the application on the dos command line. But I would personally use a batch script for such operations anyway. I might update it in the future with a fix. *Update - Fixed issue with not being able to use command line parameters on the dos command line through Launchbox. The version executable must now contain "dosbox", and the name should always be given as the last (or the only) parameter.

Further Testing tells me launchbox does not rely on the name parameter anyway. I think I see what the problem with dosbox-x is, So I am just going to go ahead and develop this as an addon, to hopefully work with any version of Dosbox, and let you select between them (which was the whole point in this thread anyway). Should hopefully not take more than a few hours to get a functional version.

I was initially thinking the same thing, but then (after a quick look at the dosbox documentation), was able to load a program from the command line without using the name parameter, and instead using a series of -c (command) parameters, so the name parameter is essentially just a shortcut not included in dosbox-x for some unknown reason. I was thinking I might attempt to develop a generic, script based, dosbox version selector solution, which would parse the command line from launchbox, and pass it through to a specified version of dosbox using just the -c parameter. This would also allow for multiple versions of dosbox to be used with launchbox at once. I'll upload a rough version once it's done.

Ok, a little testing shows that is the case, Dosbox-X doesn't seem to accept the name parameter, also agree with you that breaking a command line parameter seems incredibly stupid. However dosbox-x does have the functionality to perform the same action from the menu (Main->Quick Launch), so I'm guessing the parameter was just disabled for one reason or another during development (could simply be an oversight). Sadly all the dosbox-x documentation is unmodified from dosbox 0.74, so no hints to how the syntax may have been changed. I have also decided I am going to buy the premium version of launchbox (forever license), I have been using the free version for about 9 months now, and am blown away with how generally awesome it is. I have never found another emulator frontend so customizable and accommodating, it truly feels like steam for emulators and retro games.

Yeh, The Daum build and latest SVN build work just fine, it's just the DosBox-X builds I can't get working. This is a little bit of an unrelated note, but I just want to point out I am not a noob, and have been using DosBox (and other emulators) for years, and I have a background in Games Development. So if you come back at me with some more technical jargon I will probably understand what you are talking about.

Hi, I've been trying to make Launchbox use the Dosbox-X build (which is still being actively worked on). I've tried just replacing the file, but it just closes dosbox instantly some digging in the stderr.txt suggest's this may be because of physfs, not being supported in this build. My games will run fine with this build if I mount the drive manually and launch them entirely through dosbox, so I'm guessing it has something to do with the way launchbox launches games (through the application path). I think Launchbox is awesome software btw.