Render error
Taoz
Posts: 10,258
in The Commons
A couple of times I've got a "Render error" in 4.8.0.59 with 3Delight, if I close the render window and try again (even after closing the scene) it says "Unable to Render. Renderer already in use." I guess it's a bug that it doesn't close the renderer when the error occurs?
BTW, I tried to shift to IRay last time it happened without closing the scene, and it started rendering without any problems.

Comments
I've run into that a few times. Iray will fire up even if 3Delight is running, because they're different programs, which require different processes.
As for getting 3Delight to behave after that, you have to shut down Studio. That was one of the things Poser did right starting with Poser 7-- They gave us a checky box to fire up Firefly as a separate process. If you had an issue with it, you could forcibly shut it down without killing Poser in the process.
Yes, shutting DS down seems to be the only solution. I actually thought 3Delight was running as a separate process, but maybe not.
There's a reason some people like an external copy of 3Delight.
I've been having this sort of problem since getting 4.6 in 2013. It's VERY annoying and quite inconvenient, especially when dealing with larger scenes. I hope that DAZ 5.0 corrects this issue!
I may be seeing something related to this.
On a large scene I had my 3Delight render come out blury. This was with the camera set with depth of field off.
I could not resolve this until I rebuilt the scene from scratch. Never had this happen in any previous versions before 4.8 Pro.
JD
I thought I read 4.8 updated the version of 3Delight but I don't see it in the change log.
http://docs.daz3d.com/doku.php/public/software/dazstudio/4/change_log_4_8_0_59
I would submit a support ticket through zen desk and it won't hurt to post on the 3Delight forums since Daz does not make any rendering engine option for Studio at this time
http://www.3delight.com/en/modules/forum/
The 3DL version in 4.8.0.59 is 11.0.130...
My guess is either the DoF was set oddly (not quite where you thought it was) or the pixel samples/ pixel filter were changed.
It's not in that change log because that's the second point release since the one that updated 3Delight.