Application Details:
Version: | 2006 (3DMark06) |
License: | Retail |
URL: | https://benchmarks.ul.com/3dma... |
Votes: | 0 |
Latest Rating: | Gold |
Latest Wine Version Tested: | 6.0 |
Maintainers: About Maintainership
What works
Settings and Benchmark
OffScreenRenderingMode: FBO
use an extra command when you launch 3dmark06
WINEDEBUG=-all wine 3DMark06 -nosysteminfo
Set the Filter to any except Optimal because of FireFly
Q:
I'm getting a "System Info error: WMI Enumeration not found" or a
"System Info error: Wbem not connected" error message when starting the
benchmark. How can this be corrected?
A: This problem occurs on some systems and we're currently
investigating the cause. There are a couple of things which may help:
1) Ensure that you have the latest available motherboard BIOS
installed. 2) If you have created a custom Windows XP installation CD
or manually disabled standard services, please ensure that "Management
Instrumentation (WMI)" service is installed and configured to run. You
can also use the "-nosysteminfo" command line option to disable the
SystemInfo from running. This will prevent you from submitting your
results to the ORB, though.
I have installed winetricks: d3d9, net 1.0, net 2.0, visual c libraries
DirectX Update and SDK November 2008
I use Nvidia 8600M GT 512MB DDR2 with NVIDIA 177.82 driver
3DMark06 Score (1280x800,fullscreen,SM3.0,NoAA,Optimal)
Linux: 2633 points (Vista: 4490 points)
What does not
Everything else, because of empty hardware info
Workarounds
What was not tested
Everything else, except Benchmark
Hardware tested
Graphics:
Additional Comments
Operating system | Test date | Wine version | Installs? | Runs? | Used Workaround? | Rating | Submitter | ||
Show | Ubuntu 20.04 "Focal" (+ variants like Kubuntu) | Feb 28 2021 | 6.0 | Yes | Yes | Yes | Gold | C. Leu | |
Show | Debian GNU/Linux 8.x "Jessie" x86_64 | Jul 04 2015 | 1.7.46 | Yes | Yes | No | Gold | Wylda | |
Show | Ubuntu 14.04 "Trusty" i386 (+ variants like Kubuntu) | May 02 2014 | 1.7.17 | Yes | Yes | No | Gold | Jarkko Korpi | |
Show | CentOS 6.4 | Sep 16 2013 | 1.7.1 | Yes | Yes | No | Gold | Artem S. Tashkinov | |
Show | Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu) | Aug 07 2013 | 1.6 | Yes | Yes | No | Bronze | an anonymous user |
In order to run 3DMark 2006 under Wine you have to:
1) first install d3dx9_28.dll and d3dx9_36.dll dlls using winetricks (right mouse click, "Save link as", save as winetricks.sh, then make it executable, then run it).
2) edit the 3dmark 2006 link and add this flag to its command line: "-nosysteminfo", so it will look like:
wine "C:\\Program Files\\\Futuremark\\3DMark06\\3DMark06.exe" -nosysteminfo
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Artem S. Tashkinov on Monday September 16th 2013, 16:25
16430 3DMarks
SM2.0 Score: 5384
HDR/SM3.0 Score: 7855
CPU Score: 6313
(native d3dx9_36 and d3dx_28 are required, 3DMark must be run with -nosysteminfo option)
Windows 7 64 results will be posted shortly.
by Artem S. Tashkinov on Friday September 20th 2013, 2:36
24950 3DMarks
SM2.0 Score: 9874
HDR/SM3.0 Score: 12681
CPU Score: 6042
CPU score is more or less the same, SM scores are almost two times smaller.
by Artem S. Tashkinov on Saturday March 17th 2012, 6:51
10101 3DMarks
SM2.0 Score: 4506
HDR/SM3.0 Score: 3007
CPU Score: 7006
Windows XP 64/NVIDIA 285.58
15568 3DMarks
SM2.0 Score: 6196
HDR/SM3.0 Score: 5918
CPU Score: 7407
CPU: Intel Core i5 2500K @4.1GHz
GPU: NVIDIA 9800GT non-overclocked
Wine definitely needs to be greatly improved, on average it's 33% slower, but in SM3.0 test it's two times slower.
by Vadim on Sunday December 12th 2010, 11:32
2xGTX280, QX9770, resolution 1600x1200, all other settings default.
SLI=Auto
7418 3DMarks
SM2.0 Score: 2362
HDR/SM3.0 Score: 3167
CPU Score: 5185
(SLI=AFR gives the same scores, SFR slightly better, AA even more better (despite there was no antialiasing at all))
SLI=Off
8341 3DMarks
SM2.0 Score: 2805
HDR/SM3.0 Score: 3471
CPU Score: 5199
i.e. single card has better performance. Weird...
by Vadim on Sunday January 9th 2011, 7:22
Why such strange results?