Search the Community

I have not used the ps2 emulation in some time (5-6 months) but when I last used it, everything was working as it should. I remembered an old game I was fond of so I downloaded it but when I came to play it, I can hear the game's sound but not see the image. Funny enough, If I speed the game up, I can now see it? I tested the other ps2 games and sure enough they all do the same thing. Any obvious ideas? So strange that this happened for what seems like no reason. Thank you SO much!

Hi everyone, I’m setting up PlayStation 2 games in LaunchBox and wanted to get some advice from people who’ve already dialed this in. I’ve noticed that PS2 emulation can behave differently depending on emulator versions, BIOS files, and per-game settings. Sometimes a game runs fine on one version and has issues on another, which makes library management a bit tricky. How are you all handling this inside LaunchBox? Do you stick to a single emulator version, or do you keep multiple versions configured for compatibility? Also, what’s your preferred way of organizing BIOS files so LaunchBox stays clean and easy to maintain? I followed a detailed setup and BIOS guide recently that helped clarify a few things during my testing, so I’m curious how closely your setups match common recommendations: AetherSX2 APK Would appreciate hearing how others approach this, especially for larger PS2 libraries. Thanks!

I wanted to ask which PS2 emulator people here find works best. I have been using AetherSX2 for a while now. So far, I have not noticed any major problems or crashes. Games run smoothly in my setup. I am curious to hear about other experiences and what emulators others prefer.

I've recently been setting up PS2 emulation in launchbox, using retroarch as emulator. There's a bit of an oddity that I wasn't sure whether was a Launchbox or a Retroarch issue; when I attempt to launch roms, I'm told that a dependency isn't satisfied. When I check the dependency (screenshot) It shows that the bios can't be found... except that I DO have the correct bios in the correct location, and that 'Play anyway' will correctly launch the ROMs. I'm posting so that the Launchbox team can have a look - it's reporting the bios folder name as bios' instead of bios (see pic) in the first half of the text - the \system\pcsx2\bios location specified contains my bios files, but I think the verification might be using an incorrect name (with a ' appended) when trying to verify. Note that 'Open Location' opens my pcsx2 folder, not my pcsx2/bios folder. So I'm assuming that there's some sort of path issue confusion due to the ' (maybe)?

R-Type Final sound pack View File Some menu navigation sounds from R-Type Final on PS2 and a handful of themes for Startup. Sourced from sounds-resource.com and zophar.net. Trimmed using Audacity MOVE001.wav SELECT001.wav BACK001.wav STARTUP001.wav Submitter la vache qui rit Submitted 07/06/2025 Category Sound Packs  

Sony PlayStation 2 Overlay Animated View File Sony PlayStation 2 Overlay Animated to Retroarch 1920x1080 only tested in fullscreen. Submitter andersonlino Submitted 04/04/2024 Category Platform Bezels/Overlays  

I'm running LaunchBox version 13.20. I just added PCSX2 via Tools > Manage > Emulators. Attempting to launch games from the collection immediately crashes, appearing as though PCSX2 is never launched in the first place. Locating the PCSX2 app in the LaunchBox file structure and launching it directly works, until I either try to launch a game or try to open any of the menus. At which point, it immediately crashes. I've reinstalled it twice. I've placed various BIOs files. And I honestly have no idea what to do from here. I can offer any information that would be helpful. Any help would be appreciated. Thanks in advance.

Ps2 Console Box Theme Video View File My Ps2 Box Platform For U guys. Game On! Sony Playstation 2.mp4 Submitter DonellHD Submitted 07/05/2024 Category Platform Theme Videos  

Hello people, this is the first time I come here. So if I posted in the wrong place I'm sorry can anybody help me? I am unable to run the ps2 emulator (pcsx2), every time I open it this error occurs. I found absolutely nothing on the internet. Thanks in advance.

I have the following pscx2 emulator config: when I'm trying to open PS2 game from LaunchBox it asks to insert a disc: but when I'm trying to execute the game directly from pscx2 emulator it works fine. could you please suggest what changes should be made to start the game automatically from LaunchBox? thanks in advance.

