Why pcsx2 crashes

Forgot your username? Create an account. Please Log in or Create an account to join the conversation. With you having both dxgi. Install as opengl Same way the other way around, if you first start with D3D Install as dxgi. This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

View Privacy Policy. Reconsider Cookies You have declined cookies. This decision can be reversed. Index New Topic Profile Search. Log in Username. Remember me. Log in Forgot your password? Start Prev 1 Next End. If both dxgi. When using the OpenGL renderer, however, content can be started and it will function normally but if you pause the emulation and then go to the video plugin section the app will crash.

This can be avoided by renaming dxgi. Both dxgi. The issue seems to have started in 4. In summary: 1 4. This is expected behavior. Since ReShade 4. I've also tried the Arch Linux community packages with the same result. Could this be an issue with GCC Issue Explorer. Vendor: VMware, Inc.. Driver: Core Profile Mesa Sanaki wrote this answer on ThisNekoGuy wrote this answer on Your Name. Your Comment Add Comment. More Details About Repo. Also even if I use the connected controller's mousepad the ds4 has one , I can move the cursor around and it too crashes.

That's also bluetooth-connected. This issue is related to If you know anything about debugging. Could you attempt to post a backtrace of the issue for us? Interesting, that must be it exactly. So the delay needed to trigger the crash is simply needed for the bluetooth device to lose connection.

Still, that doesn't explain why I can trigger the crash by moving the mouse cursor using the touchpad of the same ds4 controller that stays connected since I'm using it to actually play the game. Also yes, I'm certainly happy to help you debug this.

However, I tried a gdb trace but I get the following message in terminal before the game runs at all nothing to do with the above crash :. Also, I can close this issue and report any further results in the other issue report if you'd like, just to keep everything in one place.

That's not actually true. You can run it with the recompiler. But yeah the other thread would be best. Well I set the EE to interpreter and ran the gdb, didn't crash until I woke up the bluetooth keyboard. Sure thing, results are here assuming you mean the "word" backtrace and not something else? It happens deep in the belly of GTK3. GTK3 is highly experimental, you probably saw that message during the cmake run.

I tried installing GTK2 on Ubuntu There you can compile against GTK2. Maybe give that a try? I'm personally quite a sucker for Manajaro as it has all the out-of-the-box luxury Ubuntu gives you plus pacman and AUR access.

There is even a Manjaro Cinnamon version Just to make sure I understood you correctly in your initial post, you did play around with the "Always hide cursor option", right? Thanks for the detailed explanation, and you're right that I'm stuck with GTK3 on Mint 20 no downgrade path or alternate system here in the immediate term unfortunately.

Funny you mention, I've actually been planning to use Arch or Manjaro myself at some point in the future but haven't found time to set it up yet - perhaps then I'll try GTK2 even though I assume the other benefits of GTK3 may outweight this annoyance just don't know when.

In either case I'm happy to report it there. Finally yes, I did try the "Always hide cursor" option to no avail, sorry for any confusion. I use it as a clean environment for testing PCSX2. OpenGL, Bluetooth, Internet runs out-of-the-box on the live system. LilyPad you can exclude right away if you're using onepad. Then it comes down to the four calls in FrameForGS.