PvP settings are about information, not frames
The FPS guide covers raw performance. This page covers the other half: what you can see and how fast you learn you hit something. In Rust fights are often decided by who reads the first hit correctly.
Crosshair and hit feedback
- Hit Cross: on. This is the recommended setup — you get confirmation feedback without a permanent reticle cluttering your screen.
- Static Crosshair: off if you rely on Hit Cross. Many players instead use an overlay such as Crosshair X for a consistent reticle across games.
- Show Blood: on. It gives additional feedback that you connected, which matters when you cannot see the target clearly.
- Hit notification level 2 in console (
hitnotify.notification_level 2) gives better hit feedback in combat.
Stop the screen from fighting you
These two are the biggest quality-of-life wins in a gunfight:
- Hurt Flash: off — removes the camera shake when you take damage.
- Limit Flashing: off — prevents sudden visual masking during damage effects.
In the Censorship menu, turning these off means a hit no longer blinds you at exactly the moment you need to return fire.
Awareness
- Compass Visibility: on — helps with orientation and callouts, which matters more in a team than in solo.
- Max Gibs: 0 — removes debris after destruction, so you can see through doors and walls when they are destroyed. This is a genuine tactical advantage, not just an FPS tweak.
- Grass Displacement: on — helps you read tracks and movement through grass, at a small performance cost worth paying in PvP.
Console binds that help in a fight
bind c +graphics.fov 90; graphics.fov 70— press C for a zoom effect, useful for spotting at range.graphics.vm_fov_scale false— “skinny weapon view”, so your gun blocks less of the screen.egs.enablelegs 0— removes your own legs from view.input.holdtime 0.1— reduces the delay on object interactions, so looting and opening doors respond faster mid-fight.inventory.quickcraftdelay 0— crafting responds immediately.input.bind F1 client.consoletoggle; combatlog; client.ping— one key for console, combat log and ping.
Sensitivity and mouse
Aim settings are personal, but the environment around them is not:
- Disable mouse acceleration in Windows — uncheck Enhance pointer precision so mouse movement is linear and muscle memory transfers.
- Keep your key binds consistent and backed up so you can re-import them if you reset settings.
- Use a high-performance or Ultimate Performance power plan so the CPU does not throttle mid-fight.
The tuning method that actually works
Do not paste someone else’s config and hope. Start from the base settings above, then:
- Join a low-population server or a quiet area.
- Turn off one visual feature — shadows, for example — and test again.
- Watch the frametime graph, not just average FPS, to catch stutters.
- If you still have headroom, selectively re-enable features that do not hurt performance.
- In combat, pay attention to whether visual clutter — effects, particles, glare — is interfering rather than helping.
Realistic expectations
Rust is poorly optimised on the Unity side, so even strong hardware dips on packed servers. 60+ FPS is comfortable and 100+ is the PvP target; below 30, shooting is practically impossible. Draw Distance and shadows are the two biggest levers if you need frames back.
Related guides
- Best FPS settings — the performance half
- How to get scrap fast
- Tech tree guide