Introduction After figuring out how to implement PS2 games into my Launchbox library properly i thought i'd share my findings. This is a slightly different approach than the guide by Zombeaver. It has a bit more manual configuration work but it's also more elegant in that it does not require a third party tool or individual command line options. It still features individual configurations (and mem cards) for each game. Step 1 - Setting up your PCSX2 installation: You should be using one of the experimental 1.5.0 builds at this point. The last stable release is 4 years old now and simply outdated. Provide Bios file to Bios directory and start PCSX2 Misc > Uncheck "Show Console" Config > Memory Cards: Convert your memcards to folders and make sure the "Automatically manage saves based on running game" checkbox is tickedSet up like this PCSX2 will automatically create new memcards based on the running game. You don't have to manage mem cards anymore. Config > Emulation settings - GS Window: Enable "Default to Fullscreen" Config > Emulation settings - GS Window: Enable "Always hide mouse cursor" Config > Emulation settings - Speedhacks: Choose Preset 3 Config > Emulation settings - Speedhacks: Now disable Presets Config > Emulation settings - Speedhacks: Disable MTVU Option Config > Controllers > Plugin Settings: Set up your controller of choice in Lilypad plugin settings Config > Video > Plugin Settings: Feel free to adjust Internal Resolution to your liking(Thanks to Suhrvivor for pointing out OpenGl as the better default) Config > Video > Plugin Settings > Shader Configuration (optional)Recommended Shader options: PIXEL_VIBRANCE & TEXTURE_SHARPEN Step 2 - Setting up PCSX2 in Launchbox Go to Menu > Tools > Manage Emulators > Add Select PCSX2 from the Emulator Name dropdown menu Point the Emulator Application Path at your PCSX2 executable Use the following Default Command-Line Parameters: --fullscreen --portable --cfgpath=inis\%gameid%The %gameid% variable will tell launchbox to parse the game's ID from the XML data and insert it into the command line. The --cfgpath=inis\ infront of this will result in a unique subdirectory in your PCSX2's ini folder where the configuration for each specific game will be saved. Unfortunately %gameid% is the only available parameter to use for this to work. It would be nice if there was a parameter to just use the rom's filename (twice) but launchbox doesn't have it right now. Go to the Running Autohotkey Script tab and remove the ESC > Close script for now.. Step 3 - Import and configure your PS2 games Import your PS2 game image as rom file and choose PCSX2 as emulator. Now try to start the game once.You will get an error message like this. At this point PCSX has already created a new subfolder in the inis directory based on the %gameid% variable. But since it is empty, you are greeted by the config wizard. Choose cancel and navigate to your ..\PCSX2\inis directoryHere you can see an example for the auto-created ini folder. It can be identified by being the newest folder and only containing these two files. Now copy all .ini files from your inis folder to the subdirectory and overwrite when prompted.We have now supplied this game with the chosen default settings. Start the game again from Launchbox. This time it should run with your chosen default settings. Now it is time to finetune your game config. As a source of information for game configs i used each game's entry in the PCSX2 wiki. Here you can find detailed information about most game's issues and their known workarounds. Alternatively, you can use the PCSX2 Config Spreadsheet Zombeaver provides in his guide. Press ESC, make adjustments and hit File > Resume to test the settings. At this point making changes on the fly like this is very reliable in PCSX2. Once you are pleased with the result, just close PCSX2. Your changes will be saved to the game's individual config. Now repeat Step 3 for all your PS2 games (I know ... *yawn*) Step 4 - Finalizing When you have all your games imported and configured there are 2 more steps to make integration into Launchbox perfect. Change the Default Command-Line Parameters of your PCSX2 Emulator in Launchbox to: --fullscreen --portable --nogui --cfgpath=inis\%gameid% By adding --nogui each game will start directly without invoking the main PCSX2 window. Go to the Running Autohotkey Script tab and restor the ESC > Close script as follows: (Thanks to Retro808 for providing a cleaner close command) ; This section closes PCSX2 when pressing Escape $Esc:: { WinClose, ahk_exe pcsx2.exe } This will restore the functionality of the ESC key to quit the PCSX2 process. This is especially important if you are using the --nogui parameter because using the (regular) ESC in PCSX2 with --nogui and disabled log window will leave you with no visual indication that PCSX2 is still running. And you will have to kill the process from the task manager every time. Afterthoughts You may have guessed it by now, with the gameid being cryptic as they are, the only sensible way to re-adjust your games is to undo Step 4, make the corrections ingame and then reapply it. That is the one gripe i have with this approach at the moment. But it's really a minor inconveniance. The result is a really easy import process on the Launchbox side and still getting those per/game configs & saves. So i am very happy. Let me know what you think and please share ideas for improvement.

Auto Generated Playlists for the bigger systems, all zipped up View File A few automated child playlists I made today, over 1600. I'm debating whether or not to include these with my main build, I'm thinking it might be too much. Anyways, here they are, all zipped up if you want 'em. Submitter -McFly- Submitted 02/11/2024 Category Playlists  

