funk wrote:I'm trying to load a previous orbx, which had animated displacement. I noticed that scrubbing the timeline is not updating the displacement now.
1. Load the attached orbx
2. Make sure youre at frame 0, and click the render target to start rendering
3. Look at the "wire" pass, so we can see the displacement clearer
4. Scrub the timeline to frame 60
NOTE: At this point, the displacement is actually wrong. Take a screengrab or copy the image to clipboard so we can use it later for comparison.
5. Press stop
6. Press start to start rendering again
The displacement has now updated and looks correct.
funk wrote:I'm seeing a new error in the log: "Tried to access null node"
While this is not obvious in standalone, the modo plugin pops up a dialog box every time a log error appears
1. Load the orbx
2. Go to window > create log window
3. Right click the glossy material > render
A log error appears:
Started logging on 12.11.19 21:59:25
OctaneRender Enterprise 2019.1.4 (6000400)
Tried to access null node
Bulwerk wrote:Is it possible to drive bend weight in the displacement mixer via vertex maps?
I'm using C4D and Octane of course it would be great to be able to use fields driven vertex maps as in this way.
Can this be implemented?
See my post in the C4D plugin forum outlining the issue.
samsue wrote:gpu fails scenes that were perfectly functioning in the previous version ...
J.C wrote:Sun position can be chosen as a value for non related properties:
Image resolution can be chosen as a value for non related properties:
Zay wrote:Yesterday I upgraded 1 of my the licenses as it will expire in 2 days. But when I try to sign in, it picks the wrong license.
How do I get it to pick the one I just upgraded?
J.C wrote:Intersecting volumes still have rendering issues on its boundaries.
Users browsing this forum: No registered users and 1 guest