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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
Workaround provided. Mis-use of LoopPose.