- Tue Oct 13, 2015 4:05 pm
#388821
Some colleagues who are using Rhino are experiencing problems with scenes created in Rhino. Somehow displacement gets in the scene, but won't/can't be purged. When sending the scene to Maxwell the renderprogress explodes somewhat in RAM and everything freezes up or simply crashes. Fire does work in Rhino, but that's not taking displacement into account?
Unchecking "displacement" in studio does solve the problem. First we thought displacement was still in the scene somehow, but we can't find any proof it was in and it's certainly not in anymore. It looks like displacement sneeks in
We are still running 3.1, update will hopefully be for the end of the year. Maybe we do something wrong, but the problem was not occuring before?
Help is much appreciated
Unchecking "displacement" in studio does solve the problem. First we thought displacement was still in the scene somehow, but we can't find any proof it was in and it's certainly not in anymore. It looks like displacement sneeks in
We are still running 3.1, update will hopefully be for the end of the year. Maybe we do something wrong, but the problem was not occuring before?
Help is much appreciated
@ Home: Maxwell Render V3.2 / Rhino v4 / Blender 2.76b / Windows 10 on HP Z400 / Wacom Cintiq 24HD
@ Work: Maxwell Render V3.2 / Rhino v5 / Blender 2.76b / Windows 7 on HP Z420 / Wacom Cintiq 27QHD
@ Work: Maxwell Render V3.2 / Rhino v5 / Blender 2.76b / Windows 7 on HP Z420 / Wacom Cintiq 27QHD