Object tag - hair thickness doesn't work here. Octane get thickness from C4D Hair material instead.
Manipulating hairs is HIGHLY unstable using Octane LV.
Moderator: aoktar
SSmolak wrote:Object tag - hair thickness doesn't work here. Octane get thickness from C4D Hair material instead.
Manipulating hairs is HIGHLY unstable using Octane LV.
aoktar wrote:Not sure what you mean with HIGH non-stability but there should be a problem with your side.
cph_visuals wrote:Bug in instancing.
There seems to be a bug with loading instances on the first frame of animation. The bug has been around for a few releases, but has been difficult for us to recreate, as there may also be some interplay with object motion blur calculations. We're working on trying to figure out if it's a separate bug or a part of this bug. At least removing motion blur from camera seems to fix the problem.
The attached scene shows the instancing bug in action. Basically on the first frame when the scene is generated instances are not rendered in the right position, second frame instances are correct. It is absolute hell when rendering on our render farm because any rerendered frame will be incorrect as it's the first frame.
To get around it we've stopped using render instances, but that limits us to 24GB cards, and gives us 50m+ poly scenes. Ouch.
Because of NDAs I'm unable to share actual production scenes, but it's a bug we run into all the time, especially using spline-bassed rigs + cloners.
cph_visuals wrote:The attached scene shows the instancing bug in action. Basically on the first frame when the scene is generated instances are not rendered in the right position, second frame instances are correct. It is absolute hell when rendering on our render farm because any rerendered frame will be incorrect as it's the first frame.
frankmci wrote:cph_visuals wrote:The attached scene shows the instancing bug in action. Basically on the first frame when the scene is generated instances are not rendered in the right position, second frame instances are correct. It is absolute hell when rendering on our render farm because any rerendered frame will be incorrect as it's the first frame.
If it's happening on the render farm it sounds like it's a core Octane Render issue instead of a C4D plugin issue. You should probably post this in the Commercial Support forum.
cph_visuals wrote:GUID fixes the issue, we initially thought that was a fix, but that merely disables object motion blur. This scene does not not have instance animation, but we've confirmed it internally across multiple installs.
In regards to the renderfarm: We're running C4D commandline on the nodes, and not Octane stand-alone, hence the post here.
@aoktar is there any place I should rather report this, seems like a bigger bug?
Users browsing this forum: No registered users and 5 guests