OTOY Forums

I’m having weird thing in Octane Blender 3.2, in render view I’m setting material with basic texture map, changing UV and it changes in edit mode but once going out to object mode the changes in UV are ignored. Restarting render doesn’t help UV stays the same, what could be the problem?

It might be a Blender bug, are you able to try the Blender 3.3 version of the plugin? It might be fixed in that version.

Thanks Grimm for your comment, unfortunately I am using blender octane prime (free tier) so 3.2 is the newest. It rather is octane bug, in other thread user named opstyix gave me workaround for displaying textures in viewport (because it’s not working as well) and it fixes frozen UVs problem too, adding blender texture node and blender output node, then setting UVs using eevee for preview and then when going back to object mode makes octane respects the new Uv layout
Of course it would be very painful to work like that all the time in normal projects, so I think I’ll stick to octane 4 as long as I can
Do You use 3.3 ? does material preview or texture preview work in 3.3?

Glad the workaround helped! Just wanted to chime in to say that the bug is also present in the latest Blender Octane Test build 2022.1.XB3 27.3 beta, which is based on Blender v3.3.2.

Just wanted to chime in to say that the bug is also present in the latest Blender Octane Test build 2022.1.XB3 27.3 beta, which is based on Blender v3.3.2.

Thanks for the info opstyix! I was curious about that

We'll fix this issue. Meanwhile, setting the Object Type to Reshapable should help.

I can confirm the same behavior in 2022.1 XB4 (blender 3.3.2) - lots of very odd and unexpected behavior around the UV editor, sometimes I have to delete cameras to get out of it, very disruptive for the workflow. (win10, 3080ti, nvidia 516.94)

I have a stupid but effective method, click on the object CTRL+A, select "Transform All", or right click, reset the origin, one of these two operations will always be useful, this is the method I discovered by accident. This bug has been around for a long time, and I'm annoyed that it's still not officially fixed.

This should have been fixed already. I'll check, odd if it's still there.

Just checked and I can't reproduce the issue in latest 2022.