This requires full precision floats in a pixel shader, and 4.13 has an option for that.
Using ScreensAlignedUVs material node on some devices does not render correctly at farther distances.
Devices tested with:
Working: iOS 5s and Pro
Working: S7 Edge - SM-g935P
Working: LG G4S - LG-H735
Not Working: Samsung Galaxy S5 - SM-G900P
Not Working: Nexus 5
Not Working: LG G2 - LG-D802
Not Working: Samsung Galaxy Tab 4 - SM-T530
Not Working: Samsung S4 Mini
1. Create a Mobile Project
2. Create a Material using the ScreenAlignedUV node plugged into a Texture Sample plugged into the Emissive Material input.
3. Make the material Two-Sided
4. Add a Sphere to the default level and scale it really large
5. Deploy to device
6. Pull back the camera until you see the issue (screenshot below)
Regression: No
Results: Looks like a distance precision issue for some devices when using the screen aligned uv node.
How does TextureRenderTarget2D get TArray<uint8> type data?
Why does the REMOVE method of map container remove elements have memory leaks?
How do I set a material as a post-processing material?
How to delete some elements correctly when deleting an array loop?
What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?
UMG RichText not appear image when packaged
What is the difference between Camera and CineCamera?
How does TArray loop correctly remove elements in blueprints?
Head over to the existing Questions & Answers thread and let us know what's up.