Theme Videos and Video Snaps for Sony Playstation 3 View File Sharing some theme videos and video snaps I made for this console. I might add more as soon as I make them. How to add to your LaunchBox and BigBox: Download the zip files. Extract to LaunchBox's root folder. Content will be extracted to its proper folders. Done! Video snaps will show up in the game details panels and theme videos will appear on BigBox themes' views that use them. List of Video Themes: Catherine Demon's Souls Diablo III: Reaper of Souls: Ultimate Evil Edition Earthworm Jim HD Final Fantasy XIII Final Fantasy XIII-2 God of War HD God of War II HD God of War III Lollipop Chainsaw Lightning Returns: Final Fantasy XIII Mirror's Edge NBA Jam: On fire Edition NEW Ni no Kuni: Wrath of the White Witch NieR: Replicant Persona 5 Red Dead Redemption Red Dead Redemption: Game of the Year Edition Resident Evil Code: Veronica X HD Super Street Fighter II Turbo HD Remix The Last of Us Details for Nerds: Theme videos are mostly 1080p60, encoded with HEVC for optimal file size. Video snaps are usually 540p, some lower resolution, some higher up to 720p60. Encoded using x264 for compatibility and performance. Theme videos' audio is 160 kbps aac, video snaps 96-160 kbps aac. Submitter Suhrvivor Submitted 03/24/2019 Category Sony Playstation 3  

