Excellent program, but he doesn't understand what it does. ;) Other classmates where impressed though.

I'll resume working on it mid July.

:^D

you did show him the rolling demo of 3Dmark2001 (yes sir, that all done with JAVA! ;) )

I spent the entire weekend looking for a laptop that could run 3Dmark.... didn't found one. Eventually i ended up with a pentium I laptop of a kind neighbour. It took 898 seconds to caclulate pifast, lol. :^D

Moeha! Great news! I found another way to substract the average frames per sec without as much limitations as it has now!

The only thing necessary is that the bench can stop itself, like a prerecorderd script. That shouldn't be a problem with most apps (like Q3, UT2K3, ...).

I just tried it on UT2K3 and it works! :super:


Damn, i've spent my first hours of my vacation trying to tweak MadMark. Addict to the bone... :)

:woot: going strong, MadMark for president! ;)

can't u just use the standaard benches from ut2003?

the results are stored in a textfile

Yes, but the standard has popups (i want no user interaction during the batch) and one way to substract the avg fps in all directx/opengl games is better than a seperate way for each game. :)

Next update will include ability to record hardware config:

ver 0.09 is finished, but will not be publicly be released since the madmark database server is not made public (yet).

ver 0.10 will have the ability to submit your results to the madmark server, and compare them with other results (!).

long time no update: here's a teaser of the next release. I will be able to continiously monitor the framerate, instead of giving an average fps.

I consider this to be a big advantage: average fps does not tell you how many times the frame rate drops below acceptable levels.

There will be three 'zones':
eg. cat "3d shooter"
<25: unplayable (red_
<60: playable (yellow)
>60: excellent (blue)

As you can see, my laptop (ati radeon mobility) barely manages to get out of the red zone.