Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0b5
2020.1
Issue ID
1188386
Regression
No
Only the property that was declared second can be edited in the Inspector when one property references the other
How to reproduce:
1. Open the attached project "1188386.zip"
2. Enter Play mode
3. Select the Test GameObject
4. Edit the Array that appears first in the Testing component in the Inspector
Expected result: Values change for both Arrays
Actual result: Values do not change
Reproducible with: 2017.4.33f1, 2018.4.12f1, 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Notes:
Editing the second Array will work as expected.
Switching the order in which the Arrays are declared in the script will also switch which one is editable.
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (2020.1.X):
Low priority defect and unlikely to be fixed for the near future