D/S 4.5 Pro rendering errors
Ok, so I decided I'd been really naughty and the only way to properly punish myself was to try D/S 4 (4.5 Pro to be more exact).
There are so many things that it does that are weird I can't even keep track of all of them, but they are really only minor annoyances (maybe I'll ask these questions another time, as I'm sure there's a good reason Daz made the software behave so bizarrely, as if completely jacking up the interface wasn't enough).
Anyway, I get some really strange stuff in the little box that appears when you do a render. The render completes ok (except for the times when D/S unexpectedly terminates for no obvious reason), so I'm not really sure it's a problem, but it looks like a problem, so attached is what it looks like.
Is this anything I should be concerned about?
Edit to add: If it looks a little odd it's because the error is bigger than the little box (and Daz apparently didn't want me to be able to make the box bigger) so I cobbled it together in photoshop.
Comments
I am sure somebody can help, but in the meantime, here is what it says on the 3Delight site:
I just got the same errors again but the render was messed up in a way I have never seen. And sadly, even if I had screenshot it before Daz decided to go *poof* I couldn't post it here (naughty bits showing). So I'll take a shot at describing it in hopes that armed with a description and the errors above someone will have an idea.
Ok, so the render is of v4 sitting near some water. I wanted the surface of the water to be reflective so I made surface settings so it would reflect. I did a couple spot renders to check it was looking as I wanted and then went for it. Everything was as expected until it got to the water and started showing the reflection. In the reflection you can see v4's naughty bits even though she's wearing clothes (yes, in the reflection her pants are gone!). Also in the reflection, her right leg is cut off at the knee, and she has no left leg at all, though there is a hole where it would be if she were a doll.
The only thing I can think of that might be giving D/S a hard time is the reflective surface is also semi-opaque because I wanted some of the underwater details to show.
Edit to add: I must have crossposted with you Jimmy. Hmmm... I wonder if it's because all my runtimes are on an external drive.
Were the surfaces that didn't render using uberSurface? Just wondering if the Raytrace option was somehow set to off.
You should be able to get the full text of the error from the log file.