XoRRoX

I'm all for decreasing the amount of different connectors. But if we look at versatile uses of the 3.5mm jack, ending up in devices in pockets, etc. I foresee some problems with that the usb connector is a bit short and not round and so less rigid.

hydro Setting up and running emulators with their configurations is not really for the faint of heart, really technical and requires you to spend quite some time educating yourself. It's not a "Next, Next, Finish, Run, Play" kind of thing, most of the time. There are a lot of communities with forums etc. with people that want to give pointers, though. But it is not likely that someone will connect with Teamviewer and set it up for you. Because that shows that you didn't put enough time into it to try to understand certain things and it, in a way, becomes the responsibility of someone else, instead of your own. Like SentaiBrad mentioned earlier, he made quite an extensive and comprehensive collection of videos showing how to set LaunchBox up for a wide range of systems/emulators. You could start by watching the ones pertaining the system you'd like to set up and take it from there. You can find them here: https://www.youtube.com/channel/UCSIht6UXIEXIgz4eXAEShxA/videos?view=0&shelf_id=1&sort=dd

Are these answers/suggestions disguised as questions? While this scenario might not seem likely to occur for others, I'm giving feedback and details of when and how this occurs so it can be assessed to what extend it can possibly lead to issues for other users. Without that, I think you are jumping to conclusions in an actually quite unpleasant manner.

Jason Carr said Sounds like it's competing with the Controller Automation features. So turning off controller automation should stop that, I think. I don't think it's on by default (it's a premium only feature). Can you confirm that? Hmm, did some testing and discovered what happens - quite funky really :) I don't know if this makes sense to you and how likely it is to cause other problems with other users, but I leave that up to you ;) I have a PS2-style joystick which can be switched between Digital and Anolog use of the D-Pad. When I do this: 1. Joystick to digital; select title with the arrow that appears; button 1 (confirm) => Starts selected title 2. Exit game 3. Switch joystick to analog; select another title; Hold button (7 or 8 or 9 or 10); button 1 => Jumps to title selected in 1. and starts that one. In fact, after I selected any title in Digital-mode, any title I select (try to) confirm while holding down another button in Analog-mode, the previous title selected in Digital-mode always gets selected.. As the coder, could be that this makes sense to you of course :) If my description is not clear or anything, if needed I could record a video.

Jason, Adding the possibility to pass the configured rom-file (either with or without the extension) to the dialog of the Additional Apps could provide great(er) flexibility. Then people can pick that up in whatever tool/batch-file they want to run before or after.

Hi @Jason Well, LaunchBox has focus at the moment I select and confirm a title (which doesn't launch the "title" but my in-between launcher with the title as a parameter.) When I only press the Confirm button (1), all's well. But when I hold, for example, button 9 or 10 and then press button 1, it jumps to the 1st title in the list and confirms that one.

@Jason Car I'm running into quite some trouble when trying to use some of the joystick keys to trigger things in LaunchBoxPCSX2. By default they almost all seem to be configured in LB and effectively unusable for my app. Even ones that are not configured according to the LB dialogs, 9 & 10, make LB jump back to the first title in the list when held down and button 1 ("Click / Enter / Confirm") is pressed to confirm /and thus start LaunchBoxPCSX2). Now, I can understand that you cannot take any tool out there into account. Would it be possible though to have your thoughts on this? For instance to at least let the not configured ones do nothing? Thanks in advance :)

You can also have a look at a small app I created for this called LaunchBoxPCSX2 @ https://www.launchbox-app.com/forum/features/launchboxpcsx2-an-in-between-launcher-for-launchbox-and-pcsx2 You can chose per game to let it use a Generic Config (for games that don't need special settings) or a Game-Specific Config. It also features Saving and Loading of savestates and exiting pcsx2 by joystick. The current version only works with the pcsx2 setup where the configuration files are not in the Documents folder (the so-called "portable" setup) but I am hoping to release an updated version soon with which either setup is possible.

Sorry, I was too busy too finish up the next release which takes the possibility of the Documents folder into account but I hope to free some time for it soon. Thanks for checking it out :)

