Jump to content
LaunchBox Community Forums

alec100_94

Members
 View Profile  See their activity

  • Posts

    227

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Everything posted by alec100_94

  1. alec100_94
    No that shouldn't make a difference, the plugin will just read the path from launchbox. That box should be enabled if the game is on the list above, it essentially just makes a request to that page, does the one game that isn't greyed out download a config?
  2. alec100_94
    No the build of PCSX2 shouldn't matter, seems really strange that it's not working.
  3. alec100_94
    @Gilanth what games are you trying to use the plugin with, only games on this list have remote settings, the rest will have the box greyed out. Can't think of any other reason why it would be greyed out on some games, but not others.
  4. alec100_94
    Don't know, the only thing I can think of is that point is that it might be having problems writing the files, if your Launchbox is in program files or something. Check if the "Use remote settings" box is ticked, unticked, or greyed out as @Zombeaver said. If it greyed out it might be some sort of network problem.
  5. alec100_94
    The new version of the plugin has finally been released as an alpha, and is available to download from the downloads section.
  6. alec100_94
    @Nicodemus The configs should just download and overwrite what's there, but from the image above it looks like your PCSX2 folder is in program files which might prevent the files from writing. You have two options you can either run Launchbox as admin, which should allow the plugin to write to program files, or change the game configs directory to a directory of your choosing that is not in program files (under Tools > PCSX2 Configurator Settings).
  7. alec100_94
    It should be in a sub-directory called "PCSX2 Configurator" (Name doesn't actually matter), inside the Plugins folder. For some reason I forgot to put it in a directory for the current download of the stable version.
  8. alec100_94
    @Nicodemus I think that could be because the plugin may not be in a sub-directory. Now just a general statement about the future of this plugin, I was actively working on a new version (v0.99) about a two months ago, and had a bunch of guys from the forums helping me test it. This version is much better, and pretty much re-designed from the ground up, but I have not got around to working on it recently, and I think it still needs polishing up before I want to release it publicly. Launchbox.Next Support is on my to do list (can be found on my github) and shouldn't be that hard to implement (Although there is a good bit of work to be done there). But there are other more pressing issues with the in-development version of the plugin that will need to be addressed first (So the next release probably won't support LB.Next). This does mean I will be making no further changes to the old version and anything that is straight up broken will remain straight up broken in that version of the plugin. I will try and get a build of the new version released soon, I was personally hoping to have it ready much sooner but work has been quite stressful recently, so I've not been spending much of my free time programming. It appears the first version of this plugin is over a year old now. A lot has changed for me in this time, as well as what my original vision of the plugin was. So I would like to say a big Thank You to anyone that has used the plugin at all at any point. I feel the new version should be at least as good (and hopefully a little better than) the current version, but right now there are still some issues that would cause it to act differently or not work in some scenario's and I need to work through them and test everything thoroughly before I am comfortable releasing publicly. If anyone wants to help test the in-development version, just send me a PM and let me know, but bear in mind it is buggy in places, and not really finished yet.
  9. alec100_94
    @Jason Carr I am the developer of the previously mentioned PCSX2 Plugin, thanks for the heads up about the current directory issue, and thanks to @ckp for finding the issue. I had made the assumption that Directory.GetCurrentDirectory() would always point to the LaunchBox root directory, where that doesn't appear to always be the case in LaunchBox.Next. LaunchBox.Next looks awesome btw, and I cannot wait to see how it progresses.
  10. alec100_94
    @WuTangDan @Zombeaver I personally think Fast and Approximate Anti Aliasing (FXAA), is great and it is usually my preferred method of Anti Aliasing (AA), although it is not always perfect for all games. It definitely beats no AA in most cases and a performance impact of next to nothing, where something like Multi Sampling Anti Aliasing (MSAA) or a brute force AA Method like Super Sampling Anti Aliasing (SSAA) will often tank a games framerate on less powerful hardware. I also think Temporal Anti Aliasing (TAA) is nice, although obviously not applicable to PS2 games. For most PS2 Games (and other games of that era) I would say upping the resolution with no AA is the way to go, which is essentially super sampling, but some (The Getaway being an example) don't scale up too well and still look kind of rough here is where an FXAA pass can do a very good job of cleaning up otherwise ugly image. I kind of agree it shouldn't be on by default though as it is essentially a shader pass, which is very much down to personal preference.
  11. alec100_94
    @WuTangDan That is easily possible and can be achieved in a couple of ways. The most straight forward is perhaps just renaming your memory card to mcd02.ps2, then your memcard will be installed slot 2 for all games and you can copy over whatever save you want to slot one by using configure to open PCSX2 and then choosing to launch without a disc. You can also use an external tool called mymc, or if it's just one game just rename your memory card to that game. Hope that made sense.
  12. alec100_94
    @WuTangDan Try the v0.984-dev build posted further up this page, it might fix the problem with it not being responsive (though will probably still be very small on a 4K screen). The upcoming version will do away with that dialog entirely, but it's not quite ready for release yet.
  13. alec100_94
    @rhydin I think you are a little confused on how to use this plugin. First of all you don't need to download anything except the plugin, That is all taken care of. If you simply want to use profiles for known games, then simply make sure the plugin is installed, right click the game you want to download the profile for and press configure. Then a prompt will come up asking if you want to download the profile for that game (by default profiles are downloaded to PCSX2's inis folder). Then PCSX2 will launch allowing you to tweak settings, you can simply close this window and then start the game from Launchbox. Custom commandline arguments will be added to your game, but you can essentially ignore them, the plugin knows what it is doing.
  14. alec100_94
    @Jwagner82 @rhydin My guess is that something isn't set up properly as that shouldn't be happening. Try giving some more details, about all the steps you go through when setting it up, what game you are using, etc. You may get that behaviour if it is not a known game and use current graphics settings is not ticked (or similar, cannot remember exact name), from the plugins settings menu (From LB's Tools Menu). Also remember that PCSX2 configurator (and all its files), should be in a sub-folder inside the plugins folder. I am also not currently maintaining the old version, in favour of the (currently unreleased), newer version, which I am hoping to get out soon(ish).
  15. alec100_94
    @Rincewind, I think the problem is probably that PCSX2 configurator is not in a sub-folder, inside the plugin directories, and that is partially my fault for not making it clear that it should be. All of the downloaded files should be in a folder called "PCSX2 Configurator" (or similar), inside your Launchbox plugin directory.
  16. alec100_94
    @DOS @spectral I think the plugin was mostly developed round about 7.14-7.16, so I guess 7.10 predates that, so you should definitely update. And you are correct there is no error, which probably means it is not a bug in the code.
  17. alec100_94
    Just as a curiosity thing, try this version. I'll make it stable if it helps you out. PCSX2 Configurator v0.984-dev.zip
  18. alec100_94
    Truthfully I have no idea what the problem is right now. I've personally not had the chance to properly look at any of this stuff in a while.
  19. alec100_94
    @DOS Post a screenshot of the error message that comes up, if there is an option to expand/show more details make sure that is done before capturing it. @neil9000 I don't see any reason why having a zipped file in the plugin directory would cause launchbox to crash.
  20. alec100_94
    I highly doubt it is due to any of the two previous suggestions if it is causing launchbox to crash. Post a screenshot of the error message (showing details), and I'll try and tell you what's wrong. Just as a heads up I apologize to never getting around to finishing my final release of this plugin, and cannot say when it'll be done. Stay tuned for more details.
  21. alec100_94
    Ok, this is old, I was eventually planning to write a plugin based version (actually started on it), but that project has been shelved for now. As the original links are down (presumably due to a forum upgrade) I will re-up it, though this comes with absolutely no warranty, or extended support/updates. This is a debug build, so it has a message box with information/parameters in it. If anyone knows what they are doing feel free to change the code, but I will be making no further changes to this program. From memory to get it up and running you have to run the .exe from an unmodified dosbox directory in Launchbox, just ignore the .au3 if you don't know what it is. Dosbox Version Selector.zip
  22. alec100_94
    @Hellzknight666 I think I know what is wrong here, the plugin and all its contents should be in a sub folder called "PCSX2 Configurator". Sorry if that wasn't made clear.
  23. alec100_94
    @Hexical Seems really odd why nothing would be happening then.
  24. alec100_94
    @Hexical Post a screenshot of your LaunchBox Plugins Folder.
  25. alec100_94
    @Hexical I'm going to need a few more details than that. The only real reason I can think to why PCSX2 may not open is if my plugin cannot find it, so is PCSX2 added as an emulator in Launchbox?
×
×
  • Create New...