Some nice ideas you have there, allows for more control.
Have you done any more work on this tool? I’ve been using it now and again, and I think it’s very useful.
I have found two bugs in it though:
-The global declaration for benchmarkerSettings is not entirely correct, causing a crash the first time it is run. Forward declaring it as a global (without assigning a value) resolves that.
-The number of iterations is incorrect. When using 1 iteration, starting at 1, it is running for i = 1 to 2, which runs two iterations. Could be easily resolved by subtracting 1 from the iterations value when building the loop.
I kinda forgot about this one actually, but feel free to modify whatever you see fit and repost
Well that’s all I have on it really. I just turned it into a macroscript and fixed those two things.
And I wondered if you had done any more work on it.
I still use this script now and again, and find it very useful!
In addition to the bugs mentioned previously, I fixed a bug related to 3dsmax2013 PU4 (“return()” vs incorrect “return”). I’ve also added more persistent storing of the method strings. I found myself entering them again and again when having to restart 3dsmax in between benchmarks. So now they’re stored in a .ini file in #UserScripts.
It’s all a bit patchwork, but it works so far