Sometimes when I load a large Poser object into Vue 6I then delete it, I find that there isn't enough memory left to load another large poly count object.  This manifests sometimes as missing arms (or perhaps whatever mesh parts were trying to load last when the memory limit hit).

Another problem I came across recently is a figure which loaded with all its props and child figures, but the figure was missing (not just arms missing but the whole figure).  I figured out the problem there was that the figure had been moved to another P6 external runtime so the PZ3 no longer knew (and so could no longer tell Vue, I'm guessing) where to find the obj file for the figure.  Once I reloaded the figure in P6 then renewed the PZ3, Vue saw it all.

I'm guessing your situation might be a memory limit.  I've found when figures start loading incompletely that I have to exit Vue entirely then reload the program... then my figures load completely.  In your case, if that doesn't work you may need to consider more RAM, or smaller poly count figures.  Another strategy which works well, and which I use alot, is to load an empty Vue scene, load my high poly count Poser object then save it as a Vue object.  Much less memory drain.

Good luck.

Quote - Thank you, as I only do still renders at this time, that was immensely helpful and a good deal easier than the bodyparts suggestion.

You're welcome.  If one uses the keyboard shortcuts to switch cameras, it can be very quick.  Anyway, glad this now works for you.  cheers...

When you're in a given frame, you can usually just switch to another camera (e.g., the Face Camera) and rotate it.  The parts pop back in and you can switch back to your prior camera.  This is easier than moving body parts.  However, this solution (and all others I've ever heard of) fail to address "lock jaw" for animations. 

Hey Ockham... long time no see!

I haven't installed SR3 either, largely because I don't use P7 at all anymore.  I just got tired of the lousy cloth room performance.  (hmmm... wonder if SR3 was supposed to fix that too?)

I've since discovered Vue 6 Infinite for renders, so P6 works just fine for setting up scenes to be rendered in V6I.  Plus, all those great scripts you've created work great in P6.

cheers...

I just checked my Actions folder in my pose library, and I'm now up to 6,083 pose files; with about half of them animated poses ranging from a few keyframes to thousands.  But then, I've been developing and accumulating them for at least five years now.  Maybe I should open a store.  (grin)

This won't help with scenes you want to load over and over, but my solution for my base figures is the same one suggested by Ockham near the top of this thread:  open the CR2 for any new version of a figure I create in a text editor and manually delete all references to --and prop info groups related to-- "control" props.  This way, when I load a character from my figure library, only a single set of CenterOfMass props is loaded and I can navigate the hierarchy without all the superfluous prop clutter.  Also, I tend now to do less saving of scenes and more saving of poses which can then be applied to clean figures and props when I want to generate a scene for rendering.  Saves disk space too since my PZ3s tend to be very large.

I've just migrated to V6I and bought SkinVue.  Love them both.  Here's a useful discovery I'll pass along:  you can edit the SkinVue plugin for your figures so that the textures of props parented to your figure are also converted to Vue materials you have saved in your SkinVvue material library.  So, for example, I've edited the SkinVue script I use for my V2 figures so gold jewelry is automatically converted to a Vue gold material.  cheers...

FWIW, I've just started using V6I, with most of my work involving animations with dynamic cloth imported from Poser 6 (I have P7 but don't use it anymore since it is awful at cloth sims and the main advantage of better firefly render times is now moot given my shift to V6I). 

What I've discovered is that the dynamic cloth sim sometimes imports and sometimes doesn't.  I haven't done enough testing to know what's causing the cloth sim import failures, but I have discovered that if I want it to work every time, I make sure I do the following steps:

1.  save my PZ3
2.  set up and run the cloth sim(s)
3.  save the PZ3 again

Cloth sim imports properly every time.

I do know that if I move a PZ3 from one directory to another, the cloth sim import usually fails, even if I also move all the associated files, like the dyn and tmp files. 

Also note that I do not use external morphs.  Don't know if that makes a difference, but in case it affects the above solution one way or another...

good luck

Huh.  A little surprised I never got a response. 

Anyway, I went ahead and converted all my Poser custom mag effects to morph targets and bought V6 Infinite.  The MT approach actually works better than the mags, especially when figure twisting or bending moves the mag zones away from where I want the mag effects manifest.  Also, the python scripts for animating the effects run faster than they did with magnets, so it was probably worth doing whether I stayed with P7 or went to V6 for rendering.

