Star Citizen 3.16 PTU - Origin 400i Size 4 Load-out Combat Testing

Save
3 years ago
32
Star Citizen Linux Lutris DXVK WINE GloriousEggroll-proton-GE

======================================================
———
System Specs
----------------------
OS: Garuda Linux
Host: X570 AORUS MASTER -CF
Kernel: 5.15.2-zen1-1-zen
DE: Plasma 5.23.3
CPU: AMD Ryzen 9 3950X (32) @ 3.5GHz
GPU: AMD Radeon RX 6900 TX
Memory: 64GiB

Capture Card: Blackmagic Design DeckLink Quad HDMI Recorder PCIe Card
Capture Software: OBS 26.1.0
Bit Rate: 27000 Kbps
Game Play Resolution: 4K (3840 × 2160) Very High
Capture Resolution: 3K (2880 × 1620)

Live Stream Resolution: 1080p
Full Build Details

https://builds.gg/builds/scar-2-0-23547
======================================================

Get Star Citizen
CIG Site:
https://robertsspaceindustries.com/

Use the following referral code when purchasing a Star Citizen
game package to get 5,000 UEC to spend in Voyager Direct:

REFERRAL CODE: STAR-FTJK-QRC5

Join Star Citizen Linux Users Group
https://robertsspaceindustries.com/orgs/LUG

Discord:
https://discord.gg/meCFYPj

For more advice and information on playing Star Citizen in Linux

======================================================

Get Lutris
Lutris Site:
https://lutris.net/

Once Lutris is installed, install SC from Lutris script

Lug-Helper

Run pre-flight checks using Lug-helper either from
GitHub: https://github.com/starcitizen-lug/lug-helper
or
Arch AUR: https://aur.archlinux.org/packages/lug-helper/

Once SC is installed you can use the LUG WINE runners from
DevNull:
https://github.com/gort818/wine-sc-lug/releases

NOTE FSYNC COMPATIBLE KERNEL REQUIRED:
Ubuntu/elementary OS/Pop!_OS users can check out XanMod for an fsync compatible kernel

======================================================
Increase the sysctl option vm.max_map_count to prevent
crashes due to memory allocation limits in areas with
lots of geometry:
Note I am running at 4K on 64GB RAM so my setting is 2100000000
For anyone running 1440p or 1080p with upto 32GB RAM use 16777216

sudo nano /etc/sysctl.conf
enter the sysctl option vm.max_map_count

vm.max_map_count = 2100000000

sudo nano /etc/sysctl.d/20-max_map_count.conf
enter the sysctl option vm.max_map_count to prevent crashes
due to memory allocation limits in areas with lots of geometry
vm.max_map_count = 2100000000

sudo nano /etc/systemd/system.conf
delete # from the line "DefaultLimitNOFILE" and set value to
DefaultLimitNOFILE=2100000000

sudo nano /etc/systemd/user.conf
delete # from the line "DefaultLimitNOFILE" and set value to
DefaultLimitNOFILE=2100000000

To temporarily increase this value enter this command in a terminal
sudo sysctl -w vm.max_map_count=2100000000

Output: vm.max_map_count = 2100000000

more /etc/systemd/system.conf | grep NOFILE
======================================================

Loading comments...