Search Issue Tracker
Duplicate
Votes
2
Found in
4.2.0f4
Issue ID
561931
Regression
No
A monobehaviour can't be in a namespace and have optional parameters in its method signature at the same time
To reproduce:
1. Open the project
2. Add TestComponent to a game object. It will fail.
3. Remove the default parameter to TestFunction ("=false") or remove the namespace to add the script.
Identified as duplicate of 496529.
-
ilya_ca
Sep 29, 2014 02:32
The issue is still present on Mac OS X in Unity 4.5.
-
randomtiger
Mar 21, 2014 19:57
I'll never get those two hours of my life back
-
codestage
Dec 06, 2013 07:44
Looks like 4.3.1 has regression for this.
Just attach this MonoBehavior script:
using UnityEngine;namespace Assets.UnityBug
{
public class Bug: MonoBehaviour
{private void someMethod(int param = 10)
{
Debug.Log(param);
}
}
}and you'll see this error after starting simulation:
The class defined in script file named 'Bug' does not match the file name!Change private void someMethod(int param = 10) to private void someMethod(int param) and it will run fine!
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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
This is a duplicate of issue #496529