CapFrameX v1.7.5 beta

New features

• Support Intel Lunar Lake
• Support Intel Arc Graphics (130V, 140V)
• Experimental Support Intel Arc Battlemage
• New overlay real-time metrics

CapFrameX v1.7.4

New features

• Support AMD Zen 5
• Support Intel Arrow Lake
• Thread Affinity Controller compatible with Arrow Lake core layout
• PresentMon v2.2 with new Start-to-PresentReturn / PresentReturn-to-PresentReturn frame time measurement approach
• New CPU Busy metric which indicates the duration the CPU was engaged in processing the frame before presenting it
• Added TBP Sim for AMD RDNA2 graphics cards

Image source: VideoCardz

Enhancements

• PMD metrics as floating point numbers with one decimal digit

Bugfixes

• Exception handling AMD ADLX API calls

Info

With the new PresentMon version the frame time measurement approach has changed from Present-to-Present to Start-to-PresentReturn / PresentReturn-to-PresentReturn. Taken from the PresentMon release notes:

"The majority of metrics are changed to use the time that the CPU started working on a frame as the reference point instead of the present() call, with values that are more aligned to measuring the quality of graphics applications (e.g., latency and duration of interaction and displayed frames). See README-ConsoleApplication.md for more details."

Unwinder (the author of RTSS):

"There is no best or preferable method. Both have their own different usage cases. Frame-start-to-frame-start frametime graph can be used to validate framepacing quality of latency oriented framerate limiting modes (low latency SK limiter mode, async/back edge sync RTSS limiter modes, NV CPL framerate limiter etc). Such graph should become "flat" when such framerate limiting strategy is in use. Present-to-present frametime graph can be used to validate framepacing quality of framerate limiters prioritizing presentation timings adjustment (latent sync or normal framerate limiter in SK, front edge sync or scanline sync in RTSS). Such graph is expected to jitter if latency oriented framerate limiting strategy is in use, but become "flat" if framerate limiter prioritize presentation timings adjustment. You may also switch between these two modes to determine which framerate limiting strategy is used by some other third party framerate limiters or in-game framerate limiters."

CapFrameX v1.7.4 beta

Update 2024/11/2

• Thread Affinity Controller compatible with Arrow Lake core layout
• Added TBP Sim for AMD RDNA2 graphics cards

New features

• Support Intel Arrow Lake
• PresentMon v2.2 with new Start-to-PresentReturn / PresentReturn-to-PresentReturn frame time measurement approach
• New CPU Busy metric which indicates the duration the CPU was engaged in processing the frame before presenting it

Image source: VideoCardz

Enhancements

• PMD metrics as floating point numbers with one decimal digit

Bugfixes

• Exception handling AMD ADLX API calls

Info

With the new PresentMon version the frame time measurement approach has changed from Present-to-Present to Start-to-PresentReturn / PresentReturn-to-PresentReturn. Taken from the PresentMon release notes:

"The majority of metrics are changed to use the time that the CPU started working on a frame as the reference point instead of the present() call, with values that are more aligned to measuring the quality of graphics applications (e.g., latency and duration of interaction and displayed frames). See README-ConsoleApplication.md for more details."

Unwinder (the author of RTSS):

"There is no best or preferable method. Both have their own different usage cases. Frame-start-to-frame-start frametime graph can be used to validate framepacing quality of latency oriented framerate limiting modes (low latency SK limiter mode, async/back edge sync RTSS limiter modes, NV CPL framerate limiter etc). Such graph should become "flat" when such framerate limiting strategy is in use. Present-to-present frametime graph can be used to validate framepacing quality of framerate limiters prioritizing presentation timings adjustment (latent sync or normal framerate limiter in SK, front edge sync or scanline sync in RTSS). Such graph is expected to jitter if latency oriented framerate limiting strategy is in use, but become "flat" if framerate limiter prioritize presentation timings adjustment. You may also switch between these two modes to determine which framerate limiting strategy is used by some other third party framerate limiters or in-game framerate limiters."

CapFrameX v1.7.3 beta

Update 2024/06/10

• Support AMD Zen 5 Granite Ridge
• Fixed FPS counter showing values for wrong process when multiple processes were detected

New features

• No new features for now

Enhancements

• UI/layout improvements for low display resolutions

Bugfixes

• Fixed missing TBP sensor (ADLX) for AMD graphics cards
• Bugfix minimize CX to tray

Update 2024/02/23

• Bugfix NVML PCIe throughput sensors

CapFrameX v1.7.2

New features

• Updated PresentMon caputure service to v1.9.0, see PresentMon GitHub repository for more info.
• New metric: GPU Active Time (GPU Busy)
• GPU Active Time graph on Analysis tab. GPU Busy graph can be enabled via "Additional graphs".
• New overlay metrics: GPU Busy and GPU Busy Deviation. GPU Busy Deviation describes the deviation of GPU Active time from the frame time. The closer it is to 0% the more balanced the workload is.
• FPS <-> ms toggle on Analysis tab
• New real-time metrics: 1% and 0.2% Low Average
• More Powenetics v2 features
• PMD logs export (context menu)
• Mapping PMD data to frame time data points
• Smart data mapping via linear spline interpolation
• Real-time metrics reset button
• Updated AMD ADLX and Intel IGCL
• Optional ADL fallback (TBP Sim for RDNA2, Vega VRM temps etc.)
• Implementation network ping overlay entry
• Thread affinity controller (Intel hybrid architecture, AMD Ryzen with 2 CCDs)

Enhancements

• Performance optimization AMD ADLX readings
• Reset thread affinity to default when starting a new game
• Overlay entry showing current thread affinity state
• Better handling of integrated graphics (UHD Graphics and Iris Xe Graphics )

Bugfixes

