I have noticed that C5 is pretty picky about the scenes you import.  I was never able to get a file I wanted to render in C5 to load, it had multiple figures (3), dynamic clothes and hair, with hi res textures.  I ended up doing it the other way you said, by saving the figures one at a time in P6 and loading them seperately in C5, then I got the memory allocation error in C5.  I ended up rendering the scene in C5 then putting the figures in, in P6.  Oh well...  I'll figure it out eventually.  I did notice that Bliss Vision hair does not work very well in C5, you always end up with a visible skull cap where it should be transparent.  And you can never figure out which of the dozen or so procedural shaders C5 creates for it are the skull cap to remove it properly.Maybe with Eovia being bought by Daz, they will improve the rendering of poser figures and dynamic hair, or better yet, if they integrated Daz Studios functions into the next version of Carrara it would be awesome.

 

Quote - I'm having very similar troubles with C5_Pro. Some scenes it flat out won't load. Some I can manage to load after a number of tries, but when I try to render, C5 blinks out. Gone. With still others, I get the "unknown error"s or the "memory allocation error"s. I'm starting to wonder if I didn't have a lot less trouble with "vanilla" C5, rather than C5.1?? Do these problems seem worse on 5.1 to anyone else. We're talking scenes in the 150-225 megabytes range with multiple figures and hi-res textures.

I was also tinkering with the idea of loading scene elements in bite sized chunks. In otherwords, set the scene in Poser, and then save out the scene elements in separate files. Then using Import in C5, rather than Open.

I'm not a happy camper. I switched to Carrara to get away from this sort of problem. Belive it or not, last night I rendered a 'toon in Poser, at medium resolution, that C5 wouldn't even load. Talk about a turn about.