rest state for proceduaral textures
Moderator: juanjgon
As far as I can tell, nothing has been added relating to this recently. I don't quite understand why UV coordinates can't be used for this purpose. The OP talks about "seams" caused by the use of UVs but I don't quite understand why that would be the case unless we're talking about multiple objects each with their own UV space.
Hello,toby_a wrote:As far as I can tell, nothing has been added relating to this recently. I don't quite understand why UV coordinates can't be used for this purpose. The OP talks about "seams" caused by the use of UVs but I don't quite understand why that would be the case unless we're talking about multiple objects each with their own UV space.
because the procedural textures are sampled in uv space( 2D), you get discontinuous textures where the uvmap is discontinuous ( islands ). If it were sampled in 3D space, it would be seamless.
viewtopic.php?f=24&t=80814&p=419149#p419152Goldorak wrote:For architectural and stability reasons it was my call to push Rest position and the remainder of the brigade kernel work to to the next release - 2023.1 - already well underway, see the blog post update on the home page. We will begin testing in the same slack group we used for 2021 beta.
Win 10 64bit // GTX 4090 + GTX 3090 // 5900x // 64GB // SideFX Houdini // C4D
Hi, thanks for the clarification. Would it work for your usecase to generate an additional UV set that doesn't have the discontinuities (for example using the UV Project Sop)? If you name the addtional UV set "uv2" and promote it to a primitive attribute then you should be able to use it in the Mesh UV Projection node in Octane as UV set 2.WoutTgh wrote:Hello,toby_a wrote:As far as I can tell, nothing has been added relating to this recently. I don't quite understand why UV coordinates can't be used for this purpose. The OP talks about "seams" caused by the use of UVs but I don't quite understand why that would be the case unless we're talking about multiple objects each with their own UV space.
because the procedural textures are sampled in uv space( 2D), you get discontinuous textures where the uvmap is discontinuous ( islands ). If it were sampled in 3D space, it would be seamless.
Hello again,toby_a wrote:Hi, thanks for the clarification. Would it work for your usecase to generate an additional UV set that doesn't have the discontinuities (for example using the UV Project Sop)? If you name the addtional UV set "uv2" and promote it to a primitive attribute then you should be able to use it in the Mesh UV Projection node in Octane as UV set 2.WoutTgh wrote:Hello,toby_a wrote:As far as I can tell, nothing has been added relating to this recently. I don't quite understand why UV coordinates can't be used for this purpose. The OP talks about "seams" caused by the use of UVs but I don't quite understand why that would be the case unless we're talking about multiple objects each with their own UV space.
because the procedural textures are sampled in uv space( 2D), you get discontinuous textures where the uvmap is discontinuous ( islands ). If it were sampled in 3D space, it would be seamless.
I don't see how that would work as any good uv map will always have seams. If you don't, that means you're simply flattening the mesh which means overlaps and those will of course be visible when used for texture sampling. In any case, I kinda hacked together a OSL shader ( above) that works quite well, with the exception of normal/bump mapping, something is off with that :p
OK, I don't know if I'm completely understanding this, but it sounds like it's important to have a 3D texture coordinate rather than a 2D one and I will take your word for it!WoutTgh wrote:Hello again,toby_a wrote: Hi, thanks for the clarification. Would it work for your usecase to generate an additional UV set that doesn't have the discontinuities (for example using the UV Project Sop)? If you name the addtional UV set "uv2" and promote it to a primitive attribute then you should be able to use it in the Mesh UV Projection node in Octane as UV set 2.
I don't see how that would work as any good uv map will always have seams. If you don't, that means you're simply flattening the mesh which means overlaps and those will of course be visible when used for texture sampling. In any case, I kinda hacked together a OSL shader ( above) that works quite well, with the exception of normal/bump mapping, something is off with that :p
It sounds like your solution using the "rest" attribute via an OSL projection node is working well, and until Octane gets built in support for rest position is probably the best that can be done.
Are you able to create a simple scene that demonstrates the problem with normal/bump mapping?
That's exactly righttoby_a wrote: ... sounds like it's important to have a 3D texture coordinate rather than a 2D one ...
I don't really have the time for this at the moment, perhaps latertoby_a wrote: Are you able to create a simple scene that demonstrates the problem with normal/bump mapping?