Garry’s Mod: Best autoexec.cfg for Prop-Hunt Performance

The secret to Prop-Hunt stability is forcing the engine to utilize Chromium (x86-64) branch optimizations. By default, GMod often ignores modern CPU architecture; this autoexec.cfg forces the “Game Core” and “Physics” tasks to communicate more efficiently, which is critical when 30+ props are colliding in a small room.

File Path

You must ensure you are using the x86-64 beta branch of Garry’s Mod (right-click GMod in Steam > Betas > Select x86-64 - Chromium + 64-bit binaries). Then, create the file here:

C:\Program Files (x86)\Steam\steamapps\common\GarrysMod\garrysmod\cfg\autoexec.cfg

Technical Note: To guarantee the config applies, add +exec autoexec.cfg to your Steam Launch Options, along with -high and -novid.

Optimized “Multicore & Physics” Block

Copy this into your autoexec.cfg. This configuration enables experimental multicore settings that drastically reduce “Lag Spikes” when props are damaged or moved.

Parameter	Recommended Value	Technical Purpose
gmod_mcore_test	1	The “Master Switch” for modern multicore rendering in GMod.
mat_queue_mode	2	Forces the material system to use a separate thread for drawing.
cl_threaded_bone_setup	1	Offloads skeletal animations (player models) to extra cores.
cl_interp_ratio	2	Use 2 for Prop-Hunt to avoid “jittery” prop movement on high-ping servers.
r_threaded_particles	1	Prevents FPS drops during explosion or smoke effects.

// --- Multicore Rendering (The 2026 Performance Core) ---
gmod_mcore_test 1
mat_queue_mode 2
cl_threaded_bone_setup 1
cl_threaded_client_leaf_system 1
r_threaded_client_shadow_manager 1
r_threaded_particles 1
r_threaded_renderables 1
r_queued_ropes 1
studio_queue_mode 1

// --- Network & Prop Interpolation ---
rate 786432
cl_cmdrate 66
cl_updaterate 66
cl_interp 0
cl_interp_ratio 2 // Set to 2 for smoother prop movement
cl_lagcompensation 1

// --- Performance & Visibility ---
fps_max 0
m_rawinput 1
mat_specular 0 // Disables "shiny" surfaces to make hiders easier to spot
r_drawmodeldecals 0 // Disables blood/bullets on props to save CPU
r_3dsky 0 // Disables the background skybox for a massive FPS boost
menu_cleanupgmas // Clears unused addon memory on startup
host_writeconfig

HowTo: Engineering the Ultimate Prop-Hunt Setup

To reach peak efficiency on GameEngineer.net, pair your .cfg with these 2026 engineering steps:

1. The 64-Bit Requirement: You must be on the x86-64 branch. Without it, the game is capped at 4GB of RAM, and the gmod_mcore_test command will frequently cause crashes during high-action rounds.
2. Addon Cleanup: In the console, type menu_cleanupgmas. This deletes local data for addons you’ve unsubscribed from but that are still haunting your garrysmod/addons folder and eating “File Search” CPU cycles.
3. Shadow Complexity: In advanced video settings, set Shadow Detail to Low. In Prop-Hunt, dynamic shadows on props are recalculated every time a prop moves even a fraction of an inch, which can cripple your frame-time.
4. Flashlight Lag Fix: If your game freezes when you turn on your flashlight, it’s usually due to a conflict with mat_depthbias_shadow_v2. The r_threaded_client_shadow_manager 1 command in our config is designed to fix this by threading the shadow map calculation.
5. Disable “Aero” & Overlays: GMod’s renderer is extremely sensitive to overlays. Disable Steam Overlay and Discord Game Detection to shave off $\approx 5\text{ms}$ of input latency.

Technical Explanation: Multi-Core vs. Entity Overload

Garry’s Mod was built in an era where CPUs had one or two cores. In a typical Prop-Hunt match, the “Main Thread” has to handle Lua scripts, Physics collisions, and Rendering calls simultaneously. When a Seeker throws a grenade into a room full of props, the physics engine (VPhysics) creates a “bottleneck” on that single thread.

By forcing mat_queue_mode 2 and gmod_mcore_test 1, we are essentially “un-bottlenecking” the CPU. The Material System (textures, shaders) is pushed to Core 2, while Bone Setup (player animations) goes to Core 3. This leaves the “Main Thread” free to handle the intensive Prop-Hunt Lua scripts and physics, preventing the “screen-freeze” that usually happens during a chaotic hide-and-seek encounter.