Broken Cubemap in 4.2

Development Rendering
, , , ,
1

I’m having an issue with a cubemap which results in what looks like bad texture coordinates.

The problem only appears when I deploy to my phone and only started happening when I moved to 4.2 from 4.1, on 4.1 everything was fine.

On 4.2 the cubemap appears perfectly fine in the editor as well as mobile preview, it just becomes distorted when on the phone.

I wondered if there’s any suggestions out there on how to fix this issue?

Thanks

Here’s my material:

9963-mat2.jpg
9963-mat2.jpg1059×1271 226 KB

2

I would guess it’s due to low precision in the pixel shader on device. Phones use half precision for pixel shader operations, like anything plugged into Emissive or BaseColor. Vertex shaders will usually use full precision, which is inputs like WorldPositionOffset, CustomizedUV. Try using Customized UVs to pass through your computed UV, and then only do the texture lookup in the EmissiveColor chain.

3

Thanks for the reply, I will try that, however it seems very odd that it worked perfectly fine on 4.1 but on 4.2 its broken, has this precision change happened in that update?

Visually it kind of looks like the texture is being border clamped, its quite odd!

4

Just to bump this, I have tried using CustomizedUV, however these pins do not accept a 3D vector as the texture coordinate which is what is required for a cube map.

It seems like a bug that was introduced in 4.2 to be honest since it worked on 4.1, I will try on 4.3.

But any further info would be much appreciated.

Thanks

5

Looks even more broken in 4.3, would appreciate any suggestions on what this could be.

Thanks