3DMARK 2003 Patch released
3DMark03 Patch (build 320) Improvements
Key technical points:
Now supports Microsoft DirectX 9.0a.
Professional version includes customization tools for different skins.
Anti-Aliasing (FSAA) and full frame pixel shader post-processing can now be used simultaneously. (NOTE: DirectX 9.0a runtime must be installed for this functionality).
Added appropriate tools for creating custom skins for the 3DMark03 user interface.
Added a new benchmarking option which forces PixelShader 1.1 code path in game tests 2 and 3.
"Submit Saved Result" feature enabled in 3DMark03 Free Version.
2 new command lines added: "fixedfps" and "disableopt".
Fixes & Updates:
CPU & VPU/GPU MHz detection functionality updated.
Installation issue solved.
Fixed all reported issues with results in Excel.
Fixed ImageQuality Test issues.
Updated System Info.
Improved driver detection.
XML issues solved.
All other reported & identified problems and bugs in 3DMark03 have been solved.
What is so sad is that Futuremark didn't even fix their biggest flaw/cheat. You can STILL! cancel out in the middle of the benchmark and overclock your settings and re-run it to the old settings to show that your score is a lot higher then it should be. Because it still keeps the old setting even though the clocks have changed.
This was verified by some of our readers. How sad... Good Job Futuremark.
D. Solomon Jr.
jAkUp, can you test with and without forced PS 1.1 on you GFFX?
hmmm... i tried looking for the option but i cant find it! maybe its only for retail 3dmark 2k3... if anyone knows if you can enable it in trial, let me know.
If you are talking about the GPU/VPU core & mem MHz, I don't see how that is possible. I just tested this procedure:
1. Started 3DMark03 (default MHz)
2. Ran GT1 and GT2
3. Quit the benchmark run
4. Overclocked the GPU/VPU
5. Ran the whole benchmark
and when I looked at the result file, it showed me the overclocked MHz, and not the default. Or am I missing something?
*edit: Ok.. I think I know what you guys mean. You see, when you start 3DMark03, and the look at the client SystemInfo, it displays the info it collects when 3DMark03 is executed. If you then change any MHz, the client System Info is not changed, but the result file that you will upload / save is. If you do the steps I posted above, and then after the benchmark run look at the details of the result file (not the clientside SI), you should be able to find the MHz that are sent to the ORB, and they are correct. The clientside SI is not updated "on the fly". I hope this clears up things..
Nick / Futuremark
It does... You don't usually look at the file. The results do show the change once you look at the file. Maybe in the next patch you shouldn't even allow the program to run again. Have a pop up window that says, "system specs have changed. Please restart program"...
D. Solomon Jr.
well, the data that is viewable in the ORB is the one that counts. If anyone posts anything about 3DMark, or results, you should always ask them for a compare URL. It's easier to determine what's up when one can actually see the result + we can investigate it (in case there would really be some probelms).
We will keep this in mind the next time we update our products, or release new ones. It seems that people are pretty quick to look at the System Info that's been gathered when 3DMark is started. It is all ok, but as we have seen, people like to "hack" and "tweak" to fool the program. We are doing a lot to prevent cheating and faking stuff. It's not an easy task, but now it is looking pretty good.
btw, thanks for the new update in your news!
|All times are GMT -5. The time now is 12:19 AM.|
Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright ©1998 - 2014, nV News.