Bought Starfield, still can’t play it. Linux, nvidia no MUX switch. Starfield won’t use the discrete GPU. Doesn’t even know its there. Thrown every launch option I could find at it. Uninstalled and hidden now. Worst purchases I ever made on a game.
Oldrim and Starfield are the only bethesda games I didn’t buy on super sale. I’ll never make that mistake again. I even purposefully bought it without waiting for sales to throw some support to the devs for building the majority of my favorite games I’ve ever played.
The up side is that after about two weeks of tinkering I bought Baldurs Gate 3 on a whim. Been playing it non stop ever since. I might not have bought BG3 if bethesdas didn’t have such a shity unpayable game at launch, so in a way I thank them. BG3 has far exceeded my every expectation. What I thought would be a mediocre time waster turned out to be the best game I’ve ever played.
Yes I’ve done so much tinkering to everything I can possibly do. Like 5 hours of 2 minute game time testing. Enough to negate a steam refund!
Telling proton to use prime-run. Custom protons, every launch option that matched my specs on protondb.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command% doesn’t work at all.
It’s not just a Linux issue. I read on steam, a guy only got Starfield to launch in windows after disabling his primary GPU in bios via MUX which sadly isn’t an option for me.
I’ve tried everything but Wayland. If you’ve got some magic to try I’m all ears.
If you have a newer Nvidia card, Wayland works just fine, and more optimally than X in multi-monitor scenarios, as X locks the refresh rate to the lowest monitor’s setting across the board.
I have a 3090 and Wayland lets me use all three of my monitors at their native refresh rates.
It’s funny that you’re removed about the game being bad because it doesn’t run on an OS it wasn’t designed to run on. That’s kind of a silly thing to get up in arms about. Linux gamers are lucky that Proton works as well as it does the majority of the time, and I think you’ve taken that aspect for granted.
It’s funny that you’re removed about the game being bad because it doesn’t run on an OS it wasn’t designed to run on. That’s kind of a silly thing to get up in arms about. Linux gamers are lucky that Proton works as well as it does the majority of the time, and I think you’ve taken that aspect for granted.
Maybe so. Seems like there is a bunch of removed about the game to go around even on windows using nvidia though. And if Larian can get it right you’d think bethesda could. Even on windows.
Also I have no idea if the game is bad. I cant even play it so I cant say if the game sucks or not. Here in a few years when it’s playable if it’s playable I’ll make that decision. By then the modding community will have had a chance to do their thing and hopefully make the game an even better game.
Nobody has ever respected Bethesda for their quality work on engines.
Larian also has not been famously known for the last three decades as the studio with the most bugs on AAA titles.
Modding will kick off more next year when they release the official kits and tools. Surprised that wasn’t priority number 2 after ironing out the bugs.
Also, what distro are you running? I didn’t have problems getting it to work on Endeavour, once I got a Steam copy. You can’t run the Xbox launcher games properly AFAIK and they’re markedly worse for modding anyways.
You have it running on a muxless optimus laptop? What launch options are you using and what proton?
Bought SF through steam as well.
Tried EOS before Garuda. Following the asus-linux instructions they recommended manually installing nvidia drivers. Following the arch wiki I bricked my install a few times before moving on. Like I said in another post I give no shade to EOS as it was defiantly operator error. I think I was trying to use mkinitcpio to rebuild initramfs and if I remember correctly EOS uses dracut. At least thats what I think I remember causing my issue, been around a year ago.
Yeah EOS uses Dracut, that’s probably the issue there.
I’ve had success using the Nvidia-DKMS package on both a laptop (with a 1650) and the aforementioned 3090 machine.
I’ve never had to manually rebuild initramfs, whenever a major enough system upgrade happens the package manager is designed to automatically rebuild the file, which typically happens every time you update the Nvidia drivers.
Does Garuda have the option to use the DKMS package? I think that’s what made the difference for me.
…why didn’t you just refund it?
Even if you passed the 2h window because of troubleshooting, Steam Support would probably still allow it if you explained you couldn’t get it to work at all
Bought Starfield, still can’t play it. Linux, nvidia no MUX switch. Starfield won’t use the discrete GPU. Doesn’t even know its there. Thrown every launch option I could find at it. Uninstalled and hidden now. Worst purchases I ever made on a game.
Oldrim and Starfield are the only bethesda games I didn’t buy on super sale. I’ll never make that mistake again. I even purposefully bought it without waiting for sales to throw some support to the devs for building the majority of my favorite games I’ve ever played.
The up side is that after about two weeks of tinkering I bought Baldurs Gate 3 on a whim. Been playing it non stop ever since. I might not have bought BG3 if bethesdas didn’t have such a shity unpayable game at launch, so in a way I thank them. BG3 has far exceeded my every expectation. What I thought would be a mediocre time waster turned out to be the best game I’ve ever played.
That sounds more like a issue with your proton configuration then a fault of the game.
Have you tried to change the proton configuration, to force it to use the discrete GPU?
Nvidia GPUs are known to be problematic in Linux, not only with Wine/Proton
Yes I’ve done so much tinkering to everything I can possibly do. Like 5 hours of 2 minute game time testing. Enough to negate a steam refund!
Telling proton to use prime-run. Custom protons, every launch option that matched my specs on protondb.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%doesn’t work at all.It’s not just a Linux issue. I read on steam, a guy only got Starfield to launch in windows after disabling his primary GPU in bios via MUX which sadly isn’t an option for me.
I’ve tried everything but Wayland. If you’ve got some magic to try I’m all ears.
If you have a newer Nvidia card, Wayland works just fine, and more optimally than X in multi-monitor scenarios, as X locks the refresh rate to the lowest monitor’s setting across the board.
I have a 3090 and Wayland lets me use all three of my monitors at their native refresh rates.
It’s funny that you’re removed about the game being bad because it doesn’t run on an OS it wasn’t designed to run on. That’s kind of a silly thing to get up in arms about. Linux gamers are lucky that Proton works as well as it does the majority of the time, and I think you’ve taken that aspect for granted.
Maybe so. Seems like there is a bunch of removed about the game to go around even on windows using nvidia though. And if Larian can get it right you’d think bethesda could. Even on windows.
Also I have no idea if the game is bad. I cant even play it so I cant say if the game sucks or not. Here in a few years when it’s playable if it’s playable I’ll make that decision. By then the modding community will have had a chance to do their thing and hopefully make the game an even better game.
Nobody has ever respected Bethesda for their quality work on engines.
Larian also has not been famously known for the last three decades as the studio with the most bugs on AAA titles.
Modding will kick off more next year when they release the official kits and tools. Surprised that wasn’t priority number 2 after ironing out the bugs.
Also, what distro are you running? I didn’t have problems getting it to work on Endeavour, once I got a Steam copy. You can’t run the Xbox launcher games properly AFAIK and they’re markedly worse for modding anyways.
I’m using Garuda.
You have it running on a muxless optimus laptop? What launch options are you using and what proton?
Bought SF through steam as well.
Tried EOS before Garuda. Following the asus-linux instructions they recommended manually installing nvidia drivers. Following the arch wiki I bricked my install a few times before moving on. Like I said in another post I give no shade to EOS as it was defiantly operator error. I think I was trying to use mkinitcpio to rebuild initramfs and if I remember correctly EOS uses dracut. At least thats what I think I remember causing my issue, been around a year ago.
Yeah EOS uses Dracut, that’s probably the issue there.
I’ve had success using the Nvidia-DKMS package on both a laptop (with a 1650) and the aforementioned 3090 machine.
I’ve never had to manually rebuild initramfs, whenever a major enough system upgrade happens the package manager is designed to automatically rebuild the file, which typically happens every time you update the Nvidia drivers.
Does Garuda have the option to use the DKMS package? I think that’s what made the difference for me.
Yeah I have the dkms installed.
So you are running the 3090 on a optimus laptop?
What about your proton version. I’ve tried all but the latest GE version.
What about your launch options? Are you using Prime render offload?
…why didn’t you just refund it?
Even if you passed the 2h window because of troubleshooting, Steam Support would probably still allow it if you explained you couldn’t get it to work at all
I tried, steam said NO!