RailClone > RailClone Pro (*)
not using objects as instances?
JS4753:
Hey,
I have a question about Railclone Pro. I created a roof with tiles and am now trying to render it with Octane Render. Thereby I encountered 2 problems:
1. Although in in the display rollout Render Mesh is chosen, octane renders the railclone objects as boxes as they are shown in the viewport. Only if i switch to mesh in the viewport, octane renders the real geometry. But ofc the viewport is nearly dying about that amount of geometry :(
2. It seems as if Octane doesn't handle the tiles as instances (no matter if they are set as Octane movable proxies or not) but as single objects, so that the amount of geometry is huge.
Am I missing things or is Railclone not 100% compatible with Railclone? :-\ :'(
iToo:
No, RailClone doesn't include instancing support for Octane. RC objects are rendered as an unique mesh object.
1. I cannot reproduce the problem here. Objects are rendered correctly (as a huge mesh), regardless of the Display selected mode (Max 2014, Octane 1.20, RC 2.1.6).
2. As described above, that will not work. Anyway, you can convert a RC object to instances using RailClone Tools.
In this case, i suggest you use RailClone Tools. The procedure is not automatic, but it works fine with Octane..
JS4753:
Ok thx for your answer! I did it with instancing now... It would be really really great if you would make the instancing work in combination with Octane in the future. Do you think this will come soon?
I still have the viewport error occuring (rendering the boxes even if mesh is activated). Maybe it's the same reason for which my Itoo forests disappear in the viewport. I still didn't figure that out...
After instancing the geometry is correct.
Now that I know that there are some incompatibilities with Octane, is there anything special about the octane-materials and the railclone-objects or does it work the same way as normally (with the multi-sub-materials)?
Kind regards :)
iToo:
Unfortunately we cannot add instancing support without the collaboration of the Octane developers. Recently we have included in RailClone an interface for rendering engines, and we sent the documentation to the main companies. So, hopefully new engines will be supported in the future, although until now we got no reply from Otoy.
It's strange the viewport error, because in Octane RailClone objects are handled as standard Max objects (which returns a mesh). We'll do more tests. This problem is not related with the Forest issue, because it works in a different way.
There are not special requirements regarding materials, multi-subs should work fine once converted to Octane. For this purpose, we include standard materials with the RailClone library, which are very suitable for the material converters.
RU3562:
--- Quote from: iToo on December 29, 2013, 09:03:49 AM ---Unfortunately we cannot add instancing support without the collaboration of the Octane developers. Recently we have included in RailClone an interface for rendering engines, and we sent the documentation to the main companies. So, hopefully new engines will be supported in the future, although until now we got no reply from Otoy.
It's strange the viewport error, because in Octane RailClone objects are handled as standard Max objects (which returns a mesh). We'll do more tests. This problem is not related with the Forest issue, because it works in a different way.
There are not special requirements regarding materials, multi-subs should work fine once converted to Octane. For this purpose, we include standard materials with the RailClone library, which are very suitable for the material converters.
--- End quote ---
Hello I've been suffering from the instance support with the octane renderer.
As I see that this topic a bit outdated. And octane has improved in some ways.. I wonder if any other attempt to make it work with Otoy, octane render ?
I'll be asking for the instance support in the octane licence owners forum. But I wanted to ask you first.
Best,
Navigation
[0] Message Index
[#] Next page
Go to full version