Zombeaver

The new plugin is out now! Check it out here! Thanks to @alec100_94 for all his hard work on this! To celebrate the new release, I've got 25 new configs and 8 updated ones to check out: Updated: Wild Arms: Alter Code F -changed deinterlacing from Auto to Bob tff (sharpness improvement) -removed software FMV option (removes jitter caused by Bob tff in cutscenes) Wild Arms 3 -changed deinterlacing from Auto to Bob tff (sharpness improvement) -removed software FMV option (removes jitter caused by Bob tff in cutscenes) -audio changed to Async in SPU (helps mitigate brief moments of slowdown) Wild Arms 4 and 5 -removed software FMV option (unnecessary) Armored Core 2, 2: Another Age, 3, and Silent Line -changed deinterlacing from Auto to Bob tff (sharpness improvement) New: Alone in the Dark Alone in the Dark: The New Nightmare Amplitude Battle Assault 3 Beat Down: Fists of Vengeance Blood Omen 2: The Legacy of Kain Bloody Roar 4 Breath of Fire: Dragon Quarter Chulip Cyber Troopers: Virtual-On Marz Dawn of Mana Forgotten Realms: Demon Stone Frequency Gauntlet: Dark Legacy Gauntlet: Seven Sorrows Global Defence Force Jaws Unleashed Mortal Kombat: Armageddon Mortal Kombat: Deception MotoGP 08 Neo Contra Orphen: Scion of Sorcery Resident Evil: Outbreak - File #2 Star Wars: Racer Revenge Street Fighter EX3 As always, details for each of these are available on the config spreadsheet. An important note about Amplitude - you must use the --fullboot command-line parameter in order for the game to load properly. The ability for me to inject custom command-line parameters into specific game configs (so that you wouldn't have to do anything in this situation) is planned but is not yet implemented. Because of this, you'll need to add it manually. Once the config is downloaded, just right-click and edit the game and add the --fullboot parameter before --cfgpath and you'll be all set.

New comments should be directed to the new plugin thread. I'm locking this one.

I don't know of one off-hand but somebody's probably come up with something for that. You might want to try asking on the AHK forums. If you come up with something, you could add it as an additional app to start "before main application" and another one to turn it off afterwards.

Yeah I know, I'm just saying I don't understand why. As I said, these do nothing in their native .nib format in all major C64 emulators (they "work" natively in this format in micro64, but most will end up still being unusable from copy protection), and even if you go to the trouble of converting them to g64 format with nibtools, the majority of them still won't work due to copy protection. They are not intended to be used in emulators. Most of the time when they get mentioned it's combined with an understandably confused "What am I supposed to do with these?", to which I can only say "Get rid of them and grab the Gamebase64 set." No Intro and TOSEC are both terrible for C64. TOSEC at least has usable formats, but it often has 5 or 6 dumps for every game and 50%+ of those are bad dumps, so it's a giant mess.

Commodore 64 (PP) is for "preservation project" - which are .nib files. They're really not designed to be used for emulation (I have no idea why those are so commonly distributed) - they do nothing with most C64 emulators, and even if you convert them into an emulator-usable format, most of them still won't work anyway from copy protection. The C64 Preservation Project was designed to catalog C64 games in their original form (including copy protection) and facilitate the creation of new disks (as in, actual 5 1/4 floppy disks) with additional tools they released. It's not a separate platform (it's just Commodore 64) and it's not something you can really even use with emulators. Commodore 64 (Tapes) is literally just another format some games came in (for the same system). Commodore 64 had tapes, cartridges, and disks. It's not something separate, it's still just Commodore 64. (cartridges plugged directly into the back of the C64)

Synnergist has now been added to Zomb's Lair.

This isn't really a LB question, to be honest. You'd be better off asking on the PCSX2 forums. I don't really know what to tell you (savestates work fine for me) other than... maybe just don't use save states. Using in-game saves should work fine.

Okay, that's fine. None of that has anything to do with my statement. Software + Reshade does not and will never equal 4x+ internal resolution, period. They're fundamentally different things. If you have anything actually relevant to this thread that you'd like to contribute, feel free to do so, but I don't want the thread clogged up with Tom's Hardware posts please. Thanks.

Because Reshade isn't actually upscaling anything. It's literally applying a filter/shader on top. That's not even remotely close to the same thing as running the game at a higher native resolution, and will never look anywhere close to as good. It's like saying "Well why not just throw some paint on my CRT screen - that'll make it just as good as an HD TV." No, it won't. Software mode + Reshade will never look as good as a 4k internal resolution. I have a 4770k. There's nothing wrong with your CPU.

