Instructions:
Download the archive: https://drive.google.com/file/d/1fW38TwHOMe9QIhWqPf15JwbiFjdxLy5I/view
Extract it into the root folder of the game (Steam → Rust → Browse local files). After extraction, the maps and demos folders should appear in the root directory (if they weren’t there already).
Open the “Maps” folder and find the newly added file with "XXX" in its name.
Replace the Xs with the current devblog number (you can figure it out by looking at nearby files. At the time of this post, it’s "269", after tomorrow update it will be changed to "270").
If the number in the filename doesn’t match the devblog version, the demo will either freeze during the heightmap loading or the character will fly through the ground.
Here is the correct filename as of JULY 2025 UPDATE:
proceduralmap.4000.1.269.map
Here is the correct filename as of AUGUST 2025 UPDATE:
proceduralmap.4000.1.270.map
Launch the game and enter the following command into the console:
client.benchmark_demo woodcock_bm*
Wait 3–4 minutes for the test to complete.
Open the benchmark folder (it will appear in the game’s root directory after the test). Inside, you’ll find data on the average FPS during the benchmark.
* THE BUILT-IN BENCHMARK IS BROKEN IN JULY UPDATE!
Hopefully, it’ll be fixed in the global patch, but for now the only way to run the demo is:
demo.play woodcock_bm
FPS won’t be measured automatically this way, but you can track it using third-party software (RTSS / FRAPS / CapFrameX ...). Other than that, it works the same.
Let’s thank the devs for killing a feature that worked for years ❤️
Tilja
2025-08-15 17:23:00 +0000 UTCWoodcock
2025-08-10 09:56:31 +0000 UTCEzO-
2025-08-10 09:30:36 +0000 UTCEzO-
2025-08-07 05:49:54 +0000 UTCDavid
2025-08-07 01:19:35 +0000 UTC