Page 1 of 1
Problem with Environment Texture & ColourCorrect Texture
Posted: Mon Apr 27, 2015 1:35 am
by MrFurious
Running Octane for LW 2.16
I have this node setup for my environment texture:
Octane Texture Image (HDRI Image) --> Octane ColorCorrect Texture (all values to default) --> Environment:Texture
I found when the ColorCorrect Texture is connected to the EnvTexture, I'm unable to change the heading or pitch rotation in the Env Texture node, and the heading rotation of the Texture Image seems to be locked to 270deg. When connecting the Texture Image directly into the EnvTexture it works as expected.
Re: Problem with Environment Texture & ColourCorrect Texture
Posted: Mon Apr 27, 2015 11:20 am
by juanjgon
Yes, this is know issue due to the plugin architecture, but in this case you can use the texture image U and V Translate parameters to get the same feature. The U Translate parameter controls the environment heading, and the V Translate parameter the pith.
-Juanjo
Re: Problem with Environment Texture & ColourCorrect Texture
Posted: Mon Apr 27, 2015 12:01 pm
by FrankPooleFloating
OMFG. I had no idea that U Translate changed heading. I was trying to use UV Rotation.. with undesired results...
Strange thing is, U Translate seems to work when you have a CC node in between, but not when you have Texture Image plugged directly into Env:Txtr...

Re: Problem with Environment Texture & ColourCorrect Texture
Posted: Mon Apr 27, 2015 12:22 pm
by juanjgon
FrankPooleFloating wrote:OMFG. I had no idea that U Translate changed heading. I was trying to use UV Rotation.. with undesired results...
Strange thing is, U Translate seems to work when you have a CC node in between, but not when you have Texture Image plugged directly into Env:Txtr...

Yes, this is because the Octane environment node doesn't have the heading and pitch parameters itself. What happens is that the LW environment node overrides the texture image U and V Translate parameters with the Heading and Pitch values, but this only works if the texture image node is attached to the environment node.
-Juanjo
Re: Problem with Environment Texture & ColourCorrect Texture
Posted: Mon Apr 27, 2015 1:40 pm
by MrFurious
That is bizarre behavior, but all seems to work thanks for clearing that up.
The Translate U automatically rotates the texture 270 degrees so you need to offset this by initially adjust the 'heading' (Translate U) just to have the texture in the same position as before. A few math nodes places the texture in the same position using CC node, than if you were to bypass the CC node and have zero heading rotation in the environment texture:
Re: Problem with Environment Texture & ColourCorrect Texture
Posted: Mon Apr 27, 2015 2:30 pm
by juanjgon
Yes, I know that the the behavior of the rotation/translation stuff is not the same. Your node setup is right to correct the environment heading and pitch.
All this behavior comes from Octane 1, that didn't have the current Octane texture projection modes. The Octane 1 texture environment had the heading/pitch parameters, but they were deprecated and replaced by the texture image projection node parameters. To don't break the compatibility with the old scenes and workflows, the plugin is using this "old" heading/pitch parameters in the environment nodes to drive the U/V translate parameters in the attached texture image node, overriding the image node values, but currently I only can override the parameters if the texture image node is attached to the environment node.
If now I change this behavior, removing the deprecated heading/pitch parameters in the environment nodes, a lot of old scenes can be broken, so it is best to at least in Octane 2.x don't change it
-Juanjo