OTOY Forums

Hey,
I tried both sandard projection and triplanar, with a Transform 3D node, I have not success to move texture with translation. it stay in same place with differents values, I dont understand.

Using Octane 2020 RC2
Windows 10 - GTX 1060 6GB
Houdini DCC

I found the issue the Transform node need a Y rotation > 0 else not the texture translation no work. I setup to a very small rotation (0,001), and translation work.
https://ibb.co/0jfngBy

With this rotation tip Iam unable to move the Z Translation by an attribute in houdini. I think its broken. When I move Z attribute translation, the texture move fine, except with a Attribut import. Its very tricky with octane (In arnold or redshift every things is supported )

Sorry, can you share an example scene with this issue? Here the transform 3D node can displace the texture over an UV mapped object without problems.

Thanks,
-Juanjo

Thanks for the test from your side, I think I have different configuration because I want a Box projection :
http://host.electroheadfx.fr/efxbox/lau ... oudini.zip

When rotation are to zero, the translation no work except if you set Y Rotation to 0,01

The project
http://host.electroheadfx.fr/efxbox/lau ... oudini.zip

Hmm, what Octane version are you using? Here the translation works fine. In your scene, I can use the transform node, X and Z translation to move the texture over the plane.

Be aware that the translation is a float value with a 0.0 to 1.0 range to move the texture over the whole UV space. That means that a translation of 200 is the same as 0, or 1 or 10 ... try for example 200.2

Thanks,
-Juanjo

It was the issue Juan ! I move too fast in unit value (x1, x10) so I didn't see the change. Thanks

Technically is it possible to move this translation data by any attribute ?

I tried with a color attribute called translation (vector) and connected to translation transform, it doesn't work.

v@translation = set(0.5,0,0);

I connected translation to albedo, I can see the data, but is work on a vector data in any node ???

Nope, sorry. I'm afraid that the transformation parameters can't be managed by attributes currently. The attributes only work for shading, but not to drive other parameters. I'll raise this feature request to the core devs.

Thanks,
-Juanjo

ok, thanks @juanjgon.
see you