It looks like a GPU cache converts the entire scene to a single mesh, so it's not really good for rendering in Octane.p3taoctane wrote:Roeland See if these make any sense... or are of use to ya aye.
Peter
This is normal when the autofocus is enabled. Octane will automatically focus on the object in the center of the frame. If there is nothing in the center, then the focus distance is set to the value from the focal depth input.grimm wrote:I'm not really too sure how to describe this problem. All I did was to add a second render target node and connected it to the same pin on the geometry node as the first target node. When I rotate the view on the second target node the focus blur goes in and out as you move the camera. It's like at certain angles the focus doesn't work right? Focal depth doesn't change and always is set to 1.
That was the intended behavior. You can group the selected nodes together in a node graph, and any connection from or to a node outside the selection is automatically routed through a linker node. It is always possible to change the behavior but this may then be inconvenient if you need the grouping feature for a different reason.kavorka wrote:right now, it seems that if you group multiple materials, the ones not currently plugged in don't automatically create outputs.
anyone has this issue????
Code: Select all
-- find 'flashgroup', which is NT_GEO_GROUP
scene = octane.nodegraph.getRootGraph()
flashgroup = scene:findItemsByName('flashgroup')[1]
-- bug:
flashgroup:disconnectIx( N ) -- N appears to be Zero-indexed
flashgroup:connectToIx( N, node ) -- N appears to be 1-indexed
disconnectIx should be 1-based. We'll fix that in the next release.