Aye, this is a cool thread! One thing I've determined from the nearly daily, "Poser to Bryce, how to?" threads in the Bryce forum is that patience is the key. I use Poser nearly every day. I never render anything in Poser (ecxept to test collisions and placement of clothing/hair) because I am ALSO impatient, and it's lighting controls are just plain primitive compared to Bryce, or any 3D app for that matter... I've never used Grouper, and have no need. Bryce's "Family" function works just fine for me. For whatever reason, my brain has no problem keeping track of the tens of thousands of file locations when importing a figure, and I don't mind re-assigning alphas and bumps from Bryce's wonderful Material Lab. I never cared about the names of the objects, because I can just select them and re-name them. Although I love the upgrades from Poser 4 Pro to Poser 5, it's unstable even at 512MB DDR for me and considering it's proprietary mats and hair, we're still stuck with Alpha-channeled hair outside of Poser 5. Procedural textures will always blow away photo-textures, that's why they were invented. Bitmapped textures by definition lose accuracy when rendering, and although you can't beat good hi-res textures, I love to re-texture clothing with Bryce's procedurals... Not attacking or dibelieving anyone, these are my experiences with Poser. I use it for Posing, and that's it! And although I don't appreciate Wolfie's "tone" (textone?!?) much, I really DO appreciate your insight and I LOVE your huge prints! I recently did a 10x5 banner for my brother's band, all in Bryce, and that was our first Render-to-Disk usage (9600x4800), and it turned out wonderful. We also made a label for his bass-drum head, all in Bryce, the text was heightmapped from my brother's design... Other than Poser animation, which Bryce doesn't support anyways because it doesn't do morphing, I can't imagine having any need for Bryce to read .Pz3 files. (shrugs)