You all know I love Rhino, and I have nagged about graphics for 20+ years, and it is time to nag a bit more. Rhino 8 just isn’t cutting it because of some stuff that should have been fixed years ago.
Bad banding. This is visually painful for anybody who works with visual representation. I am sure this could be fixed and worked around after a single workshop day if you guys wanted to solve it.
invisible transparent materials. They are a joke, no color and not enough reflections make them invisible a lot of the time.
Shadows needs super power. The sun needs it’s own memory slider, and most game engines support shadows from rectangular lights these days, we need that too.
Invisible tranpsarent materials:
What I don’t get is that when I turn on Raytraced then they suddenly pop forward with colors and all, right before the first render pass is going on. So Rhino knows how to show this stuff, it just doesn’t…
Banding:
We need to get rid of the banding. Banding is a 1990’s excuse, we never see that in any other programs because it just isn’t a valid excuse any more. It is just a problem that has to be solved, and if your colleagues aren’t up to it then you have to work around it. It’s just how it is. Raytraced mode just isn’t good enough in dark scenes when it gives us results like this:
I understand that something wrong is going on, because Rhino should be able to show more levels of dark gray than those huge steps shown above, so you need to sit down and look under the hood here.
Check this out: This is what we get from and all gray raytraced viewport:
It’s basically identical with the same banding and no dithering, so Rhino should be able to show the render in full quality with it’s 8bit viewport. I have adressed this many times since Rhino 6 started supporting cycles and it is time to fix it once and for all now.
If you want examples on shadows and sun then shout out.
I’ve had a very backwards experience, as I never started with Rhino Cycles.
Not sure if you are on R 8.5, but it seems a lot better than initial release.
As a separate note, it is a A little, and I mean tiny shame only about the timing really. Rhino 8 has adopted the Blender 3.3+ Cycles implementation; but the 3.6 LTS introduced some substantial changes including AMD HIP/RT GPU devices and Intel oneAPI/Embree GPU devices (both were fixed I think after rocky starts). At the same time, it would have been nice to throw away OpenGL 4.1 requirement and moved to 4.3(?).
I must say, it seems much easier to work with Rhino 8.5 Cycles now more of the items are syncronised between the viewport and the render settings; but there are still problems like the banding.
Yeah, I was looking into it, there are a few related issues that I was looking at. Apparently to get this working, our display pipeline needs to be changed from 8 bit to floating point.
I’m not sure if you have V-Ray, but they don’t enable gamma correction in rendered view. Since rendered view wants to match the gamma corrected rendered result better, gamma correction is applied to the image in the display (that is 8 bit) and that causes banding artifacts.
You will probably see the same effect when changing gamma in rendered mode to 1, and then copy the rendered mode view to PS and apply gamma correction there.
Oh, that makes sense, and that effects the render mode… OK so now I understand what you are talking about. Thanks. PS! Setting the Gamma to 1 removes the banding:
But changing the gamma while raytraced view was on crashed Rhino. I don’t know if that’s repeatable, but this is a step in the right direction, so if gamma can be applied before converting to 8bit, as you suggested, then we should be good to go on this one.
