Thanks for providing the second scene. I think the issue is that the enabled state of the Group is being taken by the "value" of the enabled channel at that frame, rather than evaluating the inputs to the channel. I don't think this is a trivial fix, so I suggest working around the issue.rob2576 wrote:I have added 4 keyframes to this file now. If you look at frames 1 and 2, I keyframed the enable channel of Group 1. When viewed in the Octane live viewer, the cube changes from red to blue when you go from frame 1 to 2. So when I animate the enable channel directly for the material group Octane sees this just fine.
Moving to frame 3 and 4, I keyframe the "LocatorToChangeMaterial" user channel "BoxMaterial". Group 1 is disabled through the schematic in this case. Octane does not see this second keyframed change but it does see the first. The Modo preview render sees the second change but not the first. I would expect the second outcome from Modo as channel values are locked out of direct keyframing once they are being driven by a schematic.
I would think this is a Modo bug except that the Modo Preview is acting like I would expect and Octane does respect the directly keyframed enable channel. It does not seem to get the change
I can see how your solution would work, however, there is a lot of power, for us, in the Octane plugin translating Modo materials so directly and we use this extensively in our workflow. We only make overrides when we enter into more specialized materials. If we must make an override for every material to make these setups work, it will defeat the usefulness of the plugin translating.
Users browsing this forum: No registered users and 4 guests