Introduction If you’ve tried your hand at PS2 emulation with PCSX2 for any length of time, you’ll know that it’s an impressive but thoroughly imperfect emulator that needs a guiding hand more than most. There’s really no one-size-fits-all setting solution when it comes to PCSX2 configuration (other than setting it to software mode and leaving it there, and even then you’ll still run into some issues, just much less frequently) which means that you really need to create configurations on a per-game basis to get the most out of it. This is often a slow, tedious, and incredibly time-consuming process of testing, making changes, reading wiki and forum posts, testing, making more changes, and then testing some more. In some cases, it’ll never be perfect, regardless of settings used but with some adjustments you can get it “pretty close”. Some cases are nigh on perfect and others are a broken mess with any setting (even software, in a few cases). There are a significant number of one-off fixes that are often necessary in games, from special hacks, to fixes like running all FMVs in software mode, to things like skipdraw for disabling buggy post-processing effects and TC offsets to fix sprite alignment issues - all kinds of things that are needed to offset various visual bugs brought on by upscaling. It’s just the nature of the thing. I’ve been using PCSX2 for a while now - since version 1.2.1 (2014). My Launchbox library had been a mishmash collection of configs for versions 1.2.1, 1.3.1, and 1.4.0 so several weeks ago I decided to finally break down and go through the process of updating all of these to 1.5.0 (1.6.0 now) and then try to add more once that was complete. The thought occurred to me though, that if I was going to go to the trouble of doing this, I might as well share them here for others to use as well. That presented a question, however, as to how best to distribute them. PCSX2 is a bit more complicated when it comes to creating and using custom configs - you have to duplicate not one, but several .ini files that contain various settings that PCSX2 will use, and then direct these specific .inis to PCSX2 via command-line (--cfgpath “[path\to\the\config]”). User @alec100_94 created a great plugin for Launchbox called PCSX2 Configurator that helps automate the configuration creation process by duplicating sections of your current .inis into a new folder named after the game title, then injects the appropriate command-line parameters into that game’s Launchbox library entry. As an added bonus, it can even create independent memory cards for each game. I thought this might be a way to at least help simplify the process for people so they could more easily use the configs, so I contacted him about it about a week ago to get his thoughts on it. To my surprise, not only was he willing to help me in my attempt to streamline the process for people, he offered to come up with a way to incorporate the configs into the plugin and allow users to download and apply them directly from within Launchbox. So we had a lot of back and forth over the course of the last week and did a lot of testing and now we’ve ended up with something I’m really happy to say works very well. Exciting! Major props to Alec for all his hard work on this (and for putting up with all my picky crap ). Note: All tech support requests for the plugin itself need to be directed to Alec on the Launchbox Discord, not here. Our Discord server can be accessed here: https://discord.gg/AFxfhnv Go to the plugins channel and message @alec100_94#4327 Getting started All you need to do is download and install the plugin, then right-click on a Playstation 2 game in your library, and then click on the "PCSX2 Configurator" option at the bottom of the right-click menu. From here you can either click "Create Config" to create your own config (or overwrite your current config) or "Download Config" to download mine. If I've created a config for the game, the "Download Config" option will be enabled (lit) - if I haven't, it won't be (note that a takes a second or two for a match to be made, so "Download Config" won't immediately be lit even if I've created a config for it). If I've updated a config since you originally downloaded it, an update option will be lit which can be clicked to update the config to the newest version. Once you've downloaded or created a config, the "Remove Config" and "Configure with PCSX2" options will be usable. Clicking "Configure with PCSX2" will open PCSX2 for you to edit that config as you see fit. Once a config is present, the right-click "Configure" option will do this as well. The games must be scanned and matched with the LBGDB first! The LBGDB ID is how configs are matched, so you must do this first. Once they're scanned/matched you're ready to go - just right-click -> PCSX2 Configurator -> Download Config and you're all set! First and foremost, and I cannot stress this enough, is that these configs are designed specifically for PCSX2 1.6.0. Do not use 1.4.0 and don't use a 1.5.0 dev build unless it's a very late one. These were specifically tested with 1.5.0-dev-3400 which was post-1.6.0 release candidate. The configs Now that everything's squared away with the plugin, I'll be able to get back to working on more configs going forward. Right now I’m at 86 configs [EDIT: up to 285 currently]. Not a whole lot, I know, but it’s a start. I’m open to requests, but understand that I’ve already got a stack of about 200 more games that I have set aside to work through as a start (to-do list is at the bottom). I’m prioritizing stuff that’s 1) of interest to me and 2) don’t sound like they have huge game-breaking issues based on their PCSX2 wiki page. The PCSX2 compatibility wiki is kindof a mess that isn’t particularly well-documented and, in my experience, is frequently full of outdated and/or outright incorrect information, but it’s at least a sortof starting reference point for whether or not I decide to try out a game. Also try to keep in mind that this is often a very time-consuming process so don’t expect to see 20 new configs added in a day. In cases of really severe complications, it can be 30 minutes to multiple hours of testing and tweaking for one config. I have an ongoing spreadsheet detailing what’s in each config as well as some additional notes where appropriate and a rating of what I consider to be the relative significance of emulation issues present for that game, from minor/nonexistent to moderate to broken. Software mode is generally only used as a last-resort when no other hacks or fixes could resolve various issues brought on by hardware rendering, but be aware that there are some configs that use software rendering because of this. I’ll periodically be making updates in this thread to note new configs that are added, and of course the spreadsheet will be kept up to date. >> PCSX2 Config Spreadsheet << The configs are fairly moderate in terms of system requirements, as my PC is about 4 years old (EDIT: 7 years old) at this point (specs at the bottom) and can often push these a bit higher than what’s included in the configs, depending on the game, but realize that there’s going to be some variance in performance depending on your hardware. Because of this, I wanted to provide some tips below on how these can be altered to improve performance. Performance improvement tips (if necessary) As part of the update process from 1.5.0 configs to 1.6.0, I went through and benchmarked all configs with the framelimiter off, and made adjustments as necessary. The end result should be better performance (at the very least, better maximum performance, whether you actually need that or not) for everyone. Some key elements that can be used to improve performance (and generally have been used already where appropriate) are listed below. Enabling MTVU is often a good starting point for improving performance. It has high compatibility and is an easy go-to. There are some cases where it causes problems in a game that I've noted on the details spreadsheet. This is generally enabled where appropriate and where there was an actual impact on performance in testing. If necessary, you can also try dropping the scaling by 1x at a time until performance improves. It should be noted that some games are more CPU-limited than GPU-limited, in which case reducing the scaling can have little to no impact on performance. It's something to try if performance is poor, however. You can also try disabling Large Framebuffer. This is a parameter that used to be on by default but no longer is. It serves a primarily niche purpose as it only affects a small number of games (FMV flickering with it off) but can often negatively impact performance. I've generally disabled this in cases where appropriate, didn't cause an issue (or the issue could be remedied in an alternate way), and actually did improve performance in testing, but there may be additional cases where disabling it would be beneficial. Enabling Allow 8-Bit Textures can also improve performance depending on your hardware and the demands of the game. It basically shifts the demand on the CPU and GPU. One additional thing you can try is changing the sync mode in the SPU settings from timestretch to async. I mention this one last because it has the highest probability of causing problems, but compatibility is still quite good overall. Basically what this is doing is changing it so that audio and video no longer have to be 100% synced at all times, which sounds like a bad thing but in practice it’s not. With timestretch there can be times where, if the game is performing poorly, you’ll get this really awful, stuttery, warbled mess for the audio because it’s going out of its way to keep them in sync and it creates a bit of a mess. Async can make these problematic moments much less noticeable. It's useful for games that have occasional and brief dips in performance - if a game is just constantly running at 50% speed though, the only thing it's going to do is make the audio way out of sync from the game. You can also try adjusting the EE Cycle Rate, but I don't recommend doing this unless you really have no other option. It can be helpful on occasion, but it has a significantly higher probability of breaking things, so leave it alone unless absolutely necessary. I would highly recommend that you never change EE Cycle Skipping at all, as it has an even greater chance of breaking things, causing dropped frames, giving false speed numbers... just leave it alone. My hope is that the vast majority of people won’t have to change anything at all, but I wanted to give some pointers here in case your system is struggling. My current to-do list: My PC: i7 4770k CPU GTX 780 32 GB RAM 256GB SSD System Drive Windows 7 Pro (64-bit) pcsx2-v1.5.0-dev-2711-g8307cfc54-windows-x86.7z