Refraction UV Problems

[Ben]

Hi,

I'm currently attempting to create a shader with a panning texture map driving the refraction node for a ripple effect. I have made on of these style shaders before with amplify, but I needed a different one. For some reason, the refraction isn't following what the texture is doing. However, when I plug the same map into the albedo channel, it displays as intended.

I went back to one of my previous shaders and I noticed that one was no longer working either. After having a look at the text code, I noticed that when the shader uses a texture for the refraction slot, it creates a new texcoord. However it doesn't initialize it. In this example, you can see the albedo using texcoord_0 and refraction using the uninitialized texcoord_1.



Is this a bug or am I missing something? Sorry if this has been confusing, Im having difficulty explaining the problem.

Cheers,
Ben

[Amplify_Borba]

Hello Ben,

Thank you for getting in touch and for taking the time to report this issue!

Would it be possible for you to share with us a shader sample with the issue present?

That would be extremely helpful in helping us pinpoint the exact problem, thanks!

[Ben]

Sure thing, what's the easiest way to upload a file to the forum?

Apparently the 'upload attachment' function doesn't allow shader files to be uploaded.

[Amplify_Borba]

Sure thing, what's the easiest way to upload a file to the forum?

Apparently the 'upload attachment' function doesn't allow shader files to be uploaded.

You can either zip the file, or simply send it through wetransfer to [email protected], thanks!

[Ben]

Ah cool, I'll stick it in a zipped folder then.

[Amplify_Borba]

Thank you for sending the shader sample, we'll get back in touch as soon as we have any related developments.

[Amplify_Borba]

Hello Ben,

Hope everything is well!

We have confirmed and fixed the refraction issue you've reported.

Please download the latest build from our website, which would be v1.3.7.006 – 15th November 2017 – Stable at the time of this post, and if possible confirm that the issue has been resolved on your side, thanks!