Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.13f1
2023.1.20f1
Issue ID
UUM-56684
Regression
Yes
Parameter value does not update correctly if changed by dragging in a Script Component when editing in Prefab Mode
1. Open the attached "ReproProj.zip" project
2. In the Project window, double-click on the "Assets/Prefabs/Cube" Prefab to open the Prefab Mode
3. In the Hierarchy window, select "Cube" GameObject
4. Set “Auto Save” to true
5. In the Inspector window, change the "Int_" Parameter of the "Test Script" Component value by dragging
6. Click on the "Assets/Prefabs/Cube" Prefab inside of the Project window to open its Inspector window
7. Observe the difference in "Int_" Parameter values
Expected results: The "Int_" Parameter value is the same as the previously set value
Actual results: The "Int_" Parameter value is different from the previously set value
Reproducible in: 2022.2.0a9, 2022.3.13f1, 2023.1.20f1, 2023.2.0b11
Not reproducible in: 2021.3.32f1, 2022.2.0a8, 2023.2.0b17, 2023.3.0a14
Fixed in: 2023.2.0b12
Note: I noticed that the repro in the FAV (2022.2.0a9) is far more inconsistent and it took me a couple of tries to reproduce on these lower versions as opposed to something like 2022.3.13f1 where it happened every try
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:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.