---
title: How They Built the Pyramids: Co-Op Desync & Lag Solutions
description: Multiplayer stability fixes for How They Built the Pyramids: resolving peer disconnects, dropped stone blocks, and physics desync issues.
url: https://howtheybuiltthepyramids.wiki/co-op/co-op-troubleshooting/
---

### Quick Summary: Resolving Multiplayer Lag & Desync

Physics desync and floating blocks in **How They Built the Pyramids** occur when peer clients drift out of synchronization with the host. To fix floating blocks instantly, have the host press **F5 to force an engine resync**. Always **cap framerate at 60 FPS** in options to stabilize physics tick calculations. The player with the fastest single-core CPU and wired Ethernet should host, and builders should avoid placing [conveyor splitters](https://howtheybuiltthepyramids.wiki/automation/splitters-and-filters/) across 16×16 chunk borders.

- If stone blocks appear floating or desynced, have the host press F5 to force sync.

- Cap world framerate at 60 FPS in multiplayer options to stabilize physics simulation.

- Host on the PC with the highest single-core CPU frequency and wired Ethernet.

- Avoid placing conveyor junctions directly across multiplayer chunk borders.

## How They Built the Pyramids Multiplayer Connection Troubleshooting

In 8-player cooperative lobbies, the host machine simulates rigid body physics for hundreds of moving limestone monoliths, dozens of [Shabti helpers](https://howtheybuiltthepyramids.wiki/shabtis/market-and-hiring/), and active [32 RPM drive shafts](https://howtheybuiltthepyramids.wiki/automation/shafts-and-rpm/). While developer [Pattez Games](https://store.steampowered.com/app/5458210/How_They_Built_the_Pyramids/) optimized netcode in Hotfix v1.0.3, packet loss or CPU throttling can still cause noticeable latency.

| Multiplayer Issue | Visual Symptoms in World | Underlying Network Cause | Immediate Actionable Fix |
| --- | --- | --- | --- |
| **Floating Block Desync** | Stones hover frozen mid-air; cannot be picked up or placed | Host-client physics state desync after high-speed drop | **Host presses F5 key** to force broadcast full snapshot |
| **Conveyor Belt Jitter** | Blocks vibrate or clip through conveyor belt rollers | Client framerate fluctuating above 120 FPS vs 60 Hz physics | Enable 60 FPS Framerate Cap in graphics options |
| **Ghost Cart Rolling** | Empty stone transport carts roll backwards spontaneously | Incline ramp slope calculation mismatch between peers | Rebuild ramp with [cleated reed belts](https://howtheybuiltthepyramids.wiki/automation/conveyor-belts/) |
| **Shabti Worker Path Freeze** | Helpers gather around Work Post without moving | Pathfinding navigation mesh saturation | Pick up and re-plant the [Work Post banner](https://howtheybuiltthepyramids.wiki/shabtis/work-posts/) 2 tiles away |
| **Guest Join Timeout** | "Connecting to Steam P2P Host..." hangs indefinitely | Strict NAT type or blocked UDP socket relay | Restart Steam on both ends; check Windows Firewall port rules |

For general game startup errors and DirectX 12 driver updates, refer to our primary [Troubleshooting & Fixes Guide](https://howtheybuiltthepyramids.wiki/game/troubleshooting/).

## How They Built the Pyramids Floating Block Physics and Resync Keybind

The custom physics pipeline in How They Built the Pyramids operates on a host-authoritative model. When a guest player drops a block, the client predicts the fall trajectory while transmitting the action to the host:

### The F5 Force Resync Workflow:

- **Identify Desync:** If a stone block appears hovering mid-air or if an attached casing block will not snap to Course 1, notify the host.

- **Host Presses F5:** The host PC presses the **F5 function key**. The game pauses physics simulation for 150 milliseconds.

- **World Snapshot Broadcast:** The host serializes the exact XYZ coordinates and velocity vectors for all 23,426 potential block slots and broadcasts them across Steam P2P sockets.

- **Client State Re-alignment:** All guest machines instantly update their local scene graph. Frozen blocks snap to the nearest valid terrain, and building resumes smoothly.

If an individual player becomes physically pinned inside geometry, remember that typing `/unstuck` in chat safely displaces their character.

## How They Built the Pyramids Host PC Optimization and Chunk Boundaries

To prevent netcode lag in large-scale 8-player cooperative megalopolises, observe these structural guidelines:

- **Avoid Chunk Border Crossings:** The game world is partitioned into 16×16 tile simulation chunks. While straight conveyor lines cross chunk borders seamlessly, complex machinery like [3-way splitters and priority mergers](https://howtheybuiltthepyramids.wiki/automation/splitters-and-filters/) should be placed entirely within a single chunk to avoid boundary coordinate rounding errors.

- **Host Hardware Selection:** Always host on the PC with the highest single-core CPU frequency and at least 16 GB of RAM, as detailed in our [System Requirements Guide](https://howtheybuiltthepyramids.wiki/game/system-requirements/). The host PC manages AI pathfinding for all [Shabti helpers](https://howtheybuiltthepyramids.wiki/shabtis/market-and-hiring/).

- **Wired Ethernet Connection:** Never host an 8-player session over unstable 2.4 GHz Wi-Fi. A wired Ethernet connection eliminates packet jitter and ping spikes during intense building sprints.

Explore smooth squad coordination techniques in our [Co-Op Team Building Strategies Guide](https://howtheybuiltthepyramids.wiki/co-op/building-strategies/).

## How They Built the Pyramids Co-Op Desync FAQ
Why do stone blocks appear floating or frozen mid-air in co-op? Floating blocks indicate network packet loss during rigid body physics state handoffs; having the host press F5 forces an immediate world resynchronization across all connected peers.

How does capping framerate at 60 FPS reduce multiplayer desync? In physics-driven games, variable framerates cause delta-time calculation drift; capping at 60 FPS locks physics ticks at 50 Hz, ensuring identical simulation on all client machines.

Why should conveyor junctions avoid multiplayer chunk boundaries? Placing rapid conveyor splitters across world chunk seams can cause coordinate rounding jitter; aligning junctions within a single 16x16 tile chunk ensures flawless stone routing.

What should a guest player do if they cannot interact with machines? If your character cannot pick up blocks or toggle waterwheels, open chat and type /unstuck or have the host re-verify your Builder permissions in the session menu.

## How They Built the Pyramids Multiplayer Netcode Sources

All netcode telemetry, F5 resync protocols, and chunk boundary guidelines verified against game patch v1.0.3:

- **Source 1:** Official Hotfix v1.0.3 Patch Notes — Multiplayer block desync and conveyor stability fixes.

- **Source 2:** In-Product Steam P2P Socket Telemetry & F5 Synchronization Handler — Pattez Games (Pattez Games).

- **Source 3:** Steam Community Cooperative Troubleshooting Discussions — Community tested 60 FPS framerate cap fixes.

Return to the [Multiplayer Setup Guide](https://howtheybuiltthepyramids.wiki/co-op/multiplayer-setup/) or check all systems in the [Co-Op Hub](https://howtheybuiltthepyramids.wiki/co-op/).
