Well, Dbreen, Bryce is slow, but the render engine kicks Poser's butt, waits for it to get back up, and kicks it again... this has GOT to be done in Bryce. As long as you avoid volume materials, it's not all that bad. Your render time is what YOU MAKE it. Gear... (checking the calendar to make sure it's not April 1) I am supremely interested in the prospects of getting Poser and Bryce to communicate. Question: Platform?? On what platform do you plan to do development, and would you port to the other platform? As for interface... two monitors works for me, since I have a dual monitor setup. But I don't think you can count on that... most people only have one. Given that a Poser figure within a Bryce scene isn't likely to take up all the screen realestate, a floating palette of Poser controls that the user could move around would probably work best. That way, the palette can be moved close to the figure, reducing mousing to the screen boundaries and back. It would also minimize confusion of Bryce controls for Poser controls. Of course, the other option would be to do all the animating in Poser and import the data (BVH or a custom format) into Bryce. Then all you have to do is place the figure path into the scene. It may be easier to do, but wouldn't allow you to interact the character animation with the Bryce animation as closely. For that reason, I like the idea of animating within Bryce. I tend to have a lot of ideas on interface design, and would be interested in beta testing. -sk