Как повысить FPS в Rust и убрать фризы

How to measure FPS without random spikes

1. In F1, type perf 1 for FPS only or perf 4 for FPS, memory, and ping. You can hide the stats with the command perf 0.
2. Load into the familiar server, wait for the environment to load, and choose a repeatable route for 60 seconds.
3. Record the resolution, settings, FPS limit, VSync status, and test date. Change only one parameter between tests.
4. Make three runs before and after. If a fight, base loading, or background application interferes once, repeat that run.

Where to start with the settings?

This is a trial and error process, not a universal preset. Save your current settings and revert the parameter if it affects visibility without providing consistent gains.

• Shadows and water reflections: start by lowering one graphics setting and compare the FPS in the same scene.
• Textures: lower them primarily in case of insufficient video memory or loading pauses. Minimal quality itself does not guarantee more FPS.
• Scaling: if the game offers DLSS or another option for your graphics card, start with Quality. Compare the sharpness of moving targets with native resolution.
• Resolution: temporary decrease helps to check the impact of GPU load. For regular gameplay, assess both performance and image clarity.
• Limit FPS and VSync: do not change them between measurements. Once the test is done, choose a comfortable limit considering your monitor and frame stability.

Memory, SSD, and Page File

If freezes coincide with memory usage, check background programs and texture quality. Facepunch recommends SSD and Windows automatic page file management. After changing system settings, restart your PC and repeat the same route. Disabling the page file may worsen the situation.

What has changed in the 2026 updates

In June, Rust received new player models and animations. In October, developers removed duplicated hand meshes and reported saving around 100 MB of memory. This is a client-side change, not a command for the config; it does not promise a fixed increase in FPS. After major patches, re-run benchmarks instead of transferring old results.

• GPU Skinning Test - a separate test branch from the Facepunch support guide from March 2026 for issues with weapons in hand. Check the relevance of the branch on Steam; if there are any problems with launching, return to the regular one.
• Do not use a bundle of launch options, gc.buffer, or physics commands from someone else's config without a clear reason and a recorded value for rollback.
• If the FPS remains stable but the characters move in jerks, compare the ping and connection. This is a separate check from the graphics quality.