also having RPCS3 just open as a process and never show up
Started by supersemantic




2 posts in this topic
supersemantic
Member


0
2 posts 1 threads Joined: Feb 2019
02-28-2019, 05:35 AM -
#1
Hello,

I've read through a number of forum posts in here of folks who've had the same (or similar) issue to this, but none of the solutions I've tried worked. Specs: Windows 10 Pro, AMD Ryzen 5 2600 (six core) 3.40 ghz, Nvidia GTX 1080, 32gb DDR4 ram, and GPU driver version 419.17. I've attached my log, though it seems very unhelpful (it lists my version of RPCS3 and specs, and that's literally all). I didn't have a TTY.log, so it's just the singular log file.

Things I've tried:
- uninstalling drivers through DDU, then reinstalling
- ensuring my version of RPCS3 is the latest version (v0.0.6-7817-240ba39d Alpha, which was about an hour ago)
- ensuring I have the latest GPU drivers (I do)
- rebooting
- manually double-checking I'm launching as administrator (I am)
- swearing at the screen

Is there something I've overlooked? Or perhaps another avenue of troubleshooting I'm not aware of?

Thanks in advance.
Ani
Administrator
*******


16
4,275 posts 105 threads Joined: Aug 2017
03-02-2019, 09:47 PM -
#2
Try removing games.yml file, may be corrupted

Try with driver 399 as well, newer drivers have some issues
    Desktop: Ryzen 7 5800X,   Radeon RX 6800 XT, 2x8G DDR4 3600MHz, Manjaro Linux
     Laptop: Ryzen 9 5900HX,  Radeon RX 6700M,   2x8G DDR4 3200MHz, Manjaro Linux
Old Desktop: AMD FX-8350,     Radeon R9 280X,    2x4G DDR3 1600MHz, Manjaro Linux
supersemantic
Member


0
2 posts 1 threads Joined: Feb 2019
03-03-2019, 03:55 AM -
#3
So, I actually did manage to get it working in the time between submitting and now (thankfully!). I'm not sure which thing was what did it, honestly.

First thing was re-downloading everything for RPCS3, just in case something had gotten corrupted. Then, after remembering a lot of threads where people had trouble with their vulkan-1.dll, I re-downloaded and installed all the Vulkan stuff and moved the "new" .dll in (I say "new" because I had the latest files already). Lastly, I did all the Windows updates that I'd been holding off on, because I typically don't update for a while until any issues are found and ironed out.

Of those, I'm leaning towards either the .dll being the culprit or the Windows updates somehow affecting it, but I don't know enough about RPCS3 to say for sure. Either way, thanks for taking the time to look over this.


Forum Jump:


Users browsing this thread: 1 Guest(s)