(Updated November 11, 2008) Josef Wienerroither has optimized and tweaked the Max scenes from the tests in order to balance them with the XSI setup, and did complete benchmark sessions before and after. Max fares much better than the results published at Jon Peddie’s website, and in a few cases outperforms XSI. Check out the details at Josef Wienerroither’s website.
Josef Wienerroither, a reader from Austria, sent us feedback criticizing the tests done by Jon Peddie Research for comparing XSI’s performance with Max’s and Maya’s (see our recent news item). He downloaded the scene files and says they do not ensure a fair comparison because they are set up in a way that seems to favor XSI’s performance. After making his own tests with the scene files his conclusion is that “this looks really not like a Benchmark to count on.” Read on for more detailed information on the tests he made.
“a few examples i discoverd after 15 min
* “1000 rotating cubes” :
-> XSI scene has optimized,linear keys ( 1
key at every ~40 frames
-> Maya scene too optimized, but smooth
tangented keys
-> MAX scene has LINEAR KEYS at every
frame, this hits the Viewport FPS heavy !!!
* “1000 rotating cubes”
-> XSI scene: Viewport is set to BOUNDINGBOX mode
-> Maya,Max’s is set to Wireframe, if Max is set to
Boundingbox
it gets double the framerate
of XSI (on my system)
-> in wireframe mode, Maya is winner, Max comes next,
XSI last
* “Jogger”+”Jogger high” :
Max’s display of Vtx/Poly count in the viewport is known to cause a
performance hit (stack has to be reevaluated each frfame for this
info). If turned of a see a 20% perf. gain in “Jogger”
* “Particles_With_Four_Goals” :
XSI view+particlesim perf is better than max’s, but well ,
the particles in the XSI scene to not target their goals, their simply
float directly up 90°
again: this all i found during the first 20 minutes dealing with the
scenes, so this looks really not like a Benchmark to count on….”
