Did the Depth of Field values change recently? I haven’t looked at this tool in a couple of months, but the values that I used before are not giving the same results anymore. @nathanletwory or anyone else at McNeel?
I can try to crank up the Blur Strength to compensate, but it still doesn’t give the same effect. Note that the blurring is more pixelated and less smooth in this version.
Hmmm. I’m not sure how it is implemented here, but I would always choose physical DoF over the Post-Effect. I think most of the Rhino post-effects could be binned.
Do you have no luck setting the proper camera DoF (Focal Blur) in Rhino 8?
Thanks for the insights, @David53. Focal Blur does still work for me, but the post-effect had been a simpler interface and faster process, which worked quite well from Rhino 7 until some recent update within Rhino 8.
I’m teaching this concept to classes of new CAD modelers and the post-effect version was by far easier to teach with. The results were predictably good (until very recently), you only have to click in one spot, and changing the values doesn’t cause the cycles to start over from the beginning which saves LOTS of time.
@MikeM From looking at your screen shots, the second one has a completely different Focal Distance value. Did you change the value - or did Rhino somehow parse it incorrectly?
The issue that we’re aware of is that if the ground plane is enabled it’s hard to get Depth of Field to look good. But there is no ground plane enabled in your file.
Hi @DavidEranen
I noticed that too. The different focal distance was part of what made me think that the feature had been worked on recently.
This particular file is part of a class project, so I can say with some certainty that I picked the same, or very similar, place for the focal point back in March as yesterday.
I’ve had this same issue on a couple of computers with different specs. Here is the SystemInfo from one I have access to today. Instructor 212 Rh8 System Info.txt (2.6 KB)
I very much dislike the groundplane, too. In my opinion it is (for Raytraced and Rhino Render) better to just add your own surface. There is full control over that surface, the groundplane in Raytraced and Rhino Render is pretty much always too big. And the shadows-only feature makes renderings considerably slower.
Not to poke, but I am poking on this issue. You mention that you were aware of this issue with the ground plane enabled. However, there is no ground plane enabled in my file. Does this get added to your YouTrack file for this issue, or should it get its own?
I’ve found that there is an issue with RhinoRender’s depth channel which is causing problems with the Depth of Field post-effect. This problem is fixed in Rhino 8 SR 13. Please test SR 13 and let me know if it fixes the issues that you’ve been seeing.
Here’s how to get SR13: Help → Check for Updates… → Update Frequency. Select “Service Release Candidate”. Then press Check now.
