Yes, I viewed that tutorial and any possibly related early on. My novice reaction was "you have to be kidding". I suppose Pro users see a point to all of that, but the occasional user with complex designs are going to gag after the sweet product composer was. I could downgrade, but I have such high hopes for future product development.
I would have hoped that once saved as a Composer file the limitations of .SAT would be moot, and the objects would behave as any Composer object. But if I might restate the issue with .SAT, the objects appear to only accept one or two attributes of the material properties, even after saving in Composer.
Another aside with .SAT is the random occurence of spikes on some objects. Excuse the lack of vocabulary - I was enthralled with Composer when it came out because it didn't require a heavy background in image processing or jumping through hoops to get terrific results. Now if I don't pay careful attention, my material library gets unintentionally mashed.
Excuse my beefing, but I want Composer to be appealing to the novice class too.
Composer Pro 2.3, Alibre Design Expert 2011, V Ultimate 32bit,
MB Asus M3N78-EM, 4 GB, 3.2 GHz Dual, GeForce 8300, GeForce 9300 GTX+