PC Building Simulator 2: Fixing the 3DMark Calculator — A Detailed Guide
PC Building Simulator 2 (PCBS2) players rely on accurate benchmarking tools like the in-game 3DMark calculator to estimate GPU performance, price-to-performance, and to validate builds. When the 3DMark calculator is producing incorrect or inconsistent results it can mislead purchasers and frustrate players. This post explains likely causes, step-by-step fixes, and preventative tips — suitable for modders, players, and content creators who want reliable metrics.
Why the 3DMark calculator can be wrong
- Outdated or mismatched performance data: The calculator uses a database linking GPU models to benchmark scores. If that database is outdated or contains incorrect entries, results will be off.
- Driver or compatibility modifiers not applied: In real-world benchmarks, drivers and game-specific optimizations change scores; the simulator may fail to simulate those modifiers.
- Incorrect scaling for CPU/GPU bottlenecks: The calculator might assume linear scaling or ignore CPU limitations, causing overestimates on weaker CPUs or underestimates on powerful ones.
- Wrong normalization or unit conversion: Mistakes in normalizing scores across architectures (e.g., comparing different API backends) produce skewed numbers.
- Corrupted game files or mods interfering: Mods that change GPU names, clock multipliers, or prices can break lookup logic.
- Localization or parsing errors: Different number formats (comma vs period) or text encoding can make the calculator misread values.
When to report a bug upstream
- If the issue persists after disabling mods and verifying game files, report it to the developers with:
- Steps to reproduce
- Screenshots or video of the erroneous calculator
- The game version and your platform (Steam/Epic)
- A copy of any modified data files if you edited them
- Include test-build examples showing expected vs. actual scores.
3. RAM Timing & Dual-Channel Verification
The glitch where RAM speed was ignored is gone. The fixed calculator now reads:
- Single Channel vs. Dual Channel: Two sticks of 8GB in slots A2 and B2? +10% to the final score. One stick of 16GB? -15% penalty.
- CL Latency: The calculator now distinguishes between CL36 and CL30 DDR5. A drop from CL36 to CL30 will increase your predicted 3DMark score by roughly 2-3%.
Community Reaction: “Finally, a Simulation Again”
The fix has been live for roughly two months (as of this writing), and the sentiment has shifted from anger to relief.
One Steam reviewer wrote: “I uninstalled PCBS2 six months ago because the 3DMark calculator was gaslighting me. I reinstalled today. It works. I can actually PLAN builds now.”
On Reddit’s r/pcbuildingsimulator, the weekly “calculator wrong” posts have dropped to zero. In their place are posts asking for advanced strategies, like “Why does the calculator penalize my APU build?” (Answer: Shared memory bandwidth).
A notable modder, TesseractPC, even confirmed: “I decompiled the new scoring DLL. It’s using a proper queuing model now. It actually simulates render threads. This is how it should have shipped.”
What Was Broken Before?
Previously, the 3DMark estimation tool — meant to simulate the popular real-world benchmarking software — used a simplified, often broken formula. It would weigh core count too heavily, ignore thermal throttling, or randomly penalize certain GPU/CPU combos. You could slap mismatched RAM speeds on a last-gen motherboard and still outscore a meticulously tuned workstation. Veteran builders called it “the random number generator.”
