Search Issue Tracker
Duplicate
Votes
0
Found in
6000.0.54f1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-112204
Regression
No
NullReferenceException errors appear in the Console when changing the values of Visual Effect Control Clip Events' Attributes
How to reproduce:
1. Open the “TestTimeline” project
2. Open the “ReproScene”
3. Double-click on “New Timeline” asset to open it in the Timeline window
4. Lock the Timeline window
5. Enter Play Mode
6. Click on the Visual Effect Control Track’s clip
7. In the Inspector change any value of Attribute (ex. increase the “Size” value)
8. Exit Play Mode
9. Repeat steps 5-8
10. Observe the Console
Expected result: No errors are thrown in the Console
Actual result: Numerous “NullReferenceException” errors are displayed
Reproducible with: 6000.0.54f1
Could not test with: 2022.3.65f1, 6000.1.13f1, 6000.3.0a3 (Reproduction is inconsistent)
Reproducible on: Windows 10
Not reproducible on: No other environments tested
Notes:
- Only managed to reproduce the issue once with version 6000.0.54f1
- Couldn’t reproduce the issue after re-opening the project
- Couldn’t reproduce the issue on any new project
-
Resolution Note:
We tried to reproduce on latest versions, but we were not able to.
Looking at the callstack and the version when it was found, it seems very likely that it is a duplicate of an existing (and fixed) bug in Timeline.
Please feel free to reopen if the issue is still reproducing with Timeline 1.8.9 or above.
Thanks for reporting this.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/TB-324
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
This is a duplicate of issue #-324