Jim,
If SMV uses the same naming convention or less than the current list of actors for the Millennium figures, there is no need for an additional null-loader. The one I've posted will work. Files that are saved into the library (and pz3 scene files) from within Poser do have problems with cross-talk. This is because of the way poser currently handles the assigning of instances to figures and groups. Until a better solution (one beyond what Poser is currently capable of) is implemented, or a utility is written to handle this, manual editing of saved scenes/figures will be required. It's as easy as global replace, but only for those brave enough to tackle cr2 editing. The problems being, when a new figure is read into the scene, the next sequential instance is assigned for like figures and actors. Figure 1... 2... 3 and so on. Such is also true of :1, :2, :3 etc. When you save back to the library poser doesn't re-assign ":1" to the actors, it uses whatever the currently selected figure/actor instance is. That said, when you go to load that figure into the scene (the cr2 already has some instance other than "Figure 1" and ":1" assigned) poser sees that the null is occupying ":1" and that the new figure isn't competing with it so it lets the figure load with whatever instance the cr2 indicated. If that's the case, the null will not work. The null has to occupy ":1" and the loading figure has to request ":1" for poser to re-assign it correctly. Body itself, the root (no-actor) should be selected.

Dean,
Fixed names work... but as I said above, your not really solving cross-talk with that method because you essentially have a new figure (although it's almost identical). Load two of the same fixed name figures and you land back into the same spot... cross-talk.

Mike,
Yes. There is nothing PC or Mac specific in the cr2.

John,
No offense taken. It's true... It's a stripped down cr2 consiting of version number, a list of actors and figure section (parent/child relationships). Pretty simple.

-Rob
rbtwhiz.com