Cineversity

Hey,

I was following the tutorial for the return of stackable materials. To get it to work properly, I had to create a new render setting (my file was a little bit older).
Now, my pin material tag does not work on a model that has a bend deformer applied to it. The material is applied with flat projection.
I’ve rebuilt the setup and it still does it.
Summary: Texture slippage when using a deformation object on a polygonal object that has a flat mapped material and a pin texture tag.

Wondering if anyone else has run into this.
Note: Using Redshift as my render engine, and using R2023

(I went ahead and UV mapped my object, so I worked around it. But.. still wondering if anyone has this issue.)

Hi Wesware,

I would need a project file (Save with Assets; please reduce it to the one object that holds the material.)

Typically a texture that has a projection can be converted into a UV information, on a polygon object.

I can provide an upload link. (If you have a cloud service, please use only Amazon, Adobe, Apple, Google, Wetransfer, and Google.)

All the best

*ATT*

I have already created a UV map for the object but I can revert it back to “Flat” with a Pin Material tag to show you what’s going on.
I’ll post a link in a bit. Thanks.

Hi wesware,

Yes, I can reproduce it here.

Since I like UV, I haven’t used Redshift 3D and Pin Material.
The last question about slipping was based on noise shaders (set wrongly), hence my question for a file. No need; I reproduced it.

However, I will file a report and see what happens.

Have a great Sunday

*ATT*

Great, thanks!

You’re welcome, wesware.

For me, Redshift 3D targeg is to be fast. So, all the information we can provide, as you did with creating UVs, is aligned with that target.

As a side note: Currently, I have started collecting “ideas” on how to slow it down, as I have seen it here and there, to get, maybe in a while, a nice list of tips on how to keep the speed and not slow it down. It is all about information flow and, on the other side, what needs to be calculated each time newly. Here we can improve (or better: keep) the performance of Redshift high.

Thanks again for pointing the Pin material problem out; with RS now natively onboard as render-option, this needs to be addressed

My best wishes