pcsx2 Zombeaver's PCSX2 Configs / Simple 1-Click Installs With PCSX2 Configurator

[alec100_94]

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.

[Cineaste]

@alec100_94 thanks for the explanation although it appears it doesn’t affect everyone equally. 

@Zombeaver and I have both upgraded to the latest LB release (10.14) and find our plugins working as intended without making any changes. How come? I can confirm that 7-Zip has indeed moved to a ThirdParty folder but that doesn’t seem to bother the plugin. 

Edited April 23, 2020 by Thornback

[Zombeaver]

Just FYI I am in the process of working on these again. I'm at 208 / 85%. I would have more done but as part of the process I'm also going back and reverifying that previously updated configs are still working correctly in dev-3400 (the update process has spanned about 3 different versions at this point). So far no issues in that regard, but I want to double check them all just to be sure.

Happy to say that Kya: Dark Lineage and Burnout 3 issues status moved from yellow to green in tonight's updates.

[Cineaste]

Someone's mentioned a stable 1.6.0 release in the not too distant future (possibly this year). I hope this won't reset your progress?

[Zombeaver]

It shouldn't. The release candidate for 1.6.0 is from 3/23. Dev-3400 is from 3/27. There have only been 3 revisions since 3400 all of which are minor and shouldn't have any impact on existing configs.

[Ashen]

The fixed .dll in the linked to thread fixed my issues. Thank you

[Zombeaver]

220 / 90%

[Zombeaver]

Just a bit of an aside here, but I've been playing around with Reshade a lot lately. I decided to try it out with PCSX2 tonight. Still fiddling but I like it quite a bit at the moment.

Normal:

Reshade:

Normal:

Reshade:

Normal:

Reshade:

Normal:

Reshade:

[Zombeaver]

Alright boys and girls. 244 / 100% complete. At this point I'm just doing a sweep of the configs that were updated on slightly older versions to make sure they're still working as expected (no issues so far, and I don't anticipate any) which is a pretty quick process. After that, I just have to cleanup the documentation a little bit - I've made it a point to add a lot of notes for everything in the game details spreadsheet to help clarify what everything does for each game, and I have a few more minor things to add here and there. Then I just have to push them all through to github. So we're in the home stretch now. The Google Doc that I have for the changelog is 16 pages. FML.

I also became mildly obsessed with the Reshade thing for a hot minute there...

[Cineaste]

I'm getting excited now - can't wait for the new configs. Thanks for your efforts so far.

[Zombeaver]

As an additional step of this final pass, I'm adding a new column to my spreadsheet that's to catalog the average speed that I'm getting with the framelimiter disabled. This is a good guide as to how much potential wiggle room there is and can help inform the decisions I make on things like upscaling values. I don't, for example, want to increase the upscaling from say 4x to 6x if I'm getting about 250% speed at 4x and about 115% at 6x, because then there's very little wiggle room and if someone has a little bit worse hardware than me they might end up seeing slowdown (or even I might see it in unusually heavy scenes in the game). It also helps me see which games are more CPU-limited than GPU-limited, in which case adjusting the scaling values often has little impact on performance one way or the other. Quite a few of the games had their scaling values increased during the update process (by 1-2x) primarily because of the removal of MSAA support - the combination of increased scaling and the addition of FXAA in many cases is generally a replacement or improvement in the end - and I thought it prudent that I double check myself on these values to make sure I'm not making things more taxing than they need to be. I just don't want people to update and see worse performance than they had before, basically.

This means it's going to take me a little bit longer, but I don't think it'll be too bad. Probably talking a couple days.

[Zombeaver]

Just to give another update, I've performed the final pass/benchmark check on 100 games (41%) so far, so it's still got a little ways to go. That's in part because a couple days last week I didn't have much time to work on this at all. I got 50 of the 100 done in one day, to give you some idea. I'm hopeful this won't take a whole lot longer, and it shouldn't so long as I can just knuckle down and keep working away at it. I will say that I think this extra measure will be worth it in the end because I've made a few changes here and there based on the test results. I've also fixed a few more things along the way, so that's an added bonus.

[Cineaste]

Very nice, almost there!

So will you be replacing the Google doc with updated configs once everything is set and done on your end?

[Zombeaver]

Yep, I've got my own copy that I've been updating. I'm not going to update the public one until they're pushed through because it wouldn't be accurate with the current configs on Github.

[Zombeaver]

Another quick update - 160 / 66% on the final pass. Tweaked a few numbers here and there, disabled large framebuffer and enabled MTVU in a few cases. It's easier to see when that's really beneficial with the framelimiter off. I also fixed a few more things along the way.

[deathsycthe420]

Will the configurator still work with PCSX2 16.0 or am i better off just sticking to the dev builds for now?

[alec100_94]

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.

[Zombeaver]

Well, the timing mostly works out because I'm almost done. 194 / 80% right now. I'm hoping to have the rest done in the next day or two.

Once that's done the only thing I have to do is throw up a couple updated configs on Github and verify that everything is being pulled through correctly. It should, but some of the parameter names/verbiage in the .inis has changed a little bit since the current configs so I want to make sure. As long as that's working as expected I'll push them all through.

[Cypher]

13 hours ago, deathsycthe420 said:

Will the configurator still work with PCSX2 16.0 or am i better off just sticking to the dev builds for now?

I just tried it with 1.6 & 1.7 dev and the tool stopped working. Even reverted back to 1.5 and tried reinstalling the plugin and it doesn't work anymore.

I wouldn't risk it, personally.

Edited May 7, 2020 by Cypher

[Zombeaver]

5 minutes ago, Cypher said:

I just tried it with 1.6 & 1.7 dev and the tool stopped working. Even reverted back to 1.5 and tried reinstalling the plugin and it doesn't work anymore.

I wouldn't risk it, personally.

You're probably using the wrong version of the plugin.

Try this one.

@alec100_94 Please add the hotfixed version directly to the download page, otherwise this is going to continue to be problem. Just add it as a separate file. You can have both available from the same download. People shouldn't have to find a comment and go to Github to get it.