![]() Maybe a bug maybe not but I'm almost certain it's some particular setting of feature otherwise the issue would be more widespread. I think it's some setting that's allocating too much memory. The same can also be added to the value of the variable named 'GRUBCMDLINELINUXDEFAULT' and either would work. Look for the line containing 'GRUBCMDLINELINUX' and edit it as follows. It's obvious the game can use a ton of resources yet is still playable on a Steam Deck which is very resource constrained for a typical gaming PC. Ipv6 can also be disabled by editing the grub configuration file. Though with FSR it might be more like an 1/8. ![]() at about 1/4 the resolution with DLSS Quality. That's all at low settings, no DLSS, ray tracing, etc. In an hour of play well into the game it never crashed. Even it's not, the game obviously isn't coming close to consuming that many resources. i sudo lsattr /etc/nf i sudo chattr -i /etc/nf chmod +w /etc/nf. My Deck running the very same Windows 11, the game runs about on level with SteamOS I think. On my gaming rig the game is using 16 GB VRAM and 32 GB RAM, but that's with everything on including DLSS 3. If what you're saying is true, then it's probably a bug because this issue clearly can't be the case on a Steam Deck. I wouldn't expect a game to need that many in the first place, but gamedevs sometimes surprise me. We know spam when we see it and will delete it. This means things like repetitious posting of similar content, low-effort posts/memes and misleading/exaggerated titles on link posts. We all need to support each other to help GNU/Linux gaming grow. 2) Type in your terminal sudo gedit /etc/nf and give enter (mind the space between gedit and /etc). If it's a link post, think about writing a comment to tell us more - the more you engage with us, the more we like it. Remember you are talking to another human being.ĭevs and content producers: If you've ported your game to Linux or created some GNU/Linux-gaming-related content (reviews, videos, articles) then, so long as you're willing to engage with the community, please post it here. Heated discussions are fine, unwarranted insults are not. What exactly did you do, and how, and with what version of what? How have you tried to troubleshoot the problem? Vague, low-effort tech-support requests may get removed. Include relevant details like logs, terminal output, system information. Tech-support requests should be readable by and useful to others. ![]() It is not (primarily) a tech-support forum. /r/Linux_Gaming is for informative and interesting gaming content, news and discussions.If you have MORE than enough RAM, set swap tendency to a MUCH lower value by running command to edit nf: sudo gedit /etc/sysctl. Set maximum performance in Nvidia X Server Settings -> PowerMizer.Ģ. In addition, to get much SMOOTHER Nvidia window dragging experience, you can also do:ġ. To check if previous changes work after reboot, run command: sudo cat /sys/module/nvidia_drm/parameters/modeset Finally update intramfs and reboot your machine. When the file opens after running the previous command, add following line and save the file. Type your password (no asterisks feedback) when it prompts and hit Enter.Ģ. Open terminal (either via Ctrl+Alt+T or by searching for ‘terminal’ from software launcher) and run command to create a new config file: sudo gedit /etc/modprobe.d/nf Screen tearing usually happens on Ubuntu Linux laptop that uses Prime to switch between NVIDIA and Intel drivers.ġ. For Ubuntu 18.04 users plagued by screen tearing issue while using NVIDIA proprietary drivers, this quick tutorial may help you via enable PRIME Synchronization on Optimus. What is the command you are using to open the /etc/nf file Probably is 'sudo gedit', right Try: sudo nano /etc/nf or. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |