3DMark
Haliaeetus Dec 5, 2024 @ 2:55am
"SystemInfo data is incomplete" while running Time Spy (Extreme) to achieve "What's the rush?"
First of all, let me be blatantly honest from a user's perspective:

The whole system info collection process is a joke - always running it prior to a benchmark instead of once upon 3DMark's launch & then only if any hardware change (changing render device, monitor (output) used, etc.) occurs would be what's expected. It's just time consuming & delays everything for no useful reason.

Next, selecting a benchmark to run on my iGPU (Ryzen 7950X3D, even connected the monitor to the mainboard's DisplayPort), still keeps 3DMark telling me that the rendering device isn't connected to the monitor - that's simply BS & should be already fixed.

Now, let's get to the most annoying issue:
After system info collection is done, the benchmark, i.e., Time Spy (Extreme), is run & after all the wait, the result's log shows above's error? Seriously?
It should stop right there, after the incomplete collection, to prompt users if they still want to run the benchmark.

But what's _really_ annoying me - up to the point that I cared enough to write this post - is the fact that _any_ benchmark runs just fine with RivaTuner Stats Server turn on for FPS limiting (at 3 FPS to account for Time Spy's 1st GFX test's initially high FPS values) - until running Time Spy (Extreme) to unlock aforementioned achievement.
Because doing so, results in system info being incompletely collect. _Always_.
However, running the exact same settings for _any_ other achievement with _any_ other benchmark, the system info is collected just fine. _Always_.

That just drives me nuts - so, please, allow those with too powerful hardware to complete those older benchmarks, too!
< >
Showing 1-7 of 7 comments
UL_Jarnis  [developer] Dec 5, 2024 @ 4:22am 
The reason why SystemInfo scan runs also at the start of the test is because otherwise people would happily cheat. It even runs a partial scan at the end of the run, and monitors a bunch of things during the run. Because some people only care about bigger number and went as far as rigging custom things tied to hotkeys that modified system settings so they could adjust things mid-run.

The UI start scan is purely for populating data on the front page hardware information and to give warnings for incompatible tests.

I would need to see SystemInfo logs to determine why TSE would fail with that error. Contact us directly here:

https://support.benchmarks.ul.com/support/tickets/new

and include a link to this thread.

I do not fully understand the part about RTSS.exe. All I know is that it can cause GPU driver crashes due to all the invasive stuff it allows. If 3DMark run fails with RTSS.exe running, only advice we can give is to run without it.

Related to the iGPU issues, is the iGPU driver up to date? There was a lot of issues recently seen related to AMD iGPUs that generally are caused by the fact that so many people run the iGPU with whatever driver Windows Update pushes to it (which is very old).

For our tests it should not matter what GPU and what monitor is being used, with the caveat that if you are outputting to a monitor that is not attached to the rendering GPU, there is definite overhead from the frame copying to the GPU that is doing the presenting to the monitor.
Haliaeetus Dec 5, 2024 @ 5:23am 
Thanks for the quick reply - much appreciated!

Regarding cheating, I didn't know people go _that_ far - I'm just here for achievements & some basic ranking of my rig compared to similar systems..

Now, with RTSS, I managed to get a valid result with full system info by launching RTSS, i.e., confirming its UAC prompt, only about 3-5 seconds before the actual benchmark started & I even managed to achieve only 3 / 2 FPS (1st & 2nd GFX test).
However, the achievement remains locked for no obvious reason - here's the test run, so you can check for yourself: https://www.3dmark.com/3dm/121649561

[-EDIT-]
Oh, BTW: all those good/great/excellent/legendary achievements remain locked as well, although I did score multiple times at least average results in both, overall results as well as those matching my hardware setup. Why is that?
Last edited by Haliaeetus; Dec 5, 2024 @ 5:26am
UL_Jarnis  [developer] Dec 5, 2024 @ 7:59am 
Hidden result. Is your account set to hide results by default?

For Legendary etc. I'd need to see links to results.
Haliaeetus Dec 5, 2024 @ 12:15pm 
Yes, but updated just for you & just now. 😉

And not regarding Legendary, but maybe at least "Good", please see: https://www.3dmark.com/3dm/121655863
UL_Jarnis  [developer] Dec 9, 2024 @ 1:10am 
The result you linked is in bottom 7% of the results using that hardware, it is nowhere near level required for the score based achievements. Do not confuse "% of all 3DMark results ever" and "% of results using exact same hardware as you" that the achievements require.

Frankly the score is so low for your hardware that there is probably something not-quite-right with your configuration.
Using the link above, I get to read: "better than 38% of all results" for run details & for "similar systems scores" under result details, I get "17" highlighted - which happens to be the 2nd most common result (63 for most common, 16 for 3rd most common).

How come, you tell me it's 7%?!

Besides, the specialty with my configuration is that my 2080 Ti powers an Odyssey Neo G9 instead of a more common 27" WQHD monitor, i.e., 5,120 x 1,440 pixels instead of 2,560 x 1,440.
Because other than that, my setup is basically a standard Win 11 Pro x64 machine without any OC or stuff like that.
Originally posted by Haliaeetus:
"similar systems scores" under result details, I get "17" highlighted - which happens to be the 2nd most common result (63 for most common, 16 for 3rd most common).
17 results betweeen a score of 6000-6999. Thats a histogramm not a %. You have to search for same gpu/cpu (as clicking the histogramm don't work/auto fill in since ages)
https://www.3dmark.com/search which comes to place 84th/90 or bottom 7%

your result looks like your GPU is overheating as 77°C avg for only 1.5GHz avg. reached of 1860Mhz set is too much. (you should repaste it)
Last edited by Huperspace; Jan 7 @ 9:02am
< >
Showing 1-7 of 7 comments
Per page: 1530 50