Ubuntu Version:
24.04.4, kernel 6.8.12-060812-generic
Problem Description:
Hi! I’ve been having an issue with launching games using 3D engines that I’ve been searching pretty hard for solutions to, with not a lot of success thus far.
Right now, what happens when I launch Unity games in Steam is that the game indicates it is running briefly, shows a small crash window (see below), and then stops. Some games, like Peak, will launch with a specific Proton version (Proton 8.0-5), but won’t get past the introduction screen with only 2D elements up to that point. I have a feeling this is related to my current graphics drivers, but I haven’t been able to find a lot of clear advice on finding Unity crash logs to troubleshoot the exact issue for what is going on. The exact crash-logger depends on my version of Proton. The below is an example from allowing Steam to autoselect the compatibility layer it wants to use.
Relevant System Information:
I’m also including my lspci output since I figure it may be relevant. I’ve noticed I don’t have a 3D controller listed, and I suspect that’s not a coincidence.
$ lspci -k | grep -EA3 'VGA|3D|Display'
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1)
Subsystem: Apple Inc. GK107M [GeForce GT 750M Mac Edition]
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
Screenshots or Error Messages:
The first crashlogger screenshot is from compatibility autoselect, the second results from both Proton 9.0-4 and 8.0-5. Sorry if the embeds don’t work! It’s hard to tell from the topic-drafter.
What I’ve Tried:
In case it is relevant, I previously had to spend some time troubleshoot my graphics driver settings; in order to install the Nvidia 470 drivers compatible with my gpu I had to downgrade my kernel to 6.8 from 6.17, and I’ve played a lot with other settings and potential driver installers since doing so to fix this issue myself. So far I’ve tried turning off Wayland to use Xorg using my /etc/gdm3/custom.conf (which I have since returned back to normal), uninstalling and reinstalling my drivers a couple times (which themselves required troubleshooting), and a couple other things I can probably explain in more depth using history if relevant (for now I’ve opted not to though given that the issue preceded and prompted this troubleshooting, and if I’m not sure it would be useful it would be a good amount of effort to reverse engineer exactly everything I’ve tried).
Thanks so much for any help you are able to offer. I’ve spent almost a full 24 hours pulling my hair out over this and it would be really nice to get some help, so your time is deeply, deeply appreciated.