Importing from Poser to DS - stuff not saving in DS
Is this to be expected as a consequence of importing from Poser through the content library tab?-
I imported some architecture (an office) from my Poser library, set up a scene in DS that looks great in the test renders, then save it. When I open it later all the furniture has moved around and half the walls have gone.
While adding the content some "can't find texture" messages came up but I assumed DS had all the objects successfully saved in the scene. Apparently not.
Perhaps to put it another way, when the scene is opened, the Poser stuff in not loading into the scene.
Can I avoid this in the future or is this pretty much what sometimes happens bringing in non-DS stuff from another library?
Post edited by fred9803 on
Comments
No, that should not be happening.
Where is the Poser content? Where is all your content? Is it all on the same hard drive? Split over more than one? Is it on an external drive?
What operating system are you using?
What it is sounding like is that for some reason (and being on a different/external drive, can in some cases be 'enough') the content wasn't where it was expected to be...neither the 'data' folder content (that's where the 'converted' stuff goes) or the original that would be reloaded if the 'data' folder stuff wasn't found.
Thanks mjc.
Both the Daz and Poser content are on the same external drive. Using Win 7.
I've had no problems with single objects but because the architecture I imported consisted of multiple separate objects (desks, roof, walls), I guess something went wrong.
I was probably a bit ambitious expecting such a load to all come over properly and be saved. I can live with that and I'll be more careful how I do it next time.
Thanks for your input.
Have you got that poser library added in preferences?
i have had this happen with an old one on another drive that is not,
You say "imported" — did you actually use the File>Import menu option, or did you load it with a double-click from the Content Library tab? There shouldn't be a difference, but stranger things have happened (sometimes to me).
It does sound like D|S isn't aware the location you loaded the Poser file from is a proper content folder, that's definitely known to cause Weird Stuff™ to happen. The Poser files might also be badly laid out; Poser can frequently handle dud files with minor glitches, but D|S is less forgiving.
Not sure how much of a difference this makes, but was the multi-object file you loaded a .cr2 figure or a .pp2 prop? Both Poser file types can include multiple objects with no problems, but the only way to do the same with saved D|S files is to save each bit separately as proper Support Assets, then save a Scene Subset with all the bits together in one scene.
Just remembered, it might also be a .pz3 Poser scene file — these include a lot of data that D|S can't use, and in this case it's definitely better to save everything as Support Assets and reassemble the bits and pieces into a proper D|S scene.
Thanks Kitty.
I loaded the Big Office through the Content Library tab. It's a pre-loaded pp2 prop group that contains everything, but not a pz3 scene file.
The problem doesn't seem to be getting the stuff into DS, but more about saving it correctly.
Anyway, I rebult the scene in DS again and did all my rendering without closing it. This one was also mess up when re-opened, but it doesn't matter anymore.
If your saving as a scene subset (the easiest way to save into studio) you need to be sure that your saving into the studio section and not in the poser files.