Search Issue Tracker
By Design
Votes
0
Found in
2017.4.4f1
Issue ID
1042558
Regression
No
Different timing and available property value range in play and edit modes, when animating shader properties
To reproduce:
1. Open project
2. Open 'Tester' scene
3. In Hierarchy select 'Mistwraith'-> 'Mesh' and preview the animation
4. Notice animation timing, and that values range is [0,1] for 'MistDisplace' material shader A and B properties
5. Enter play mode
6. Notice that animation timing is different and that values range is [1,2] for 'MistDisplace' material shader A and B properties
Reproduced: 5.6.5p1, 2017.1.4f1, 2017.2.3f1, 2017.4.3f1, 2017.4.4f1, 2018.1.2f1, 2018.2.0b5
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:
Workaround provided. Mis-use of LoopPose.