Every time I try to render my model in raytraced view the brick turns black, I have tried this in multiple different models and the same problem happens every time. I work on Mac.
How can I fix this?
This is how it is supposed to look like in rendered view:
Please run SystemInfo in the command line of Rhino8 and post the popup content here. Thanks.
Please copy and paste the complete pop-up content here, thanks.
Please select an object that turns black, then export it as a new rhino 8 file. Make sure you check Save Textures and say yes to embed if asked. Then share that new file here for further investigation.
systeminfo.txt (4.1 KB)
Oh, here
Hi, I tried but the file is too big…
Just one object is needed, not the entire file. If it still is too big for uploading here you can upload using our uploader. I have prefilled my email address so I get notified when the upload has finished. Please also copy&paste a link to this discourse thread in the comment section.
Sent it
@Aleksander_Ainsley you have subsurface scattering turned fully on with black as the scattering color.
Turn off the subsurface scattering (amount to 0.0) and it’ll look good.
Note that you also have a displacement texture, but since your geometry is already displaced it is better to turn off - and much faster to get started Raytracing.
Hi, thanks for the help. I tried this and it worked with the material, but now it just makes the whole thing pixelated.
rendering fine here- what are you quality settings in the rendering preferences?
something weird going on… your runtime for the rendering was :02…that’s not long enough unless you have some sort of magic mac…
it’s :27 on my pc with a huge video card. It’s 1:47 on Nathans mac.
what happens if you run it in the standalone renderer?
I’d disable the displacement channel (click the light bulb so it changes to the unlit bulb).
If you want to help investigating more what could be happening you could go to Rhinoceros > Settings > Advanced, then in the search bar type VerboseLogging. Turn the setting RhinoCycles.VerboseLogging to true, then restart Rhino.
Open the scene you showed with the blocky stuff and once Raytraced says it is done and the result is still blocky run the command RhinoCyclesShowLog. Copy&paste the text, save as a text file and attach that here in a reply please. Thank you.
RhinoCycles_log.txt (1007.9 KB)
Thank you. I don’t see anything out of the ordinary in most of the log. Am I seeing it correctly that rendering initially is fine, but then at some point after some changes while Raytraced is active you see this blocky result that stays like that? I’m not sure why this would happen though, so it would be helpful if you could keep an eye out for a pattern of actions that leads to this.
On another note as a matter of model optimization for rendering, I’d extract the render mesh of this brick leg and hide the original, use the mesh for rendering purposes. You can get the displaced mesh with -_ExtractRenderMesh. This will make it so that only one object is sent to RhinoCycles instead of a huge amount. It will make data processing much, much faster - you should be able to turn back on the displacement channel in the pbr material as well, the processing won’t take as long as with the original object.
Also, if you want faster rendering and you don’t mind pixel differences between two runs (pretty much undetectable by human eyes) then you could go to the advanced settings and search for AdaptiveThreshold, set it to 0.1. You should find that in most cases rendering will be finished considerably faster.
I also like to replace the shadows-only groundplane with a simple plane large enough to capture the shadow - this is of course not a solution if you want to composite your render onto other images, but if you don’t do that then replacing the groundplane will also give you rendering speedups.
Here down from ~1min30s to 7s on my M2 Ultra with above tricks applied
