Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.4.X, 2019.2.X
Votes
1
Found in
2018.2.2f1
2018.3.0a1
2018.3.8f1
2019.1.0a1
2019.2.0a1
Issue ID
1138161
Regression
Yes
.NET 4.x Runtime Script Component can not be loaded when it has more than 2 Partial Classes with the Nested Class inside
How to reproduce:
1. Open the "SampleScene" Scene in the attached "PartialedNestedClasses.zip"
2. Open the "PartialNestedClasses.cs"
3. Delete Comment slashes on line 9
4. Click on the "PartialedNestedClasses" GameObject in the Hierarchy
5. Observe the Inspector
Expected Behavior: The "PartialedNestedClasses" Component is loaded successfully
Actual Behavior: The "PartialedNestedClasses" Component is not loaded, and no Compilation errors are present
Reproducible with:2018.2.2f1, 2018.3.10f1, 2019.1.0b8, 2019.2.0a9
Not reproducible with: 2018.2.1f1, 2017.4.24f1
Note: If you set Focus on the GameObject, then go to VS or any other program, then come back to the editor - the Component disappears and you have to reselect the GameObject for it to appear. If you use .NET3.5 the issue is not present.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2019.1):
Fixed in 2019.3.0a1 Backported to 2019.2.0b1, 2019.1.3f1, 2018.4.3f1