That sounds like it may be an actual bug then. @Jason Carr you might want to take a look.

Probably a good call.

I don't know. But 1.5.0 is at everyone's disposal and has been for quite some time. https://pcsx2.net/download/development.html Except that, as we've already established, it's been in the testing phase for literally two+ years. You're not going to break anything. I've probably already setup whatever game you want to use with it for you. Except that's not going to provide some kind of miraculous benefit in its current state. x64 doesn't just magically make everything better, despite what you seem to think. PCSX2 certainly has issues (primarily on the accuracy front), but they're not going to be resolved simply by slapping x64 in there. If you'd like to make it better though, feel free to contribute. It's open source after all. This is true. It could certainly be better. It's also not the end of the world. You can choose different video drivers to use in Retroarch too. You download different, individual cores that are separately maintained/updated too. That doesn't suddenly make Retroarch garbage. Most of this was just rambling blather about things that you clearly don't know anything about, want to sound like you know something about, and then proceed to get faux-angry about things that you don't know anything about but want to sound like you do. No one cares. Take that shit back to /r/emulation. I'm sure you'll fit right in. We don't have flying cars yet either, that doesn't stop me from driving to work in my sad little ground car. You can either use the tools that are at your disposal and are actually fairly sufficient, or you can complain until you're in the grave about how much better things "could be", while contributing nothing to that end no less. You seem to have this idea in your head that the people contributing to the development of PCSX2 are some kind of reprehensible conclave of lazy idiots. They're just people spending their time, using their skills, for free... for you. Maybe try and muster up just a little bit of respect.

1.4.0 has been irrelevant for years (because it's literally 2+ years old at this point), that doesn't mean that 1.4.0 is what you or anyone else should be using if you want to emulate PS2, and it doesn't mean that PCSX2, in it's current state, is shit. 1.5.0 is actually pretty good, and leagues beyond 1.4.0. It gets updated literally multiple times a day. It's come a long way since 1.4.0. Many many games that literally wouldn't do anything in 1.4.0 work great in current builds. Don't be too quick to shit on it. Can (and will) something else better come along years from now? It's pretty much a guarantee. So what? That doesn't mean that ZSNES wasn't great for what we had at our disposal in the 90s. The same goes for ePSXe or anything else. Bleem, in retrospect, was "shit" compared to Mednafen too, but it was still amazing for its time. There's always something better on the horizon, but that doesn't necessarily mean what's at your disposal now is "shit" either.

The future is here!

What happens if you drag the files that you want to import into the LB UI and start the wizard?

Post screenshots of your Retroarch and Higan emulator entries.

Sorry, not sure what to tell you there. It's working normally for me via Big Box. This is what it looks like in FS-UAE. And in Big Box:

This sounds awesome dude. Would be happy to help test, though I'm on 7 as well.

It's probably a compression issue. FS-UAE can read within compression one level deep, and it's only going to recognize a single game per zip/lha/whatever. You can't have everything in one zip. For WHDLoad, if you open a zip and see a folder and a .info with the game title, those are fine as-is. .lha files are a compressed format in and of themselves, so you cannot have an .lha in a .zip. Beyond that you just have to have an OAGD (think it's OpenRetro now) account and be logged into it in FS-UAE.

Yep, still working on it. Making a lot of progress though! I think people will be very pleased once everything's done.

Yep...

The plugin was rebuilt a while back to add/change/fix some things. Maybe the old one still works. The one currently available for download definitely doesn't.

And you're using v0.995 Alpha of the plugin? The one that's on the download page here? If so, you're some kind of magical butterfly, because it doesn't work for literally anyone else.

Existing downloaded/created configs will continue to work, but you cannot download/create new ones with the plugin beyond 8.5. The right-click "Configure" option (which you use to do either of those things) does not work outside of OG Launchbox (it's greyed out), which isn't accessible beyond LB 8.5. The new version is designed from the ground up for Next (or just "Launchbox" now). It's getting there but there's still some stuff to be sorted out. It isn't hooked up to my github repo yet so it doesn't download any configs, it only lets you create new ones currently; the plugin's control panel doesn't work yet; the matching still needs to match against the LBGDB ID rather than the library title, etc.

A new version is currently in development, but until it's released you'd need to be on LB 8.5 (which still has an OG LB option) or earlier to use the plugin.