My wife has an eight year old computer we're building a replacement for. Recently, Hades started to a black screen with a cursor; and Cat Quest 2 claimed no graphics card was installed.
I replaced the previous GTX 950 with a GTX 1660, replaced the PSU with a new one, and updated Nvidia graphics drivers to version 515. Unfortunately, this is all still happening.
It is the only thing on the machine, which I know of, to have issues of any kind. The 1660 is in perfect health. I recently used that same card to play Hades through to the end, on a different machine, running the same OS.
Problems go from a black screen with a cursor visible to outright failure to launch. Not that long ago, it was working fine. I know it isn't the GPU or the PSU. In the best case, she has a black screen, a cursor, and background music.
Does anyone have any ideas?
Addendum: Recently I managed to get Hades to a title screen, but only after along delay and a brief flash of what looked almost like CGA graphics. It was still unresponsive.
Addendum: Now that said computer is reassembled, I used NVIDIA's prime-select to ensure that the desktop environment was set to use the actual graphics card, and not the iGPU. (This would be just as well, save that the games aren't seeing it.) It actually doesn't even detect the iGPU, possibly because it's an older AMD piece from around 2013 or so. Steam's system information also reports the correct card installed, and every other program runs flawlessly.
Addendum: My wife informs me that after setting Proton to use DirectX instead of Vulkan, and a considerable delay, it finally loaded and allowed her to play. This is a weird spot in an academic sense because I still don't know why it was refusing before. Additionally, possibly because of the DirectX setting, she has significant screen tear now; but it should hold her until her new machine is assembled.
That said, I don't consider the problem solved, because the game is still acting wonky (screen tearing) and I had no such problem using Vulkan on an almost identical machine, with the exact same hardware. So, I think the jury is still out on this one...
systemctl—I used the command option /GpuIndex=1 just in case, and it had no affect, but it might be that my GPUs are being indexed in the wrong order and it was doing that anyway. I've also validated the game cache twice and come up with nothing. I'll be back when I've got more data.