Thanks. Most of those were done in bryce as Vue is only a recent addition to my armoury. Amarri-Tath was done at the default Broadcast mode.

As far as I'm aware, the rigging problem you found is essentially because the thing you're rendering (the rigging line) is a fair bit smaller/thinner than a pixel of the final image, so as the rigging line crosses pixels in your rendered image it can sort of appear/disappear depending on how much of it falls within each pixel that it runs through (thats my understanding of it anyway).If only a bit of rigging lies in a pixel, then it'll not show up, if there's a fair bit of rigging line in the pixel, then it'll appear.

I use one of two ways to go about the problem - first is to just render bigger (in effect making the rigging mesh bigger with respect to the pixel size in the final image) and then shrink the rendered image down to the size you want. This can be really inefficient for time.

Other way is just to up the AA settings and re-render the troublesome area of the image until you get the result you want and then paste that back into the main render in a paint program. Now I haven't done any "rigging" renders in Vue, but in Bryce you'd just raise the ray's per pixel up to about 16 or 36 and that'd take care of the problem from my experience. In vue I think this translates to playing with the object anti-aliasing slider's max setting to those sorts of numbers and raising the quality slider for the OAA to 90+ % and see how that goes for rerendering only the troublesome area. 

I'm still largely at the trial and error stage in Vue as far as render settings go, so I  don't really have an innate feel yet for what is appropriate for these sorts of things. I'd recomend have a good read at Peggy's pdf tutorial that people mention in this thread ->

http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2714774

 and going from there - its what I did. As long as the final render is under a week, I'm happy :)

Dreams are just nightmares on prozac...
Digital WasteLanD