Search Issue Tracker
By Design
Votes
0
Found in
2020.3.48f1
2021.3.26f1
Issue ID
UUM-36913
Regression
No
The property of a component becomes read-only when it is bound to "PropertyStreamHandle"
Reproduction steps:
1. Open project “Repro.zip”
2. Open “SampleScene”
3. Enter Play Mode
4. Select the “Player” GameObject in the Hierarchy
5. Try to change the value of the "Value" property in the "Property Handle Test (Script)" component
Expected result: The value of the "Value" property can be changed.
Actual result: The value of the "Value" property cannot be changed.
Reproducible with: 2020.3.48f1, 2021.3.26f1, 2022.2.16f1
Not reproducible with: 2022.3.0f1, 2023.1.0b19, 2023.2.0a17
Fixed in: 2022.2.17f1
Reproducible on: macOS Ventura 13.2.1 (Intel), Windows 10 (by the reporter)
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
- Main Camera rendering is being overwritten by a UI Camera when using multiple cameras with URP and the second camera's background type is set to "Uninitialized"
- VisualTreeAsset has significantly increased memory allocation size at runtime when the project is built with IL2CPP scripting backend
- NullReferenceException is logged when cancelling Shader Graph recovery of an already deleted Shader Graph
- White Edges appear during Camera movement in runtime when using FSR2 with Motion Vectors and Exposure enabled
- Lens Flare renders without occlusion when the light source is obstructed by solid objects when running on Android using OpenGL
Resolution Note:
Since animation writes back at every frame, it's expected that you won't be able to change the value.