Search Issue Tracker
By Design
Votes
0
Found in
2018.3.6f1
Issue ID
1128980
Regression
Yes
gameObject.SendMessage doesn't accept value as a function argument correctly in the .NET 4.x Scripting Runtime
How to reproduce:
1. Open the user-submitted project ("Unity_2018_3_NET_4_6.zip")
2. Enter Play Mode
3. Observe the Console Window
Expected result: all of the messages are sent correctly
Actual result: the message with a value as a function argument isn't sent correctly and throws the "Calling function Test with no parameters but the function requires 1." error
Reproduced in: 2019.2.0a6, 2019.1.0b4, 2018.3.7f1
Not reproducible in: 2017.4.21f1
Resolution Note:
This change is actually a design decision made by the Microsoft C# compiler team long ago: https://github.com/dotnet/roslyn/issues/33486 To workaround, cast the 0.0 float value to an object when using as a parameter. It will prefer the 'object' overload then.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- EditorGUILayout.PropertyField does not work for Vector4
- Absolute paths from included packages cannot be converted to virtual paths in Assets/Packages
- Crash in VCProvider when upgrading project from 18.3 to 19.1 and 19.2
- Android Vulkan corrupted rendering when there is no camera in the scene
- Creating mesh assets produces broken blendshapes
Add comment