Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0f2
Issue ID
1111198
Regression
No
Space attribute order in .NET4.x is different in the inspector window than from a script
To reproduce:
1. Open attached project "1111198.zip"
2. Select "GameObject" from the hierarchy
3. Observe in the Inspector window that there is a gap between "Testing" and "Age" variable
4. In Player Settings change Scripting Runtime Version from .NET3.5 to .NET4.x
5. Select the "GameObject" again and observe as there is no gap between "Testing" and "Age" variable but there is a gap between Script name and "Testing"
Expected result: [Space] attribute works on .NET4.x in the same way as in .NET3.5
Actual result: [Space] attribute is placed before [Header] attribute even though in the script the [Space] attribute is after [Header] attribute
Reproduced on:
2017.4.0f1 2017.4.22f1 2018.3.8f1 2019.1.0b6 2019.2.0a7
Notes:
If [Space] attribute is added before [Header] attribute, then space behaves normally.
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
- "InvalidOperationException" and additional errors throw in the Console window when using a custom Composite
- The Visual Effect Graphs Custom HLSL node does not generate errors when the HLSL code used is incorrect
- The Capacity field in the “Particle System Info“ is not updated when changing the Visual Effects Graph is not saved
- [VFXG] Setting an exposed texture to none assigns a random texture
- Rigidbody2D with interpolation position breaks when rotation is set and Time.timeScale is adjusted
Resolution Note (2019.2.X):
low priority defect and cosmetic issue. Likely won't be fixed.