• Bugfix detection error (Call of Duty MW2)
• Config files access exceptions (Moved folder from MyDocuments to AppData/Roaming)
• GPU PCIE Rx and Tx throughput unit

CapFrameX v1.7.2 beta

Update 2023/09/12

• Updated PresentMon caputure service to v1.9.2
• Bugfix detection error (Call of Duty MW2)

Update 2023/08/27

• Updated PresentMon caputure service to v1.9.0, see PresentMon GitHub repository for more info.
• New metric: GPU Active Time (GPU Busy)
  
• GPU Active Time graph on Analysis tab. GPU Busy graph can be enabled via "Additional graphs".
  
• New overlay metrics: GPU Busy and GPU Busy Deviation. GPU Busy Deviation describes the deviation of GPU Active time from the frame time. The closer it is to 0% the more balanced the workload is.
  
• FPS <-> ms toggle on Analysis tab
  
• Bugfix: GPU PCIE Rx and Tx throughput unit

Update 2023/07/15

• New real-time metrics: 1% and 0.2% Low Average

Update 2023/06/15

• More Powenetics v2 features
• PMD logs export (context menu)
• Mapping PMD data to frame time data points
• Smart data mapping via linear spline interpolation
• Real-time metrics reset button

PMD Analysis tab with export feature

Excel Export

Update 2023/03/25

• Updated AMD ADLX and Intel IGCL
• Better handling of integrated graphics (UHD Graphics and Iris Xe Graphics )
• Optional ADL fallback (TBP Sim for RDNA2, Vega VRM temps etc.)

Update 2023/03/08

• Reset thread affinity to default when starting a new game
• Overlay entry showing current thread affinity state

New features

• Implementation network ping overlay entry
• Thread affinity controller (Intel hybrid architecture, AMD Ryzen with 2 CCDs)

Thread Affinity

• Intel: default -> P-cores -> E-cores -> default
• AMD: default -> CCD0 -> CCD1 -> default

Warning: If a game has a large thread pool, forcing scheduling to half the number of threads can lead to increased context switches and thus noticeable frame times spikes. This was the case, for example, with Metro Exodus Enhanced Edition.

Toggle Thread Affinity

i9-12900K P-cores

i9-12900K E-cores

CapFrameX v1.7.1

New features

• AMD Radeon RDNA 3 support
• ADLX implementation (e.g. GPU TBP)
• Support Intel Raptor Lake (Alder Lake Refresh) with Model ID 0xBF: i5-13400(F), i5-13500
• TBP Sim Sensor for Intel Arc GPUs

Enhancements

• Adjustable frame time and frame rate line graph color
• Slightly adjusted window size to also fit 768p screens

Bugfixes

• Wrong system info on PMD tab
• When Run History was enabled, switching overlay configs showed the overlay entry even on configs where it wasn't enabled

CapFrameX v1.7.1 beta

New features

• AMD Radeon RDNA 3 support
• ADLX implementation (e.g. GPU TBP)
• Support Intel Raptor Lake with Model ID 0xBF: i5-1300(F)

Enhancements

• Adjustable frame time and frame rate line graph color

Bugfixes

• Wrong system info on PMD tab

CapFrameX v1.7.0

New features

• Powenetics v2 support
• Powenetics v2 real-time metrics + charts
• Powenetics v2 PMD data logging + analysis
• Powenetics v2 real-time overlay metrics
• Battery life overlay metrics
• Import Nvidia FrameView log files (DLSS 3 compatible)
• Calculation PC Latency on Analysis tab
• PC Latency graph on Analysis tab
• x% Low Average and Integral metrics
• Intel Arc VRAM bandwidth (Read and Write)

Enhancements

• UI and performance optimizations
• Stuttering charts auto zoom
• Configurable color overlay group name
• Improved ReBAR detection (D3D and Vulkan)
• Added host visible coherent memory counter: amount of video memory which can be directly accessed by CPU
• Smarter sensor config management when new hardware has been installed

Bugfixes

• Zen 4 sensor logging data load failure when iGPU is enabled
• Overlay update error real-time metrics
• Memory junction temp on Ada GPUs
• Deleting capture files unintentionally when drag & drop files within the folder tree (very rare).

Note

Powenetics v2 is not yet available! This feature is for devs and testers.

PMD overlay metrics

Nvidia FrameView log files with DLSS 3 frame times and PC Latency

Intel Arc VRAM bandwidth (Read and Write)

Improved ReBAR detection + visible coherent memory counter

CapFrameX v1.7.0 Beta

Update 10/03/22

New features

• Powenetics v2 support
• Powenetics v2 real-time metrics + charts
• Powenetics v2 PMD data logging + analysis
• Powenetics v2 real-time overlay metrics
• Battery life overlay metrics
• Import Nvidia FrameView log files (DLSS 3 compatible)
• Calculation PC Latency on Analysis tab
• PC Latency graph on Analysis tab
• x% Low Average and Integral metrics
• Intel Arc VRAM bandwidth (Read and Write)

Enhancements

• UI and performance optimizations
• Stuttering charts auto zoom
• Configurable color overlay group name
• Improved ReBAR detection (D3D and Vulkan)
• Added host visible coherent memory counter: amount of video memory which can be directly accessed by CPU
• Smarter sensor config management when new hardware has been installed

Bugfixes

• Zen 4 sensor logging data load failure when iGPU is enabled
• Overlay update error real-time metrics
• Deleting capture files unintentionally when drag & drop files within the folder tree (very rare).

Note

Powenetics v2 is not yet available! This feature is for devs and testers.

PMD overlay metrics

Nvidia FrameView log files with DLSS 3 frame times and PC Latency

Intel Arc VRAM bandwidth (Read and Write)

Improved ReBAR detection + visible coherent memory counter