Search Issue Tracker
Fixed in 4.0.0-preview
Votes
0
Found in [Package]
3.1.0
Issue ID
1068046
Regression
Yes
(Need Sprite Master Node) Sprite Renderer doesn't update ShaderGraph time properties when it is viewed from a certain distance
How to reproduce:
1. Open user-submitted project (TheVoidTest2018.zip)
2. Open "samplescene" scene
3. Ensure "bgStar" game object has "BGStars" shader assigned to it
4. Play the scene
5. Switch to scene view
6. Switch fog options for scene view
7. Zoom in and out of the scene
Expected result: Sprite renderer feeds time to the shader independently from the distance to the camera
Actual result: Sprite renderer stops feeding time to sprite shader once a certain distance from the camera is reached
Reproducible with: 2018.2.3f1, 2018.3.0a8
Could not test with: 2017.1, 2017.2, 2017.4, 2018.1 (Project compatibility issues)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 4.0.0-preview):
Not fixed in 4.0.0-preview but checked in 4.0.0-preview