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
- The Scene view flickers when moving around if there are visible Hair Shaders
- The gradient ShaderGraph is inverted when using the Perceptual blend mode
- Particle System allocates large amounts of memory when it is very far away from the origin of the Scene
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
Resolution Note:
Since animation writes back at every frame, it's expected that you won't be able to change the value.