A lot of what we do in Labs is somewhat predictable. But what we are really looking for is the unexpected.
The benchmark continues to progress, and results are rolling in.
After several rough weeks, the end is in sight. Scripts are cleaned up, benchmark package is created, now to see if it works.
Well, scripting has been kicked up a notch, and the training wheels are off. I dive deeper into AutoIT, and attempt to figure out arrays and networks.
I this ongoing series, I experience a very frustrating week, full of blue screen, crashes, and more blue screens.
This was a pretty wild week. Well… as wild as being stuck at home writing code can be.
With much of the scripting done, I turn my attention to making the benchmark somewhat customizable.
After a couple weeks of smooth sailing, things get a bit rocky.
This week we continue the development of a new benchmark and dive into scripting within 3ds Max
An ongoing series on creating a benchmark, from inception to completion. This week, identifying areas of 3ds Max that hardware creates slowdowns or bottlenecks.