Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Everything cleared up once I re-installed, including the shader issue and some graphical fidelity loss.
Thanks for the info, will uninstall, wipe all steam game folders for First Descendant, reboot, reinstall, test & reply back.
Sometimes is ok, good quality & fps, get into combat gameplay and quality + fps drops like a stone, frequently crazy bad, looks almost like 8bit 420p.
After combat it returns to looking ok again.
Effectively impossible to play like this :(
Perhaps it's something else in my system, Mesa perhaps?
I was running mesa 24.1.5, or even .4 & now I notice its 24.1.6
Not keen on downgrading it though, even to test, as it will likely effect other applications.
I guess I am stuck playing in awful bloatware/spyware Windows until it magically fixes itself.
Will try it in a VM I guess :|
My systems specs in case they might help...
5950X
128Gb DDR4
Crosshair VIII Dark Hero
Powercolor Red Devil 7900 XTX
2x 2Tb Firecuda nVME
3x monitors all 2560x1440 @ 60Hz
I've use Proton Experimental (I've used this since launch), also tried 9.0.2 & 8.0.5
No errors in dmesg output.
I am using Steam-Native, (I think that's standard?) errors when launching from console (no idea if the link to img will work)...
Steam from Konsole[postimg.cc]
Am running on KWin (Wayland)
Absolutely zero issues with anything else on my system, & as I said TFD was running perfectly fine until a little over a week ago.
& VirtualBox is a no go because I can't do GPU passthrough :(
Back to Windows to play the game again for now I guess :(
what does that console window say when you 'start' the game? Steam isn't wayland native, it's x11 native, runing in a piss poor emulation layer. Try, if you can running the game on a native x11 session to see if 'that' may be the cause. xwayland is a pos even more so than wayland itself.
as for dmesg we're not looking just for errors. do a 'dmesg | grep amdgpu | less
dmesg | grep amdgpu > dmesg.txt
Part 2 to follow, 18k character limit!
Konsole output from steam-native & running the game (lengthy!)
Haven't tried X11 yet, last time I tried that it really messed up my monitors & I couldn't get back to a desktop at all & had to reinstall lol
If either were updated, downgrading and blocking that one update may help. Also try going to a more bleeding edge version might also help as it may be a bug already solved in a later version but the fix has not been back ported.
You also seem to have a problem with your steam install.
May need to reinstall steam itself. Don't worry, if you installed your games to say a different location than the default, all you would need to do is point the reinstalled steam at it. no re downloading needed.
Hmm, looks strange to me...
Garuda Settings Manager says kernel = linux-zen 6.10.5.zen1-1
But fastfetch says kernel = Linux 6.10.6-zen1-1-zen
I'll have to find out how to either update the Garuda listing or downgrade what Fastfetch is reporting.
Will also uninstall & reinstall Steam, & I guess Wine too.
I can just copy my installed Steam game directories to a backup then copy back after.
Will do the uninstall/reinstall in the morning now.
But want to sort the Linux Kernel first.
Not sure why I have 2 different versions being reported, I think it best to go with the one reported in Garuda Settings.
Will uninstall steam & wine, reboot, then install them again, reboot & test.
Issue still remain, seems slightly better, but that could just be this session and time of day.
Will try a different kernel in the morning.
I decided to try the Zen Fallback Initramfs kernel first.
Jumped into game & everything is 100% perfect again.
Tested for a couple of hours, all good.
uname -r = 6.10.6-zen1-1-zen
So same as before, so I am not quite sure what's changed.
As I understand it initramfs is a temp filesystem useful for overcoming things like kernel panics, so I'm not really sure of the next step to make.
Haven't rebooted yet though, I usually only do that when forced to by an update.