PartsLife run viewer — sensor graphs and FPS overlay

How to use

1. In PartsLife, record a test (the “Test recording” view). It writes run-<ID>.json and sensors-<ID>.csv to Documents\PartsLife\runs.
2. Drop both files together above. The CSV name must match stream.file in the JSON. A run that was cut short is shown as “ended early”.
3. Read the capabilities table first: items that could not be read (for example CPU temperature, which needs a driver) are empty, not guessed.
4. To overlay an FPS log, save it in the FPS log analyzer (with the run ID or the start time), then pick it here. Align it to a marker if the start time is only an estimate.
5. If PartsLife’s AI export text is present (in the JSON or as a .txt/.md you add), it is shown as written. This tool never calls an AI.

Worked example

Example (all numbers are examples): a 10-minute run shows GPU temperature rising from 45 °C to 78 °C while the clock sits at 2,700 MHz; a saved FPS log overlaid in the same minutes shows 144 FPS falling to 130 FPS at the same time. That is two things that happened together — it does not say one caused the other.

Limits

• It displays what PartsLife recorded. It does not diagnose faults, guarantee that a voltage or temperature is safe, or tell you to change protections.
• Time sync: sensors are 1-second samples on the PC’s clock. A PresentMon CSV has no wall-clock time, so an FPS log’s start is estimated (seconds to tens of seconds of error); aligning to a marker is accurate to when the marker was pressed.
• CPU temperature, core voltage, fans and motherboard values are not read in this version; Intel GPU temperature/clock/power are not read either.
• Files are read in this browser and not sent anywhere. Saving stores only a small record (run ID, times, GPU names, build code) in this browser.
• This page is not indexed by search engines: it shows nothing without your own files.

Your inputs and results stay in this browser. Nothing is sent to a server.