Jason Carr said You mean our site? Nah, they have people that review this stuff. That's seriously some people's jobs. As it seems then that person isn't quite good at it anyway ;) And then to think there are even emulators in the App Store and Google Play which should give PayPal a clue..

SentaiBrad said You've always been able to have your files in your documents folder or your PCSX2 folder. However, only savestates, memory cards, BIOS and logs can be in your PCSX2 install. It looks like ini's need to be in the ini 1.4.0 folder for the new 1.4.0 version. You might not have file permission so PCSX2 can't access it, otherwise try removing all installs of PCSX2 (keep your memory cards and save states if you have any) and install PCSX2 fresh. See if it boots after this. Hmm, good to know - thanks for providing these insights :) Alakazander is referring to a LaunchBoxPCSX2 error message and not PCSX2 itself not starting, so no need to do a fresh install of PCSX2 At this moment LaunchBoxPCSX2 is coded to look only check for {PCSX2 Folder}\inis and not in the Documents folder (as Alakazander seems to have configured it) so I have to build that in too. Thanks again for the info though

Alakazander said Hey man, this app looks sweet but I'm having an issue with it. When I tried to make a Game-Specific Configuration I got this error: I looked at C:\Users\***\Documents\PCSX2 and found that I had a folder called "inis", but that the new version of PCSX2 had made a new folder called "inis_1.4.0". So I thought I'd just copy and replace the files from "inis_1.4.0" into "inis", but I got the same error message again. Is there something that I am doing wrong? I heard today (after the release) that with the new 1.4.0 release you can choose between having certain folders in either the PCSX2 folder or your Documents folder. The latter you seem to have chosen. The current release v0.03b of LaunchBoxPCSX2 doesn't anticipate on that yet and only assumes the old situation where the \inis folder is a subfolder of the PCSX2 program folder. I'll have to investigate the new possibility and make changes to accommodate for that.

I updated LaunchBoxPCSX2 to version 0.03b. -= Changelog =- +Added: The Joystick Buttons are now configurable in an ini-file (LaunchBoxPCSX2.ini) +Added: Display of various notification messages (non-essential) can now be toggled in an ini-file +Added: Feedback sounds can now be toggled in an ini-file / Fix: Not all PCSX windows were closed when --nogui was being specified as a command line option in LaunchBox. I updated both the text and attachment in the first post (thanks again @Jason Carr ) Looking forward to your feedback

Jason Carr said Thanks @sagaopc. I can't find a license to see if it'd be legal to include AutoIt with LaunchBox. Hi Jason, I don't use AutoIt (yet) but found their license here: https://www.autoitscript.com/autoit3/docs/license.htm I myself am looking at ways to close PCSX2 reliably with all different Fullscreen and Nogui parameters and will update you soon with it so you can include it in LaunchBox if you want. Mike

Thanks for this list. For completeness sake, I'd like to remark that currently PCSX2 besides iso, mdf, nrg, bin also supports img, dump, gz, cso. (gz with the highest compression by the way). ePSXe supports bin, iso, img, cue, ccd, mds, pbp and ecm. Cheers.

Zombeaver said This is a really great idea! I'll have to check this out as it should cut down setup time quite a bit. I've just been setting up each game with PCSX2's master config files until I'm happy with them and then copy them into the specific game's folder and then add a launch command to the game to direct it to those configs via -c "config folder location". Well, that's basically what happens behind the scenes. In addition I added some Joystick features. Looking forward to your feedback :)

