XoRRoX

@tomolrs Glad to see it's still useful 🙂

Glad that you're finding it useful ? I didn't gave it much attention anymore as I understood that there was a plugin with the same purpose (didn't keep track of it though). Also, my current situation changed quite drastically and have next to no time for hobby anymore. Is there something not working as it should, or do you have a special need for a function?

? You're most welcome

Great. Happy to have helped

Hi all, First I want to say I'm very sorry not having been able to maintain this. Life changed quite a bit back then (in a positive sense). Thanks for all your interest in this. I dug up the old code and I think the issues people ( @Klamp @rotatorkuf @firion @LuismaSP89 ) were experiencing are now fixed. I also added an option (requested by @StuDentBR) to disable the joystick functions. You can download it in the first post. If there's anything please let me know. My time for this kind of things is still very limited so I can't make any promises (I hate false promises) to fix it in a short while. Cheers.

I'll have to look into it. I'll let you know, okay?

Hope you'll find it useful. I'll be happy to receive any feedback.

Thanks for asking - it means I wasn't clear enough to explain its purpose in the first place In PCSX2 there's functionality to have a different configuration file for certain games. You have to copy the ini-files, then specify to use that config on the command-line. I thought that it would be handier to automate that. By using LaunchboxPCSX2, you can let it create a game-specific ini-files by pressing a joystick or keyboard combo. Next time you start the game, it detects that there is a game-specific config file and uses that automatically. After that, in PCSX2 you can change whatever config option you want - effectively it will only affect that specific game. Next time it will use that game-specific config again. If no game-specific config is found when starting a game, it'll start PCSX2 with the generic config. LaunchboxPCSX2 also provides the option to delete the game-specific config again - in case you want to use the generic config again, for whatever reason. As an extra, you can save and load states with a joystick combo in PCSX2. Hope this clarifies it sufficiently. If not, feel free to ask

Yes, if you have the premium version of LaunchBox. Although it's not its main purpose (I just put it in 'cause I don't have premium). LaunchBoxPCSX2's main purpose is on-demand per-game configuration of PCSX2 settings and save-states by joystick.

LaunchBoxPCSX2 features per-game configuration (optional per game) and PCSX2 save-states and quiting the emu by pressing a combination of joystick buttons.

In one of the developer sessions I attended, Jason mentioned voice control not working in the UK version of windows and was trying to fix it. So, he's aware of it but I don't know the progress, if any.

Cool If you like, let me know your thoughts on using it. I really have to upgrade a few things but wasn't able to finish yet in the little spare time I had the recent period But, also according to feedback, I can see what I can do in the future.

Well, I only going to need logs if it doesn't work But if you can post your findings, that would be great ?

@timekills I uploaded an updated version which automatically scans all passed parameters to see if its the game-file, making it position independent. This way it will also work with RocketLauncher. I had a quick go with RL but could you please test it with your setup?

@timekills Did some more investigations. I installed RocketLauncher and set up LaunchBoxPCSX2 with the PCSX2 module. I enabled RL's debug function and it wrote: [code] 20:38:51:329 | RL | INFO | +N/A | Main - RocketLauncher v1.1.1.1 (www.rlauncher.com) 20:38:51:329 | RL | WARNING | +0 | Main - Logging level is debug or higher and will cause slowdowns to RocketLauncher's performance. When troubleshooting is finished, please lower logging level to restore proper performance. D:\Games\Emu\PS2\PCSX2>LaunchBoxPCSX2.exe "G:\Games\Emu\Roms\PS2\Okami\Okami.iso" --fullscreen --cfgpath="G:\Games\Emu\Sony\PS2\PCSX2\Game Configs\Okami" 1>"G:\Games\Front-Ends\RocketLauncher\command_1_output.log" 2>"G:\Games\Front-Ends\RocketLauncher\command_1_error.log" This confirms what I already suspected, also from the first log you posted - RL doesn't specify the game-file as the last item. I have to look further into it to see if something can be done to make it work, either in RL or that I have to change something in LaunchBoxPCSX2. I'll get back later.

@timekills Hmm, that log is not really helpful, is it? According to the RL error msg, I suspect RL doing something 'intelligent' other than just starting any exe, as the ahk_class wxWindowNR is one of the PCSX2 windows. But, I extended the logging to show everything passed now. You can overwrite your current LaunchBoxPCSX2.exe with the one from the updated package in the 1st post. Could delete the current log, have another go and post the log again?

@timekills I added some basic logging to see what command-line parameters are passed; you can download v0.03c in the first post. You can either use the new included LaunchBoxPCSX2.ini and change the debug option from false to true or copy & paste the section below to your existing ini-file. [Other] ; Toggle debug messages being written to My Documents\LaunchBoxPCSX2_Log.txt (0 / false = off, 1 / true = on) Debug=true After that, start a game as normal. A file named LaunchBoxPCSX2_Log.txt will be created in your default Windows Documents folder. After that you can post the file here again. Don't forget to turn off the option again after you're finished debugging

Hmm, thanks for posting the logs. Although, I couldn't find anything useful from the logs. I'll create a new version of LaunchboxPCSX2 that will log the passed parameters by itself for you. I'll try to do that tomorrow and post, okay?

I don't have RocketLauncher myself and I don't know if the RocketLauncher log file will provide enough info but could you try? I found directions on how to enable RL debug logging @ http://www.rlauncher.com/wiki/index.php?title=RocketLauncher_Troubleshooting If you don't want to fiddle around yourself, just say so and I'll set something up over here, okay?

Styphelus said This is a question for our friend Frank, former PCSX2 developer! What is? :)

Chris said Just wanted to say thank you for this. It works great and it made playing my PS2 games so much easier! Thank you Chris - happy you find it useful and helps you :)

jt_3o5 said how do you do this i created a new thread before i saw this...... where do i put the command line argument i.e. --cfgpath="C:\Games\PCSX2 configs\FFX-inis" With LaunchBoxPCSX2 you don't need to do that anymore - you can have it create per-game configuration files for you. Else, if you want to do it manually, you need to put the --cfgpath parameter in Edit Game/Emulation/Use Custom Command-Line Parameters. You need to do this for every game separately though. ...that's why I created LaunchBoxPCSX2. You need just one emulator profile. By default, if there is no Game-Specific Configuration, it will use the PCSX2 Generic Configuration. If you let it create a Game-Specific Configuration, it will copy the Generic Configuration as a base (so you don't have to setup things from scratch). You can then do your configuration for that game in PCSX2. The next time you launch it, it will detect that GSC and use it. ;)

I'd just like to add that "PC" got renamed to "Windows" so that there's now "DOS" & "Windows".

Kristijan1001 is there a specific reason you want to keep the .cue files? And did you test to see if there's any/much size difference between the .7z and .cso (compressed iso)? If there's no need for the .cue files, you could unpack your files, delete the .cue files and repack to cso files. Like Brad said, that would also reduce the loading times (for unpacking your 7z) because PCSX2 can read the cso directly.

Jason Carr said Hi @XoRRoX, this sounds like an odd issue that is probably related to your specific controller. What model of controller are you using? Apologies if that's further up in the thread. Unfortunately nothing is really making sense as to why any of that would be happening, based on your description. A video might help, but it's still probably going to be hard to follow without the controller in hand. Unfortunately this is probably gonna be a situation where the only way I'll be able to fix it is if I actually have that particular controller. Thanks. You knowing the code, if you don't foresee it potentially causing problems or confusion for others using a switchable analog/digital joystick, it's not that important. My intention was more to provide you with info to assess this than it's a problem for me personally per se. I can confirm that the Controller Automation feature is indeed off for non-premium users.