Rhino 6 Proxy Geometry errors
Posted: Sat Jan 12, 2019 2:01 amHi,
I have been working with octane render plugin for Rhino 6 (previously with Rhino 5). As part of our office we use proxy blocks with all our vegetation/trees for visualisation. The process is great as we can duplicate blocks and have the same tree mulitplied across a scene with very little effect on rendering time and the ability to move these blocks around is also great. Unfortunately there seems to be a glitch/issue with this process in Rhino 6. It seems that when ever we try to have 1 block that is linked to a tree, Rhino 6 octane only renders it at the origin point and will not move. This means all the trees get stuck at the origin and don't move at all.
These are the issues i've identified:
1. Trees that are linked to a proxy block get stuck at 0,0,0 and cannot be moved with the block.
2. Re-opening rhino deletes all the proxy geometries and they have to be reapplied (or they get stuck at the origin oncemore - meaning we have to delete the proxy and reapply).
3. Proxy geometry cannot be duplicated using the one block copied and pasted. Now the only workaround seems to be having a separate block for every tree that we want in the scene (if we want this to move around with the block). In this case, upon re-opening rhino should the file crash or we wish to close the file, then all the proxy geometry will be reset and trees will only render at the origin point (0,0,0).
4. When I open my file in Rhino 5, all of these issues do not occur - meaning we have to backsave our rhino 6 file in order to render our trees.
I've attached images that attempt to describe what I am saying.
The proxy geometry (with obj trees linked)
What the render produces in Rhino 6 using octane render plugin
I have been working with octane render plugin for Rhino 6 (previously with Rhino 5). As part of our office we use proxy blocks with all our vegetation/trees for visualisation. The process is great as we can duplicate blocks and have the same tree mulitplied across a scene with very little effect on rendering time and the ability to move these blocks around is also great. Unfortunately there seems to be a glitch/issue with this process in Rhino 6. It seems that when ever we try to have 1 block that is linked to a tree, Rhino 6 octane only renders it at the origin point and will not move. This means all the trees get stuck at the origin and don't move at all.
These are the issues i've identified:
1. Trees that are linked to a proxy block get stuck at 0,0,0 and cannot be moved with the block.
2. Re-opening rhino deletes all the proxy geometries and they have to be reapplied (or they get stuck at the origin oncemore - meaning we have to delete the proxy and reapply).
3. Proxy geometry cannot be duplicated using the one block copied and pasted. Now the only workaround seems to be having a separate block for every tree that we want in the scene (if we want this to move around with the block). In this case, upon re-opening rhino should the file crash or we wish to close the file, then all the proxy geometry will be reset and trees will only render at the origin point (0,0,0).
4. When I open my file in Rhino 5, all of these issues do not occur - meaning we have to backsave our rhino 6 file in order to render our trees.
I've attached images that attempt to describe what I am saying.
The proxy geometry (with obj trees linked)
What the render produces in Rhino 6 using octane render plugin