Search Issue Tracker
Duplicate
Duplicate in 2019.3.X
Votes
0
Found in
5.2
2019.3.0b1
Issue ID
1180021
Regression
Yes
Unity Events that have arguments cannot be used anymore
Repro steps:
1. Add a "Slider" component to the scene.
2. Select it and check its "On Value Changed" event property.
3. See that it has no argument and no method that takes a float can be assigned to it.
This has been found in 2019.3.0b1. The problem is not present in 2019.1. 2019.2 has not been checked.
The problem seems to appear for all UnityEvents that take arguments. If it does, the argument does not appear in the inspector, any existing method on it will appear as "missing", and no new method with the right signature (e.g. expecting a float) can be assigned.
Note that this is not exclusive to uGUI. Any use of UnityEvent anywhere will exhibit the same problem.
-
Resolution Note (2020.1.X):
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1178687