Hi,
I get constant crashing when I use the depth of field option in cycles. I’m rendering an interior for a client but if I try to use depth of field it constantly and consistently crashes rhino. I sent in the bug/crash dumps. McNeel has my info it’s in the last thread I wrote in on cycles crashing.
RM
@3dsynergy the crash you are experiencing is in the post effect system, not Cycles crashing. This has already been fixed in what will become 7.11.
Until then I suggest that you disable the post effects while rendering. Especially with the denoisers as last in the effect list the problem happens more likely.
Hi @nathanletwory
Thanks for the quick reply. I don’t know if this matters since you’re fixing this but I only get the crash when using depth of field. I can use the other options and cycles doesn’t crash.
I did find one way to really kill cycles is to open another version of rhino and then run a rendering. I crashed so bad that cycles would not render but only displayed black even after restarting the machine. I found I had to rotate my view in the rendering, then render and cycles came back to life. it’s like the view was stuck and wouldn’t render. It’s these bad little bugs that make cycles still feel like beta software.
Related to my computer rig, I’m really amazed that you and others think that cycles can’t perform with my current hardware. I was rendering working in rhino and watching YouTube at the same time and cycles was flying and stable my renderings took about 7 minutes for good quality.
We need a physical camera I don’t see how one can adjust exposure without it except in post effects which seems really limited.
We need physical lights and with more options like ability to turn off a lights reflection in an object but keep its illumination. This area really needs work.
Environment map needs more options like rotation along the z and the ability to alter it’s horizon as well as a crop and place options ala 3dmax.
All in all love what you’re doing I just wish you weren’t limited by McNeel telling you what to include and what not to, we need the above things to really make cycles improve.
RM
It doesn’t matter. It will be a different post effect on different machines. But the crash is in the post effects system, which has been fixed already. It should become available as a fix for users in approximately 2 weeks.
What exactly crashed? You say “I crashed badly”, but that doesn’t tell me what happened. Did one of your Rhino instances disappear? Did your machine reboot?
I daily render with multiple Rhino instances open heavy scenes for testing, and have not had viewports stay black in a long while. Probably reasonably recent studio ready drivers help too.
Please try Rhino 7.10 service release candidate. There is some code that hopefully prevents Rhino going down in some cases of Cycles crashes - instead the viewport (if it is Raytraced going down) should switch automatically to Rendered mode.
Exposure control is on the wish list: RH-38985 Provide exposure control (Cycles camera).
Thank you for your concern, but rest assured we are working around the clock to improve rendering in Rhino in all aspects.
Yes one instance disappeared the one that I was rendering in. But after that even after rebooting my machine I reopened that and other files and Cycles renderings would only render black. I then closed rhino reopened rhino, reopened that same file that crashed and moved the camera and cycles kicked back on and now works.
But before that small change all my renderings though the progress bar worked and I even let Cycles complete would stay black I even changed my rendrerer from gpu to cpu.
Thanks for your help looking forward to your fix and improvements.
RM