Hi all, I recently started experimenting with LaunchBox and PCSX2. I developed a small program to cater from some things I wanted. When I mentioned it on Reddit, there seemed to be interest for it so I thought to share it. Here is the Readme: -= App Name =- LaunchBoxPCSX2 -= Features =- This Launcher is meant to be used in conjunction with LaunchBox and PCSX2, the PlayStation 2 Emulator. It has two main functions: 1. Enable Game-Specific Configuration in PCSX2: > Hold down Shift or Joystick Button 7 (L2 on my PS2 Joystick) while launching a game in LaunchBox to create a Game-Specific Configuration for that game. Any option you change will be configured specifically for this game only. The next time you want to launch this game, there's no need to hold Shift or joystick button - LaunchBoxPCSX2 will detect the Game-Specific Configuration and use it automatically. > Hold down Control or Joystick Button 8 (R2 on my PS2 Joystick) while launching a game to DELETE the Game Specific Configuration. The next times the game is launched, the Generic Configuration will be used. 2. Enable Save & Loading Game States and Exiting PCSX2 with a Joystick/Gamepad: > Save State by pressing button 9 (Select on my PS2 Joystick) + 7 (L2 on my PS2 Joystick) - Effectively presses the F1 key. > Load State by pressing button 9 (Select on my PS2 Joystick) + 8 (R2 on my PS2 Joystick) - Effectively presses the F3 key. > Exit PCSX2 by pressing button 9 (Select on my PS2 Joystick) + 0 (Triangle on my PS2 Joystick) - Without Confirmation. -= Installation =- - Place this launcher in the same folder as PCSX2.exe; - Open LaunchBox and specify LaunchBoxPCSX2.exe as your "emulator", instead of PCSX2.exe. If preferred, you can specify additional commandline parameters you want to pass to PCSX2 in LaunchBox too (ie --nogui --fullscreen). -= Notes =- . The configuration of all Joystick Buttons, several notification messages (non-essential) and sound feedback is configurable in the LaunchBoxPCSX2.ini file. . You can use the separately included JoystickTest.exe to find out your joystick's button numbers. . To any y/n in dialogues you can also respond with your joystick - Joystick button 3 for Yes, Joystick button 1 for No. . If you want to configure the Generic Configuration, you can start any game which doesn't have a Game-Specific Configuration or start PSCX2 manually and configure the options. Be mindful though that those options will not trickle through to your Game-Specific Configurations. . Game-Specific Configuration is based on the name of the game's image filename. This means that if you first create a Game-Specific Configuration and then rename your image file, LaunchBoxPCSX2 will not detect it anymore. The easiest way to solve this is to go into the {PCSX2 installation folder}\Game Configs folder and rename the corresponding folder to match the name of your image file. . You can start LaunchBoxPCSX2.exe from Windows Explorer to show it's version number. Have fun, XoRRoX -= Changelog =- - v0.01b First Release - v0.02b (not released) / Fix: made file extension of game file recognition not case-sensitive (it used to detect only lowercase extensions) - v0.03b +Added: The Joystick Buttons are now configurable in an ini-file +Added: Display of various notification messages (non-essential) can now be toggled in an ini-file +Added: Feedback sounds can now be toggled in an ini-file / Fix: Not all PCSX windows were closed when --nogui was being specified as a command line option in LaunchBox. - v0.03c +Added: Debug logging to see what command-line parameters are passed. Documents\LaunchBoxPCSX2_Log.txt. To activate, in the ini-file, under [Other] specify debug=true or debug=1 - v0.03d +Added: Some additional command-line debug logging. / Fix: On pressing Esc, PCSX2 would only close the game but not completely exit. - v0.05 / Change: Changed the method with which the game-file parameter is detected because someone ("timekills") wants to use it with RocketLauncher which passes it as the first parameter, not the last as LaunchBox does. The game-file can now be specified in any position and LaunchBoxPCSX2 will detect it automatically. - v0.05b / Fix: (again) Not all PCSX2 windows closing when --nogui was specified. Tested with latest PCSX2 developer build 1.5.0-dev-2479-g39b405648-windows-x86. / Fix: LaunchBoxPCSX2 not closing sometimes. +Added: a configuration option in the Ini to use the Joystick functions or not. LaunchBoxPCSX2_v0.05b.zip