Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

  • Days Won


alec100_94 last won the day on May 28 2017

alec100_94 had the most liked content!

Community Reputation

157 Excellent


About alec100_94

  • Rank
    32-Bit GPU

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Github was broken temporarily, its working again now. I'll upload the hotfix to the initial post as a mirror.
  2. First of all I would like to congratulate the PCSX2 team on the long awaited 1.6.0 stable release, and all of the hard work that was put into it. @deathsycthe420 This tool should work fine with the new build, as there is very little difference between it and the latest 1.5.0 Dev builds. A new (and much nicer) solution is in development for going forward, I was initially hoping to get out ahead of the 1.6.0 release but I guess that didn't happen. Just continue to watch this space.
  3. @Retroid84 It will be done when it's done, it could be a few months away (hopefully a bit sooner). There is no harm using the old plugin, you should be able to copy all your configs right over when the new solution is ready. I just wanted to make it clear that I won't be updating this any further, it should still work in the same manner as it did before.
  4. Just to clarify the reason the plugin needs 7zip is to extract a memory card file (truthfully could have probably just been a zip). The reason it broke was because the 7-Zip folder in the Launchbox directory was moved to ThirdParty\\7-Zip. Fixes would be to either make a directory junction or copy the 7-Zip folder to the root of the launchbox directory, or download the recently released hotfix for the plugin (compiled by @mitchhawks) which points to the new directory, that can be found on my github here.
  5. Am I right in thinking that @mitchhawks build works, and I don't need to do another build? That build is hosted on my github here. https://github.com/roguesaloon/launchbox-plugin_pcsx2-configurator-next/releases/tag/b2h1 @tycho1974 The 1.5.0 dev builds generally work fine, not sure what your issue is, but we are also quite close to a stable 1.6.0 pcsx2 release (probably within the next few months)
  6. @everyone I just want to make a general statement as this seems to have turned into a very negative place. As far as I am aware the plugin does still work with more recent versions of Launchbox. I'd put any scenarios where it doesn't work down to user error. There is an issue with the latest version of Launchbox as the 7-Zip directory has been moved, which I will put out a fix to resolve tomorrow. And then I'll test it to verify that it's working for me. That is very likely to be the final update for this plugin. However I want to point out this plugin hasn't been updated in over 18 months and I don't intend to do the work to update it either. There is a new solution in the pipeline and I will be putting all future development efforts towards that (can't give an ETA yet). Coming here looking for technical support is one thing, coming here to complain that my plugin is straight up broken when it works for others and expecting me to drop everything and "fix" it is quite another.
  7. @neil9000 @tycho1974 not necessarily an issue with window, there was a change to one of the paths (the drawing DLL) in the zip above from @mitchhawks. I didn't actually test the resulting DLL. I'll investigate (and fix it) tomorrow.
  8. @mitchhawks thank you for providing a fix, I'll throw that up on GitHub when I finish work. My solution would have been simply creating a directory junction (or even more lazily just copy the 7Zip folder) in Windows to get around the issue for now. In terms of the future and updates for pcsx2 configurator there is something new in the works, and that's all i'm going to say on the matter for now.
  9. @RobertBlum It's no secret that I am not really working on this at the moment, but as you asked a sensible question I'll give you an answer. Basically it disables the presets in PCSX2 when creating a new configuration with the tool and allows you to customise the use of Game Fixes and Speed Hacks. I mostly put it in for @Zombeaver to make his workflow easier when making new configs, if you know what your doing and making your own configs feel free to enable it.
  10. @qupe75 I'm sure I had Okami running pretty well under PCSX2 before, can't remember the exact settings though. My honest recommendation would be to get Okami HD for PC, and play that, as it's clearly the definitive version of the game.
  11. @Kobe34 Not many people use that feature, I almost forgot it existed, but it should be in the games config folder along with the other config files for the game (in pcsx2's inis folder by default). If you want to apply the command-line option for all games you can just add it through launchbox.
  12. @Funkenstein, @Zombeaver recently had a similar problem, it was the path to MemoryCards in the base PCSX2 config file. so in PCSX2_ui.ini (under {%PCSX2_DIR%}\inis) the MemoryCards Folder is relative to PCSX2's path, or a full absolute path with a root (drive letter). So it should probably just be memcards as shown below. Hopefully that fixes it.
  13. @EazyCheeze1978 Not been round here in a while, but I had this idea a while ago, and totally see where you're coming from. My idea was more to run LaunchBox as a background service, more akin to steam, and potentially have LaunchBox shortcuts use their own protocol. However I never even got around to prototyping that one due to a bunch of other LaunchBox plugin ideas that might be more useful. I am currently working on something LaunchBox related, that is really exciting and should eventually be awesome, but it is not this.
  14. Hello to everyone, I realise I don't really post here regularly and generally offer rather crappy tech support for my PCSX2 plugin. The main reason for this is because it is generally extremely difficult to be able to tell what is wrong with the (usually) limited information given or even just an error message, and 9/10 times it is a user error and not an actual issue with the plugin itself. I really need to be able to see the issue properly to be able to fix it. Because of this I am going to invite anyone requiring tech support to contact me through discord (you can find me on the LaunchBox channel same name as on the forums), and we'll deal with it on a case by case basis possible involving screen sharing and/or the use of chrome remote desktop. As for development on the plugin itself, it has been on a bit of a hiatus, with very little work being done on it since the last release, however I am looking to resume work on the plugin relatively soon, and hope to implement a more practical system for handling user errors, and tracking the most commonly occurring issues. -Alec
  15. @sersoft2008 based on the information that has been posted, I still don't have any idea as to what could be wrong. As far as i can see everything looks right. Am I right in thinking that after clicking "PCSX2 Configurator" from the context menu that nothing happens?
  • Create New...