Section: Rust

Every Rust player knows the feeling: you equip an AK, M249, or rocket launcher, and the bulky weapon model immediately blocks a quarter of your screen on the right. In a heated gunfight, that massive blind spot can easily hide a flanking enemy. In our testing of the client settings, we found a simple fix. If you want to pull your viewmodel back in Rust, press F1, enter graphics.vm_fov_scale false, and hit Enter. The crucial factor: your in-game Field of View must be set to 90, or you will barely see any difference. To revert to the default view at any time, run graphics.vm_fov_scale true. This guide covers verified methods to adjust your FOV, push your weapon model forward, and maximize screen visibility in Rust without hassle or ban risks.
Pushing your weapon model further away requires two adjustments: maxing out your field of view in the graphics menu and entering a single console command. If you leave your FOV at the default 70, the viewmodel will not budge—the camera frustum simply lacks the angle to scale it. The core command to pull your viewmodel back in Rust is graphics.vm_fov_scale false. Proper viewmodel positioning frees up nearly a third of your screen space, costs zero FPS, and leaves recoil patterns untouched.
Every playstyle requires a different view: open-field roamers need wide situational awareness, while monument fighters constantly peek right-hand angles. Instead of guessing, pick a proven setup tailored to your combat focus.
| Combat Scenario | Settings & Console Commands | In-Game Advantage |
|---|---|---|
| Maximum Field of View | graphics.fov 90 + graphics.vm_fov_scale false | Weapon model is pushed forward, clearing the right side of the screen for spotting targets faster. |
| Tactical Left-Hand Grip | graphics.vm_horizontal_flip 1 | Shifts the gun to the left so your weapon model never blocks targets when right-shoulder peeking. |
| Dynamic Viewmodel Toggle | bind z ~graphics.vm_fov_scale true;graphics.vm_fov_scale false | Instantly toggles between pulled-back hands for scanning and default view for iron-sight precision. |
Before adjusting your viewmodel, define your combat priorities. Unobstructed vision pays off especially when clearing tight monument loot rooms—see our for monument run routes where reaction speed decides every encounter.
Configuring your viewmodel in Rust takes less than thirty seconds. For players looking to stretch their viewmodel and pull back weapon hands, combining graphics.vm_fov_scale false with FOV 90 is the only reliable method. The engine renders first-person weapon models separately from world geometry, meaning your gun shifts forward without fisheye distortion or stretched terrain.

Press Esc, open Options, select Graphics, and move the Field of View slider all the way to 90. This controls your camera frustum; without it, viewmodel scaling will not activate.
Press F1 to open the developer console, paste graphics.vm_fov_scale false, and hit Enter. Your weapon will immediately compact and shift forward, clearing the bottom-right portion of your display.
If the iron sights on a Revolver or Hunting Bow feel too distant for precision shots, resetting is straightforward. Press F1 again and enter graphics.vm_fov_scale true to restore standard weapon positioning in seconds.
Knowing how to switch weapon hands eliminates the biggest disadvantage of right-hand peeks: slicing an angle around a tree or rock often leaves your gun model blocking the target. Flipping your gun to the left gives you an unobstructed sightline. Bullet trajectory remains identical because Rust fires projectiles directly from player eye coordinates—hitboxes and recoil patterns never change.

Switching to a left-handed grip is standard practice for right-angle peeking. Control your weapon side with these core commands:
Keep in mind that viewmodel flipping is purely client-side: other players looking at your third-person character model will always see you holding weapons right-handed. While switching hands gives you a cleaner right-hand peek, it won't reveal enemies hiding behind walls. If you want full situational awareness and zero blind spots across monuments, check out reliable with undetected ESP overlays.
Opening the console during a fight gets you killed. Mapping your viewmodel to a keyboard or mouse key lets you adapt on the fly. The trick is using the tilde prefix (~), which turns the command into an alternating toggle. Without the tilde, the engine executes both parameters at once and reverts back to default within the same millisecond.

To bind an alternating viewmodel toggle to a single key, open F1 and enter: bind z ~graphics.vm_fov_scale true;graphics.vm_fov_scale false. Pressing Z will now cleanly alternate between pulled-back and standard viewmodels.
To swap weapon hands behind cover on the fly, bind the flip command to a side mouse button: bind mouse4 ~graphics.vm_horizontal_flip 0;graphics.vm_horizontal_flip 1. This lets you alternate between left and right hands mid-sprint depending on your corner.
If you need that key for another action, unbind it cleanly using unbind z (replace Z with your chosen key). Never use clearbinds—that command wipes every single keybind in the game, including jump, sprint, and fire.
Relaunching Rust only to find your weapon model taking up half the screen again is frustrating. This happens when the game crashes or closes via Alt+F4 before dumping memory variables to disk. Locking your settings requires a single command and a quick file property check.

