I made a set of clean RTSS overlays, including a Performance Overlay built for benchmarking and testing new parts.

- Performance Overlay: FPS, 1% / 0.1% lows and frametime graph, plus full CPU and GPU stats (temp, load, power, clock, voltage, fan, VRAM, VRAM temp) and load graphs

- 8 designs in 4 themes: Dark, White, Clear and Float (no background at all)

- Ready for 1080p, 1440p, 3440x1440, 3840x1600, 4K, 5120x1440 and 5K2K, plus HYTE Y70 vertical screens

- One-click quick-install pack per resolution

- GPU limit warnings and a 12V cable monitor (No 12V versions too)

Needs RTSS + MSI Afterburner (+ HWiNFO for extra sensors). Free and open source, with a step-by-step setup guide with pictures:

https://github.com/realHfde/Apple-Style-Inspired-RTSS-Overlay

Happy to help if anything doesn't work. Reply here or open an issue on GitHub!

Update (Oct 4): the 1.9.2 beta is out! Release page

___

Hi everyone! Here's a look at what's new in CapFrameX 1.9.2, the open-source tool for capturing and analyzing frametimes (built on Intel's PresentMon). Here are the highlights:

PresentMon fixes (the main reason for this beta)

Some users reported CPU usage growing over time, frametime spikes and captures that stalled. CapFrameX now ships CX-PresentMon 2.6.1, its own build based on Intel PresentMon 2.6.0 (not an official Intel release). CSV output stays compatible with 2.6.0.

• App timing data that could pile up for the whole session is now cleaned up. That was the main cause of the CPU and memory growth Intel issue #695
• Turning frame generation off or switching to another one no longer blocks capture output.
• Extra hardening for GPU queue tracking with HAGS and for swap chain tracking.

CapFrameX now support Spanish, Russian and German

Yeah... some people thought this was exclusive to English speakers, but not anymore!

For the first time, the interface is translated. There are two separate selectors: one for the interface language and one for the OSD/overlay language. Switching takes effect immediately, no restart needed.

• Spanish (neutral): terms that gamers usually say in English (FPS, frametime, overlay, stuttering, 1% low…) are intentionally kept in English
• Russian, contributed by another community member.
• German, added right before the beta.

And there will probably be many more languages in the future.

In-game overlay is now the default

The in-game overlay is now the default for new configs and isn't marked experimental anymore. If you already picked a renderer, that choice stays.

If you benchmark: don't use the hook-free overlay for measurements. Hiding it can cause frametime spikes, and some AMD and Intel drivers have issues with DWM. Use the in-game overlay or RTSS, and check which renderer is actually active before you measure.

New installer

The installer was migrated to WiX Toolset v6 and got a refreshed look. Also:

• Uninstall: the cleanup now only runs on a real uninstall, not on a repair or an update.
• Repair: repairing the installation no longer reinstalls the Visual C++ redistributables.
• All binaries are signed, including third-party DLLs, so Smart App Control shouldn't block anything.

A more complete INFO tab (backported to version 1.9.1 as well)

• Software components: status of the PawnIO driver, PresentMon, RTSS and the Vulkan layer, with a color indicator and explanations on hover.
• Platform security: Secure Boot, Test signing, VBS and Memory integrity. Good to know, since VBS and Memory integrity can affect performance and runs should be compared with the same settings.
• "Copy system info" button: copies everything as text, handy for bug reports.

A more polished interface

• Every tab fits in a maximized 1080p window, no scrolling needed.
• Fixed several clipped labels and controls (Capture, Comparison, PMD, Sensor).
• Tab headers and dialog buttons adjust to the text length, so translations fit better.
• List columns no longer jump around while scrolling.

___

If you try the beta, the devs especially want reports about capture interruptions, CPU usage that keeps growing, or problems when switching frame generation. Include game, GPU, driver version and which overlay you were using.

Thanks to Dev for continuing to keep this project alive, and to all the contributors!!

CapFrameX 1.9.1 (v1.9.1.5, release channel):

• Restored the experimental in-game overlay with signed binaries.
• Brought back the bundled BENCHLAB service.
• Improved overlay compatibility, hardware information, and capture workflows.

This is a stable release; the in-game renderer remains experimental.

---

r/allbenchmarks reminder:

If you are asking for a specific CapFrameX-related issue or bug, please go and post here to get assistance:

https://github.com/CXWorld/CapFrameX/issues

Does anybody know?
If Nvidia FrameView 1%L is the same as Intel PresentMon FPS-Display 1%?

And does CapFrameX has it as well? Is it Real-Time P1 FPS? The numbers are slighlty different and it's difficult to tell.

Steam reviews can carry a hardware block, and I’ve been collecting them to build per-game hardware populations. Current corpus: 224,028 machines across 104 titles.
The finding: the share of players with 32GB or more of RAM is not one number. It runs from 25.0% to 88.5% across the 96 titles that clear my sample bar, while the pooled figure across all of them is 56.4%. The pooled number is the one usually quoted, and for most individual titles it is wrong in one direction or the other.
Method, so you can judge it:
• Only reviews carrying a hardware block are counted, one machine per review.
• A title is only drawn if it holds at least 600 machines. 9 of the 105 titles I hold fall below that and are excluded rather than shown thin.
• GPU strings are matched against an alias table that scores 98.7% on out-of-sample data; unmatched strings are kept raw rather than dropped silently.
• Every figure on the page carries the machine count it was computed over.
Full per-title table: https://1pct.net/findings
Caveat I would rather state than have found: reviewers are not a random sample of players. A review-writing population probably skews toward more engaged players, and I cannot measure that bias from inside this data. The spread between titles is the finding; the absolute level for any single title carries that unknown.
No ads, no affiliate links, no accounts, and nothing is stored from a visitor.

Does this build look like it's performing how it should?

https://www.3dmark.com/3dm/162879130?

New to benchmarking and don't really know what everything means.

I got this benchmark on my EVGA GTX 1060 3GB SC (with a manual Overclock applied). Is this silicon lottery or just a lucky benchmark? the OC mentioned is +150 core and +300 mem, with highest power and temp limits applied, as well as unlocked voltage control and a custom fan curve.

Hello everyone,

I just wanted to share a website I've been working on these past few weeks that allows users to submit how their PC performs while playing games.

There are around 10,000 games currently supported in the catalogue, along with 300 GPUs and around 800 CPUs to select your build from, as well as some Specific Device presets for devices like Handhelds. I haven't got all hardware parts listed, so if you do have any suggestions of parts to add, let me know. You can contact me through the contact form on the site or message me on Reddit.

Obviously, the data is 100% reliant on community-provided information, so accuracy can vary, and there aren't too many entries yet, but I thought it would be a good database to have rather than rely on publisher-provided system requirements to see if your PC can run a game.

If you want to check the site out, feel free to visit: https://www.canyouplayit.com/

I'd love it if we could get some more benchmarks on there so we can start building an accurate picture for people.

Thank you!

the double camera with independent air intake really improves the temps a lot, these are my temps after 2 tests of 10 min to max CPU and GPU load, and in games I went from playing with GPU 54 degrees and CPU 55-68 to GPU 52 degrees and CPU 44-54 degrees depending on the game.

https://images2.imgbox.com/93/17/oDX7r6A8_o.png

1080p result: 19502

Hardware: Intel 12700KF (stock) -- ASUS ROG STRIX B760-G D4 -- G.SKILL RIPJAWS 4000MHz CL18 -- ASUS DUAL RX 9060 16GB -- JONSBO Z20 black -- bequiet! SYSTEM POWER 10 550W -- DeepCool AG500BK ARGB -- Kingston Renegade G5 1TB
Software: Arch Linux (hardened kernel), KDE Plasma, Mesa open-source driver, XFS file system

Hey r/allbenchmarks,

I've been building a tool that tries to answer the question most of us Google before buying hardware: "What FPS will I actually get?"

It's called WhatFPS. You put in your GPU + CPU, pick a game, and it gives you an FPS estimate across 1080p / 1440p / 4K. It also has a community benchmark app where you can run a real bench on your rig and see how you stack up.

It's been built mostly by me and a handful of friends who've tested it so far.

No affiliate links, no paid tier, no hidden agenda — we just need more benchmark runs and honest feedback.

What I'm looking for:

• People who actually care about benchmark accuracy
• People who will be harsh if something is off
• Any rig welcome — old hardware and edge cases are especially useful

One heads up: The Windows benchmark app isn't code signed yet (EV cert is on the roadmap). You'll get a SmartScreen warning — click "More info" → "Run anyway". I'd rather be upfront about it than have you think something shady is going on.

If you're interested, drop a comment, join us on Discord (discord.gg/GHpGVGJMRD), or just go break it:

• FPS estimator: whatfps.com
• Benchmark app: whatfps.com/bench

Thanks for your time.

— Fred

Hey, i just built my new pc recently, did a 3DMark Timespy test, and the result is much lower than the average with the same GPU+CPU combination. I installed the newest drivers, but besides that i didnt change much. Is it something to worry about? Do most users overclock their system when using Timespy or why my result is so much worse? I am running the GPU in silent mode (not gaming mode) but afaik it shouldnt change much. Also im using a 360 AIO and a proper case.

Here is my link to the result, i hope some pros can have a look on it.

http://www.3dmark.com/spy/63680839

Thank you!

Hello everyone,

Is there any good free benchmark software that works on both Windows and macOS? I need it for a university project to compare performance between three computers, two of them are running Windows and the other is running macOS.

I’m looking for something cross-platform because I assume using different benchmark programs would give different results right?

Any recommendations?

Thank you!

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
- 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

Hi i just built a new personal gaming computer and i wanted to get some opinions on my score. its below average running in 3D Mark so i wanted to see if this was normal? My used 4070ti does run a bit hot so i tuned the fan curve to compensate for this based on a youtube video i watched and i plan to redo thermal paste and pads very soon. just wondering if the low score is due to voltage on the card being to low or high as with the new fan curve it doesn’t get to hot since fans go to 80-100% right after about 80c or so.

I recently installed CapFrameX for the very first time to analyze the system stats like CPU, GPU, TEMPS, USAGE etc while gaming since I am facing stuttering. I tried MSI Afterburner and I think the Stats bar was showing while in-game. But after CapFrameX, I am unable to grab that STATS BAR. I tried uninstalling, reinstalling both CapFrameX & RTSS but nothing is happening. I do able to get the seperate STATS window by going in RTSS and clicking SETUP, then PLUGINS, then "OverlayEditor.dll" plugin file which then shows me all the Stats which are currently selected inside CapFrameX.

Here is the picture demo of what I am talking about.

Am I doing something wrong? all the settings are enabled. You can see that even the OVERLAY is ON in CapFrameX.
RTSS was installed and nothing changed in it. The Show-On Screen Display Feature is also ON. Any suggestions where I might be doing something wrong?

I deleted profiles in the applications folder and restarted my PC after that I opened the app and pressed reset and after that I deleted the app with Revo uninstallers advanced cleaning option but idk if the settings that I did is reverted idk if its still applied in bios I have Rtx 4060 Laptop Gpu and a Dell G15 5530 gaming laptop

Hello, I built an open-source serverless runtime in Go.

I've included my initial benchmark results in the README, but since this is my first time benchmarking server infrastructure, I'd appreciate independent validation/critique from more experienced engineers.

If anyone is willing to benchmark it against platforms like Apache OpenWhisk or review my methodology, I’d love your feedback.

Repo: https://github.com/eswar-7116/glambdar

Benchmark scripts/methodology are included in the repo.

Thank you in advance.

can someone help me? My msi afterburner frame rate image is no longer a line but a square 😭

Enhancements & New Features

- Ryzen SMU support Zen 5

- Overlay profile compatibility mode

- New internal management stable sensor IDs

- Drag&Drop folders on the Comparison and Report tab

- Auto-enable PMD measurement

- Detailed process info, Capture tab

- RAM Game Used sensor

Bugfixes
- Capture files cannot be saved to network drives

- Invalid aggregation sensor data

- Invalid D3D sensors

- Sensor profiles not saved correctly

Platform & Infrastructure

- Fixed device path for the latest PawnIO driver 2.1.0