Release Notes

Enhancements & New Features

• Support Intel Nova Lake + ES, Bartlett Lake, Emerald Rapids, Wildcat Lake
• New NVIDIA limit sensors
• Per-game VRAM sensors
• AMD GPU fan duty sensor
• SSD sensors
• Intel memory/uncore clock sensors incl. PTL model 0xD5
• PMC Reader project integrated
• MCP server implementation
• Removed stutter metrics from FPS graph, display times used for moving averages, reworked threshold and variance charts
• Adjusted piechart layout
• Removed GPU Power Load as default sensor

Bugfixes

• Duplicated GPU memory sensor entries
• Default sensors + new IsGroupNameCompatible helper
• Integer division in NvidiaGpu.cs
• Y-axis boundaries in frame time graph
• PMC Reader DRAM latency

Platform & Infrastructure

• ADLX 1.5 update
• IGCL update
• FrameView fully removed (project + Jenkins)
• Updated NuGet packages
• New overlay config migration test for NV Mobile + Intel

Runtime Requirements

• .NET 9 is now required for full feature support and optimal stability. Download here.

MCP Server: Setting up Claude Code communication

CapFrameX ships an in-process Model Context Protocol server hosted by CapFrameX.exe. Once registered with Claude Code, the assistant can read captures, compute statistics, query the live system, and diagnose capture issues. The endpoint exists only while CapFrameX is running.

Setup

1. Find the port. Open %appdata%/CapFrameX/Configuration/AppSettings.json and read WebservicePort (default 1337; CapFrameX falls back to a free port if it's taken).

2. Register with Claude Code (one-time, user-scoped):

   claude mcp add -s user capframex --transport http http://localhost:<port>/mcp

3. Verify:

   claude mcp list

   Expected: capframex: http://localhost:<port>/mcp (HTTP) - ✓ Connected

In an active session, /mcp shows live status and the CapFrameX tools become available to the model.

Troubleshooting

• Disconnected / connect failure — CapFrameX isn't running, or the port changed since you registered. Re-check WebservicePort, then:

  claude mcp remove capframex
  claude mcp add -s user capframex --transport http http://localhost:<new-port>/mcp

• Tools missing in the model — start a new Claude Code session; existing sessions don't pick up newly added servers.
• Disable entirely — set McpEnabled to false in AppSettings.json and restart CapFrameX.

All v1.8.5 tools are read-only; the endpoint binds to localhost without auth.

CapFrameX Portable Mode

CapFrameX now supports a portable mode that allows the application to run entirely from a single folder without writing to system directories. This is useful for running from USB drives, network shares, or keeping multiple isolated installations.

How It Works

Portable mode is activated by placing a portable.json file in the same directory as the CapFrameX executable. When the application starts, it checks for this file and redirects all data storage to paths relative to the application directory.

Key Features

• Self-contained: All configuration, captures, screenshots, and logs are stored relative to the application folder
• No registry modifications: The application doesn't write to the Windows registry in portable mode
• No system folder usage: Bypasses %AppData% and Documents folders entirely
• Configurable paths: All storage paths can be customized via portable.json

portable.json Configuration

Create a portable.json file in the CapFrameX application directory with the following structure:

{
  "portable": true,
  "paths": {
    "config": "./Portable/Config",
    "captures": "./Portable/Captures",
    "screenshots": "./Portable/Screenshots",
    "logs": "./Portable/Logs",
    "cloud": "./Portable/Captures/Cloud"
  }
}

Configuration Options

All paths are relative to the application directory. You can use ./ or .\ prefix, or just the folder name.

Requirements

When running in portable mode, the following dependencies must be installed on the system:

• .NET 9.0 Desktop Runtime (x64) - Download
• Visual C++ 2015-2022 Redistributable (x64) - Download

The application will check for these dependencies on startup and display a message if any are missing.

Creating a Portable Distribution

1. Copy the CapFrameX application files to a folder
2. Create a portable.json file with the configuration above
3. (Optional) Pre-create the Portable subdirectory with: Config, Captures, Screenshots, Logs
4. The application is now portable and can be moved to any location

Behavior Differences

Notes

• Settings configured in portable mode are stored in the portable config folder and won't affect or be affected by an installed version
• The portable.json file must be valid JSON; if parsing fails, the application falls back to installed mode
• Directories are automatically created if they don't exist

Troubleshooting & Known Issues

The following tips address the most common issues reported by users and can help resolve stability, overlay, and capture-related problems efficiently. We recommend working through them in order if you encounter unexpected behavior.

1. Ensure you are running the latest version
   If you experience application crashes or unstable behavior, verify that you have installed CapFrameX v1.8.4 or newer. Many known issues have been resolved in this patch. If you were previously using version 1.7.7, we recommend uninstalling CapFrameX before installing the new version.

2. Reset application settings
   In some cases, corrupted or outdated configuration files may cause problems. Deleting
   %appdata%/CapFrameX/Configuration/AppSettings.json
   will reset CapFrameX to its default settings and often resolves startup or UI-related issues.

3. Reset overlay configuration files
   If overlay-related problems persist, try deleting the overlay configuration files located at
   %appdata%/CapFrameX/Configuration/OverlayEntryConfiguration_(0/1/2).json.
   These files will be recreated automatically on the next application start.

4. Restore missing or zero-value overlay entries
   When overlay entries are missing or display constant zero values, open the Overlay tab and use the Reset button to restore all overlay entries to a valid default state.

5. Fix incorrect overlay entry order
   If the order of overlay entries appears inconsistent or unintentionally rearranged, use the Sort button in the Overlay tab to restore a clean and logical ordering.

6. Resolve frametime anomalies after updates
   In rare cases, existing background capture processes can interfere with CapFrameX after an update. If you encounter frametime issues, close all running PresentMon processes before installing or launching CapFrameX v1.8.4 release.

7. Avoid conflicts with other monitoring tools
   Applications such as HWiNFO or AIDA64 that implement their own FPS or frametime metrics may conflict with CapFrameX’s capture service, as they also rely on PresentMon-based mechanisms. Disabling overlapping FPS or frametime monitoring features in those tools is strongly recommended when using CapFrameX.

Known Limitations

• PC latency metric may return invalid values (NaN) under specific conditions.