But the renders in Vue are spectacular, so I'm glad I moved to Vue.

I used an Antec 900 in my March 2007 build.  Great case!  Matched it with Razer Tarantula keyboard and Razer Copperhead mouse so my work (play?) area is suffused with righteous blue glowiness. 

Quote - no problem

fig =  poser.Scene().CurrentFigure()    gets you the current figure

Cool!  Thanks markschum.  I'll give that a try.  cheers...

Okay, I got it.  I actually kept the "for frame in range..." loop and changed the "nextkey" line to "nextkey = rightthighFrom.NextKeyFrame()" in the copyparms1 loop (and same using "leftthighFrom" for copyParms2 loop).  Now it blazes through its routine, changing the relevant morph targets everywhere there is a change in each thigh bend parameter. 

It's also nice that I don't have to pick each thigh in turn.  It runs even if I have BODY selected.  If I tinker with it further, it'll be to try to make the script more generic so I can just run it on whatever figure I have selected rather than having to have 3 different versions for the 3 characters I use it on.  But to do that, I'll have to read up on how to code it so it uses the currently selected figure. 

Anyway, sincere thanks once again to markschum and ockham for taking a look at it!

cheers...

Quote - Markschum has caught the problem.

If you're only going to set the value at keyframes, you don't need the
outer loop on range(scene.NumFrames()).  The while loop based
on NextKeyFrame will do the whole job.

This would do well enough in each case:

for parmName in copyParms2:
..... parmTo4 = leftthighTo.Parameter(parmName)
..... parmTo5 = leftbuttockTo.Parameter(parmName)
..... parmTo6 = lefthipTo.Parameter(parmName)
......scene.SetFrame(0)
......while 1:
....... parmTo4.SetValue(leftthighFrom.Parameter("Bend").Value() * -0.01)
....... parmTo5.SetValue(leftthighFrom.Parameter("Bend").Value() * -0.01)
....... parmTo6.SetValue(leftthighFrom.Parameter("Bend").Value() * -0.01)
....... nextKey = parmFrom.NextKeyFrame()
....... if (nextKey == None):
............ break
....... scene.SetFrame(nextKey)

hmmm... doesn't work, alas.

First fix attempt = deleted the "for frame in range(scene.NumFrames()):" line only.  This made it match the code pasted above in the quote, with periods = spaces.  Led to syntax error on "scene.SetFrame(0)" line.  

Second fix attempt = various experiments revising indentations.  Led to errors of either syntax for lines in the looping routine (e.g., the "while 1:" line) or undefined parameter error for "parmFrom".

So... not sure what to try next.  If anyone has suggestions, I'd really appreciate it!  And thanks again for your help so far.

cheers...

Quote - Markschum has caught the problem.

If you're only going to set the value at keyframes, you don't need the
outer loop on range(scene.NumFrames()).  The while loop based
on NextKeyFrame will do the whole job.

This would do well enough in each case:

for parmName in copyParms2:
..... parmTo4 = leftthighTo.Parameter(parmName)
..... parmTo5 = leftbuttockTo.Parameter(parmName)
..... parmTo6 = lefthipTo.Parameter(parmName)
......scene.SetFrame(0)
......while 1:
....... parmTo4.SetValue(leftthighFrom.Parameter("Bend").Value() * -0.01)
....... parmTo5.SetValue(leftthighFrom.Parameter("Bend").Value() * -0.01)
....... parmTo6.SetValue(leftthighFrom.Parameter("Bend").Value() * -0.01)
....... nextKey = parmFrom.NextKeyFrame()
....... if (nextKey == None):
............ break
....... scene.SetFrame(nextKey)

Sorry for the delayed expression of thanks, but I just got back from a road trip.  So... THANKS!  I'll try this improved code!  cheers...

This sounds like another manifestation of a bug which has been discussed in many previous threads.  V4 will lose parenting of hair and/or jaw parts if you have PointAt invoked for the eyes.  Locking the actor doesn't solve it.  You may notice that if you go to the frame you want and change the camera (e.g., go from Main Camera to Face Camera) then rotate that camera, the hair or jaw will snap back into place; but if you then go to another frame the parented parts are at that new frame's position.  Try turning off PointAt if you have it invoked for the eyes and see if the issue disappears.