Follow these three steps to lock your configuration permanently:
Performance Tip: Never attach writecfg to movement keys or frequently spammed binds. Writing to your disk during intense firefights can cause noticeable micro-stutters and frame drops.
Outdated guides and forums still circulate non-functioning commands from legacy builds or entirely different engines. Entering them will not work and will clutter your console with syntax errors. We audited the most commonly recommended commands to separate working ConVars from useless myths.

| Console Command | Client Status | Actual Effect | Community Verdict |
|---|---|---|---|
| graphics.vm_fov_scale false | ✅ Working | Pushes the weapon model forward away from player view | Primary command to pull back hands in Rust |
| graphics.vm_horizontal_flip 1 / 0 | ✅ Working | Swaps hands (1 = left-handed, 0 = right-handed) | Official client-side hand switch toggle |
| graphics.fov 90 | ✅ Working | Expands camera field of view to 90 degrees | Required baseline for viewmodel scaling |
| writecfg | ✅ Working | Saves active settings to client.cfg and keys.cfg |
If your viewmodel is not updating, do not reinstall the game. Most issues come down to one or two overlooked settings and can be resolved in seconds. Here are the most common snags and straightforward fixes.
Issue 1: Entered the command, but the weapon didn't move.
The fix is simple: your Field of View in the graphics menu is set too low (often the default 70). Slide your FOV to 90, and the command will kick in immediately.
Issue 2: Viewmodel resets to default after restarting Rust.
The client failed to commit your config to disk before exit. Enter writecfg in the F1 console and make sure client.cfg is not set to Read-only in Windows Properties.
Issue 3: Your toggle bind only shows the default view.
You missed the tilde (~) prefix. Without it, the engine executes both commands simultaneously, defaulting straight back to your original view.
Issue 4: Console displays a syntax error.
Copy-pasting from a browser often introduces trailing spaces or curly quotation marks. Type the command manually in plain ASCII characters.
Every ConVar in the graphics.* family is a native client feature provided directly by Facepunch. Easy Anti-Cheat will never ban for using them, making these viewmodel binds 100% legal on all official and community servers. If you want a deeper look at what actually triggers account flags, read our .
Adjusting your viewmodel is purely cosmetic: bullets continue to fire from the exact center of your screen, while spray patterns and hitboxes remain untouched. However, PlayStation and Xbox players are out of luck: Double Eleven disabled the F1 console entirely in Rust Console Edition. On consoles, the only way to gain extra screen visibility is maxing out the standard FOV slider in the screen settings.
To pull back your weapon model, enter graphics.vm_fov_scale false into the F1 developer console. You must also set Field of View (FOV) to 90 in your in-game graphics settings. To restore default viewmodel scaling, enter graphics.vm_fov_scale true.
This happens because your base FOV is set too low: at default 70 FOV, the model shift is practically imperceptible. Open Options > Graphics, max out your Field of View to 90, and the stretched viewmodel effect will become visible immediately.
Open the F1 console and enter the alternating toggle string: bind z ~graphics.vm_fov_scale true;graphics.vm_fov_scale false (replace Z with your preferred key). After testing the bind, type writecfg to save it permanently to your config file.
Switching to a left-handed viewmodel is done via graphics.vm_horizontal_flip 1, while graphics.vm_horizontal_flip 0 returns the weapon to the right side. For single-key switching, use the toggle bind bind x ~graphics.vm_horizontal_flip 0;graphics.vm_horizontal_flip 1.
Optimizing your viewmodel eliminates massive blind spots and delivers a noticeable competitive edge in high-stakes firefights. For more game mechanics breakdowns and battle-tested software, browse our . Test these binds in your next session to enjoy cleaner sightlines and smoother gunplay.
| Prevents config reset on game restart |
| graphics.vm_fov 90 | ❌ Fake | Returns error: unknown numeric command | Variable does not exist in Rust |
| graphics.vm_horizontal_offset -1 | ❌ Fake | Console returns a syntax error | Fabricated command from unverified blogs |
| render.fov 90 | ❌ Obsolete | Not recognized by current game builds | Removed by Facepunch years ago |
| input.left | ❌ Fake | Not supported by the input system | Erroneous command with zero functionality |
As veteran players frequently emphasize in Steam optimization guides, stick exclusively to ConVars officially recognized by the active engine.
Settings reset when active memory variables aren't committed to your storage drive upon quitting. To lock them permanently, run writecfg in the F1 console and verify that client.cfg is not flagged as Read-only in file properties.
No. You cannot be banned for viewmodel ConVars. All graphics.* parameters are native engine commands built by Facepunch Studios and are 100% permitted across all official Easy Anti-Cheat protected servers.
No. You cannot enter console commands on consoles because Double Eleven completely disabled the developer console for players. The only way to increase screen visibility on TV displays is maxing out the standard Field of View slider in the main options menu.