PCSX2 Troubleshooting

General Issues with PCSX2

This section covers some common problems that you may encounter when using PCSX2 and offers potential solutions.

Important Tip

Before troubleshooting any issues, it’s highly recommended to update your PCSX2 version to the latest one.

Game Stuck on a Black Screen or Not Loading Correctly

Info:
This usually indicates that your game dump is corrupted or incomplete.

Solution:

  1. Verify the Integrity of Your Dump:
    • Right-click on the game in the game list and select “Properties.”
    • In the game properties window, click the “Verify” button under the disc track list.
    • If it returns a green checkmark (✅), your game dump is fine.
    • If it returns a red cross (❌), your dump is corrupted, and you’ll need to redump your game. Refer to the gathering files page for instructions on how to do so.

Unable to Start Video Capture

Info:
PCSX2 requires additional FFmpeg libraries to enable video capture.

Solution:

Still Having Problems?

If your game is still not working or you encounter other issues, consider the following steps:

  1. Check the Compatibility Page:
    Verify if the game has been tested to run properly.

  2. Consult the Wiki Page:
    Check for specific information related to your game.

  3. Visit the GitHub Issues Page:
    See if any issues related to your problem have been reported.

  4. Join the PCSX2 Discord Server:
    For further assistance, you can join the community on Discord.

PCSX2 Troubleshooting: Performance Issues

PCSX2, like many emulators, is a hardware-intensive program that can sometimes run into performance issues. This guide covers common performance problems and how to address them.

It Works, but It’s Slow?

One of the most common issues users face is that PCSX2 runs, but at a slow speed. Given that emulation is a demanding task, especially on the processor, slow performance is not uncommon.

Caution:
Before diving into troubleshooting, it’s recommended to read the PCSX2 Requirements page. If you still have questions, you can ask for help in the PCSX2 forum thread titled “Will PCSX2 run fast on my computer?” or join the PCSX2 Discord server.

Enable OSD to Measure Performance Bottleneck

When reporting performance issues, it is helpful to include a screenshot of the On-Screen Display (OSD) with performance counters.

How to Enable Performance Counters:

Why It’s Important: These metrics help identify where the performance bottlenecks occur in your system. Screenshots should be taken while the game is running poorly to provide accurate data.

OSD Legends: Understanding the Metrics

The OSD displays various statistics, which can be confusing. Here’s a breakdown:

Hardware Mode:

Rank of Performance Impact (Worst to Least Worst):

Software Mode:

Settings Indicator:

Consistently Low or Unstable FPS

Tip:
Before troubleshooting further, ensure that your computer meets at least the minimum system requirements for PCSX2.

Windows Power Plan:

NVIDIA WhisperMode:

USB Devices Are Slow

Tip:
Avoid storing your game ISOs on USB devices. USB drives handle bulk transfers well but struggle with the small, fast transfers that PCSX2 requires. This can cause significant speed penalties. For better performance, store ISOs on SATA or M.2 drives.

Windows-Specific Issues for PCSX2

Missing “MSVCP140.dll”

If you encounter an error message about “MSVCP140.dll” during PCSX2 startup, it indicates that the required Visual C++ Redistributables are missing.

Solution:

Crashes

Several issues can cause PCSX2 to crash. Here are some common scenarios and solutions:

1. Crash When Opening Settings or Launching a Game

2. Crash When Adding a File/Directory to the Game List or Opening PCSX2 Settings

3. Crashes Due to OpenCL™, OpenGL®, and Vulkan® Compatibility Pack

Linux-Specific Issues for PCSX2

libfuse2 Error

If you encounter an error like dlopen(): error loading libfuse.so.2 when opening the PCSX2 AppImage, it indicates a missing library dependency.

Solution:

Reporting Issues with PCSX2

When encountering problems with PCSX2, providing detailed information helps in diagnosing and resolving the issue efficiently. Here’s how you can gather and report necessary information:

1. Collecting Emulog

emulog.txt contains valuable log data that can assist in diagnosing issues.

Steps to collect emulog.txt:

  1. Enable Logging:
    • Go to Tools > Enable File Logging.
  2. Restart PCSX2:
    • Ensure PCSX2 is restarted after enabling logging.
  3. Locate emulog.txt:
    • Navigate to Tools > Open Data Directory... and open the logs folder.
    • Find the emulog.txt file.
  4. Reproduce the Issue:
    • Replicate the problem you are experiencing.
  5. Close PCSX2:
    • Close PCSX2 before uploading the emulog. Avoid opening PCSX2 again as it will overwrite the log file.

Tip: Avoid booting another game or restarting PCSX2 after the issue occurs to preserve log information.

2. Collecting GS Dump

A GS dump captures graphics data which helps in fixing graphical glitches.

Steps to create a GS Dump:

  1. Reproduce the Graphics Issue:
    • Ensure the graphics bug is visible on the screen.
  2. Create the Dump:
    • Use the key combination Shift + F8.
    • Alternatively, go to Tools > Save Single Frame GS Dump.
  3. Locate the GS Dump:
    • GS dumps are saved in the /snaps folder within PCSX2’s data directory, typically located in your Documents folder.
    • Use Tools > Open Data Directory to quickly access the folder.

Info: Your graphics settings do not affect the dump. You do not need to change renderers or other settings.

3. Bisecting Regressions

If you need to find the specific PCSX2 version that introduced a regression:

  1. Identify Known Versions:
    • Start with a known working version and a known broken version.
  2. Test Intermediate Builds:
    • Download a build between the known good and bad versions.
    • Test this build to determine if it is good or bad.
    • If the build is good, test the next build halfway between it and the known bad version.
    • If it is bad, test the next build halfway between it and the known good version.
  3. Continue Testing:
    • Repeat the process until you narrow down the regression to a specific build.

Tip: Document the versions you test and whether each was good or bad.

4. Reaching Out for Help

After gathering all the necessary information:

Providing detailed logs, dumps, and regression testing results helps the community and developers to assist you more effectively.

You also may like 〣〣
icon sosmed svg icon sosmed svg icon sosmed svg