- Status
- Offline
- Joined
- Mar 3, 2026
- Messages
- 421
- Reaction score
- 7
Got a nasty one here that's been stalling progress. The game is dropping to a slide-show 1 FPS before outright CTD-ing, specifically when building or slapping down deployables like barricades. It feels like a classic case of memory corruption or a race condition triggered by Unity's PhysX updates.
The Situation:
Crashes are somewhat random but almost always occur when interacting with the building system. Even with an external setup, I've noticed that PhysX revalidation on placeable objects can tank performance if not handled correctly.
Technical Details & Symptoms:
It definitely looks like the memory is getting cooked during the object instantiation phase. If the cheat needs a relaunch, it's likely something is hanging in the overlay or the driver-level communication isn't resetting properly after the game process dies.
Anyone else encountered this specific 1 FPS freeze when building with an external?
The Situation:
Crashes are somewhat random but almost always occur when interacting with the building system. Even with an external setup, I've noticed that PhysX revalidation on placeable objects can tank performance if not handled correctly.
Technical Details & Symptoms:
- Heavy freezing (dropping to 1 FPS) immediately preceding the crash.
- All writes are guarded, yet the game state seems to desync or corrupt.
- Cheat persistence: If the game crashes, the cheat becomes unresponsive and requires a full relaunch to re-hook or re-scan, suggesting stale handles or a corrupted internal state that doesn't clean up on process exit.
- PhysX revalidation: Tried disabling object revalidation when holding buildable items, but the instability persists.
I've already verified that guarding writes isn't the magic bullet here. If you're digging into the building plan logic or barricade placement, be aware that Rust's engine does a lot of heavy lifting with PhysX during these frames. Even externally, if you're reading/writing to offsets related to the local player's held entity during the placement animation, you might be hitting a pointer that's being invalidated by the engine.
It definitely looks like the memory is getting cooked during the object instantiation phase. If the cheat needs a relaunch, it's likely something is hanging in the overlay or the driver-level communication isn't resetting properly after the game process dies.
Anyone else encountered this specific 1 FPS freeze when building with an external?
