Object space mapping is broken Tweet

[senorpablo]

I'm rendering an animation and am having issues with object space mapping. What I'm seeing is that object space mapping behaves like world space mapping. In other words, the texture doesn't maintain position relative to a moving object. Rather, it behaves like world space mapping, where the textures appears to remain fixed in space, and scrolls across a moving object.

After searching, I've found a thread in a Modo forum whereby someone describes that movable proxy needs to be enabled for object space mapping to work correctly on animated objects. It does seem to solve the problem.

In addition to object space mapping not working as expected, the scale changes (presumably if there's a scale transform on the object).

Object space mapping is a straightforward concept which Octane's implementation doesn't live up to. It's inconsistent and unintuitive. Regardless of the underlying technical reasons for this, from a users perspective, I'd like to see a more elegant solution. Movable proxies can slow down Octane viewport significantly. Object space mapping should just work as the name implies, without having to know about a secret check box.