Populares: Datos actualizados el 27 de octubre de 2026

Categorías

Internet1356
Comunicación321
Audio y vídeo898
Gráficos y diseño539
Ofimática y productividad1124
Programación3134
Inteligencia artificial529
Seguridad y privacidad385
Herramientas del sistema3114
Juegos523
Educación y ciencia239
Redes e informática284

CapFrameX Beta: descargar versiones anteriores

Frametime capture and analysis tool

CXWorld Monitorización y benchmarks #97 Monitorización y benchmarks

Aquí figuran 4 versiones de CapFrameX Beta, desde 7 de agosto de 2025 hasta la actual, 1.8.4.1. Cada una enlaza con los instaladores del propio desarrollador.

2025: 1 1 25 2026: 3 3 26
VersiónFechaTamañoArchivos
1.8.4.1Última versión 25 de enero de 2026 — 64 bits ZIPCualquier procesador ZIP
Notas de la versión
Release Notes
Bugfixes
- Capture files cannot be saved to network drives.
Runtime Requirements
- .NET 9 is now required for full feature support and optimal stability. Download here.
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
─────────────────┬────────────────────────────────────────────────────────────────────────────────┬─────────────────────────
Property │Description │Default
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
portable │Enables portable mode when true │true
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.config │Configuration files (AppSettings.json, overlay configs, sensor config, UI state)│./Portable/Config
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.captures │Capture recordings │./Portable/Captures
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.screenshots│Screenshot storage │./Portable/Screenshots
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.logs │Log files │./Portable/Logs
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.cloud │Cloud download directory │./Portable/Captures/Cloud
─────────────────┴────────────────────────────────────────────────────────────────────────────────┴─────────────────────────
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
─────────────────────────────────────┬─────────────────────────────────┬──────────────────────
Feature │Installed Mode │Portable Mode
─────────────────────────────────────┼─────────────────────────────────┼──────────────────────
Config storage │%AppData%\CapFrameX\Configuration│./Portable/Config
─────────────────────────────────────┼─────────────────────────────────┼──────────────────────
Captures sto
1.8.0.1 12 de enero de 2026 — 64 bits ZIPCualquier procesador ZIP
Notas de la versión
Release Notes
Enhancements & New Features
- Support Intel Panther Lake voltage sensors
- Added model IDs for Intel Arrow Lake-S Refresh (reserved)
- Added model IDs for Intel Core Ultra 300 Series (reserved)
- Full working portable mode
- Check for .NET 9 and Visual C++ Redistributables on app start
Bugfixes
- Overlay group control
Platform & Infrastructure
- Updated several Nuget packages
Runtime Requirements
- .NET 9 is now required for full feature support and optimal stability. Download here.
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
─────────────────┬────────────────────────────────────────────────────────────────────────────────┬─────────────────────────
Property │Description │Default
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
portable │Enables portable mode when true │true
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.config │Configuration files (AppSettings.json, overlay configs, sensor config, UI state)│./Portable/Config
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.captures │Capture recordings │./Portable/Captures
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.screenshots│Screenshot storage │./Portable/Screenshots
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.logs │Log files │./Portable/Logs
─────────────────┼────────────────────────────────────────────────────────────────────────────────┼─────────────────────────
paths.cloud │Cloud download directory │./Portable/Captures/Cloud
─────────────────┴────────────────────────────────────────────────────────────────────────────────┴─────────────────────────
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
─────────────────────────────────────┬─────────────────────────────────┬─────────────
1.7.7.15 1 de enero de 2026 — 64 bits ZIPCualquier procesador ZIP
1.7.6.8 7 de agosto de 2025 — 64 bits ZIPCualquier procesador ZIP
Notas de la versión
Update 2025/08/07
- New PresentMon version with ETW buffer overflow fix
Update 2025/08/04
New features
- Universal hybrid core detection for AMD (Performance + Dense cores) and Intel (Performance + Efficiency cores)
- Thread Affinity Controller working with AMD dense cores
- Support AMD Strix Point
- Experimental support Intel Nova Lake
image
Enhancements
- Eliminated lazy loading for capture files to resolve user-reported issues
- Performance optimization capture files management
- Performance optimization slider handling on Analysis tab (Real time update option)
image
Bugfixes
- Thread Affinity Controller fixed for Zen 5
New features
- Support Nvidia Blackwell
- Support AMD Strix Point
- Support PresentMon v2.3.1
- Frame time distribution chart
Important: This version is not compatible with Nvidia's Multi Frame Generation! We are working on a solution with Nvidia.
Blackwell support
image
Frame time distribution chart
image
Enhancements
- Lazy load capture files (aggregated file size > 512MB)
- Removed Windows Media Player dependency (NAudio library)
Bugfixes
- Fixed Zen 5 VID sensor readings
- Fixed frame time issues caused by ETW buffer overflow
When using BENCHLAB service, unzip the folder in a suitable installation folder like C:\Benchlab Service or D:\Tools, then run the .bat script as admin. Don't install the service from the Download folder. Install latest .NET 8 runtime.

Lo más popular en Monitorización y benchmarks

Ver todo
  1. VeyonMonitorización y benchmarks · Veyon Solutions
  2. Datadog AgentMonitorización y benchmarks · Datadog, Inc.
  3. windows_exporterMonitorización y benchmarks · Prometheus Community
  4. AlloyMonitorización y benchmarks · Grafana Labs
  5. LibreHardwareMonitorMonitorización y benchmarks · LibreHardwareMonitor
  6. DiskSpdMonitorización y benchmarks · Microsoft Corporation
  7. Mem ReductMonitorización y benchmarks · Henry++
  8. NTopMonitorización y benchmarks · gsass1
  9. MonitorianMonitorización y benchmarks · emoacht
  10. SnakeTailMonitorización y benchmarks · SnakeNest.com

Etiquetas

Compartir