Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2019.1.X
Votes
0
Found in
2019.1.0a12
Issue ID
1114526
Regression
Yes
Selecting track in Timeline while the Inspector is locked to GameObject with associated SignalReceiver causes Exceptions
How to reproduce:
1. Open attached project "InspectorLockSignalEmitterIssue_1" and scene "ProblemScene"
2. Select "Sphere" in the Hierarchy and lock its Inspector window by pressing the lock icon in the top right
3. Select "Cube" from the Hierarchy window to see its timeline
4. Click on any track in the CubeTimeline
5. Observe Console window
Expected result: Console window should remain empty
Actual result: Console window outputs multiple NullReferenceException messages
Reproducible with: 2019.1.0a12, 2019.1.0a13
Not reproducible with: 2019.1.0a11
Could not test with: 2019.1.0a10 and older (Timeline Signals not present)
Note: this only happens when the locked object is the receiver of a Signal track in the Timeline
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment