A question about 3DMark

[elita]

Hey everyone,

I wanted to ask about 3DMark in general. On the 3DMark website, you can connect your 3DMark account with your HWBOT account, but it doesn't do anything. Wouldn't it be nice, if both HWBOT and 3DMark could recognize your achievement equally by for example, getting the results from each other and adding to one another, so we could have more data for you to look at. What do you think?

[Leeghoofd]

Has been tried before and doesn't work sadly...

- take eg many bugged scores due to Bclock manipulation are still in the Hall of Fame

- are user got advised to have nVIDIA ECC Memory to be set to enabled  for RTX 4000 series to have a valid competitive ( read non bugged ) scores, 3DMark Hall of Fame comprises so many inflated scores with this GPU ECC Memory disabled

- Timespy was a try-out to have a no screenshots requirement , boy did that turn bad as users were able to circumvent the systeminfo detection of specific driver settings.

....

[TAN YANG]

On 2/26/2025 at 12:54 AM, Leeghoofd said:

Has been tried before and doesn't work sadly...

- take eg many bugged scores due to Bclock manipulation are still in the Hall of Fame

- are user got advised to have nVIDIA ECC Memory to be set to enabled  for RTX 4000 series to have a valid competitive ( read non bugged ) scores, 3DMark Hall of Fame comprises so many inflated scores with this GPU ECC Memory disabled

- Timespy was a try-out to have a no screenshots requirement , boy did that turn bad as users were able to circumvent the systeminfo detection of specific driver settings.

....

I believe it is time for HWBOT to align with modern benchmarking practices, particularly regarding 3DMark integration. The current submission process imposes unnecessary burdens on users, such as requiring manual entry of hardware details (e.g., CPU-Z/GPU-Z screenshots) and redundant fields like "Idle/Ambient Temperature" or "Batch Nr." For instance, uploading a 3DMark score demands excessive manual data entry—a workflow that feels outdated in 2025. This complexity discourages new users: imagine losing progress due to a 2MB screenshot limit or an unchecked "Terms of Service" box triggering a page reset.

The lack of adoption is evident. Take the RTX 5090 series: while 3DMark hosts thousands of submissions, HWBOT shows only three or four—mostly from hardware vendors for promotional purposes. If HWBOT aims to be a global hub for overclocking enthusiasts rather than a niche platform, streamlining processes is critical.

HWBOT’s strength lies in being the only platform combining rigorous 2D/3D benchmarking with community-driven moderation, making it uniquely authoritative. However, its potential remains untapped due to accessibility barriers. To expand influence:

Prioritize 3DMark user acquisition by adopting automated score imports (eliminating manual entry).

Remove non-essential fields to simplify submissions.

Leverage HWBOT’s credibility to publicly flag suspicious scores (e.g., implausible frequencies), enhancing trust and deterring fraud.

Proactive adaptation—not restrictive policies—will drive growth. 

I urge the team to reconsider these improvements to secure HWBOT’s position as the definitive benchmark authority.

（Translated by AI😉）

[TAN YANG]

On 2/26/2025 at 12:54 AM, Leeghoofd said:

Has been tried before and doesn't work sadly...

- take eg many bugged scores due to Bclock manipulation are still in the Hall of Fame

- are user got advised to have nVIDIA ECC Memory to be set to enabled  for RTX 4000 series to have a valid competitive ( read non bugged ) scores, 3DMark Hall of Fame comprises so many inflated scores with this GPU ECC Memory disabled

- Timespy was a try-out to have a no screenshots requirement , boy did that turn bad as users were able to circumvent the systeminfo detection of specific driver settings.

....

HWBOT should prioritize expanding its user base before enforcing additional rules. Without a thriving community, the regulations would serve no meaningful purpose. 3DMark submitting should be just like XTU submitting, why not?