Trust bagginsbill on this one! ;)

I'll back him up:

1. I'm a programmer (the professional part is under dispute).
2. I have the big-daddy book on texturing: "Texturing & Modeling: A Procedural Approach".  This has sections written by the people who actually developed many of the shaders you use in Poser (and everywhere else)!  I wouldn't doubt that bagginsbill has it as well.  What he says agrees with the tome and other sources.

Procedural shaders literally map on-the-fly so there is no need to store additional memory beyond the variables.

Ask yourself one question: Why is it that you can have thousands of shader nodes (if not using image maps) and Poser doesn't choke with the "Out of Memory" error, yet add a few strategically sized image maps and bye-bye Poser?

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone