Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.3
Votes
6
Found in
2018.4.9f1
2019.2
2019.2.17f1
2019.3
2020.1
Issue ID
1211380
Regression
Yes
Dynamic functions unavailable when private generic UnityEvent<T> fields have [SerializeField] attribute
Steps to reproduce:
1. Open the attached project (case_1211380.zip)
2. Select the "Test" Game Object
3. Click the plus icon under "Derived Event Bug ()" (expand "Container" if not expanded already)
4. Select "Test" as the Object
5. Click on "No Function" and navigate to BugExample context menu
Expected result: EventHandler can be selected as a dynamic function
Actual result: Only the static EventHandler function can be selected
Reproduced in: 2018.4.9f1, 2019.2.18f1, 2019.3.0f5, 2020.1.0a20
Not reproducible in: 2017.4.36f1, 2018.4.8f1
Notes:
- In 2018.4.9f1 & 2018.4.10f1 dynamic functions are unavailable for all generic UnityEvent<T> fields
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
- The Motion field of the Blend Tree doesn't get set when double clicking on the Motion in the Select Motion window
- Application.systemLanguage returns "Unknown" when system language is set to Norwegian Bokmål/Nynorsk
- Project fails to load scene in WebGL due to lack of memory
- [Mobile] DownloadHander.text throws an exeption when reading a not supported exception
- Particle System's Point Light flickers while Looping is on and Emission Rate over Time is set to 0 with Bursts Count set to 1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a23
Resolution Note (fix version 2019.3):
Fixed in 2019.3.5f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.19f1