Shared session

By @Aquiry

Z1 Battle Royale (H1Z1)

Oct 13, 2026, 05:16 PM · 2h 38min · 107 min gameplay

Detected by: system event · End: the game closed

Key takeaways

Bad session

Stutters cost a noticeable share of the playtime.

705 stutters (1052 slow frames including 106 freezes) · 103.7 s lost

Main cause: Game computation. The worst stretch cost 6.1 s of lost frames.

Pace set by the processor

The processor set the pace on 83% of the frames: it decides how many frames per second you get, not the graphics card.

Performance

FPS, lows and stutter breakdown

Frame timing

107 min active / 158 min total

Average FPS

279

Session average

1% low

142

Average of the worst 1% of frames

0.1% low

39

Average of the worst 0.1% of frames

Frame p99

5.9 ms

Time per frame, in the slowest 1%

16.7ms · 60 FPS33.3ms · 30 FPS0 s79 min157 min

Median frame time of each slice (ms) over the session. Red dots = slowest frame of a slice, when it clearly breaks from the session’s pace.

Slow frames (1052)

103.7 s lost
Game computation46(1.5 s)
Not enough RAM2(0.2 s)
Cause not identified2(0.1 s)

Breakdown of the first 50 stutters.

System state

CPU, GPU, VRAM averages and temperatures

Game CPU

?

27%

GPU

?

43%

CPU temp max

?

—

GPU temp max

?

79°

70° on average

CPU temperature not measured: advanced sensors (PawnIO driver) were off. Turn them on in the app: Dashboard › Repair sensors.

hot threshold · 83 °C GPU30 °C63 °C95 °C0 s79 min157 min

Graphics card over the session, peak of each slice. The dashed lines are the thresholds of the thermal summary.

Advanced sensors (PawnIO driver)

GPU fan max 2,122 RPMGPU power avg. 200 W

Measurement conditions

  • V-Sync: off
  • Loading hitches excluded: 257
  • Measurement cost: 0.4% of the processor
Pace set by the processor

The processor set the pace on 83% of the frames: it decides how many frames per second you get, not the graphics card.

VRAM peak

?

3.6 GB

Input lag p99

?

14.5 ms