Is this a bug, Procedural texture uses doc (x, y, w, h, etc.) even in an artboard?

[Ezbaze]

Here I have 2 artboards, one of them has a Procedural texture, and instead of using the x and y of the artboard it is in, it uses the x and y of the full bounding box of all artboards, meaning that the procedural texture breaks and changes based on the artboard position.

 

This is what it looks like without the other artboard:

 

I was expecting for it to at least take into consideration if it's inside an artboard

[Ezbaze]

I think there should be a way to at least choose whether the Procedural Texture uses the ( Document | Artboard that it's in | Parent ) for the variables (x, y, w, h, etc.) this would allow for Procedural Textures that depend on the position of the Parent to work as expected

[NotMyFault]

Use rx / ry instead if x / y.

you can the choose the origin by click-dragging.

Or add variables (type Z) and subtract that value.

PT Filter x/y only use canvas position. They are totally unaware of layer positions, even if clipped or nested.

Same apply to noise, even noise from color, and for every other filter (voroney etc).

[Ezbaze]

Just now, NotMyFault said:

Use rx / ry instead if x / y.

you can the choose the origin by click-dragging.

 

Technically yes, but even when using rx / ry, moving other artboards breaks the procedural texture / requires readjusting each time / i was hoping for this to not have any hard coded values ( inheriting them from the artboard instead )

[NotMyFault]

Unfortunately it is not possibly. I edited my earlier answer and added some more information.

[NotMyFault]

The only way to get relative position is by using linked / embedded .afphoto files.

But this opens another can of unfixed bugs and workflow issues.

[Ezbaze]

Yep, I was trying to use this in something that would require a procedural texture to at least take into account the artboard, which would have resulted in the least hardcoded values as a whole, as this wouldn't work on just the document / there would be more than inside a document so this will break no matter what.

 

What do you think of the solution I mentioned above?