Search Issue Tracker
Won't Fix
Votes
0
Found in
6000.0.0b15
Issue ID
UUM-69812
Regression
No
"Z" value of ScriptableObject is set to a random number in the Inspector when entering the value and changing the variable type from Vector3 to Vector2 and then back to Vector3
How to reproduce:
1. Open the user-attached project “My projectdsdsddf”
2. Right-click in the Project window, Create → ScriptableObjects → SpawnManagerScriptableObject
3. Open the created ScriptableObject in the Inspector and add some Elements to the list
4. Set the “Z” value of Elements to a random numbers
5. Open the “SpawnManagerScriptableObject.cs” Script and change “Vector3” to “Vector2” at line 9
6. Save the Script, wait for recompiling, and change line 9 to “Vector3” again
7. Observe the “Z” value on the ScriptableObject
Expected result: The “Z” values are the same as they were set before changing the Script
Actual result: The “Z” values are set to random numbers
Reproducible with: 6000.0.0b15
Not reproducible with: 2022.3.23f1, 2023.2.17f1
Can’t test with: 2021.3.37f1 (Functionality is not introduced)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
Note:
-Reimporting the project seems to fix the issue, testing results might be inaccurate
-No regressed version because opening the project with the different version fixes the issue
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
- [VFX] Custom HLSL with 'int' parameter, without the 'in/out/inout' access modifier is not supported
- [Windows] Lens Flare doesn't work in the Lens Flare Showroom URP Sample Scene
- Crash on ujob_execute_job while using OverlapBoxCommand when collisions are more than maxHits
- The validity of the multiple handles can behave differently based on the load/release operations order, when multiple Addressables.LoadAssetAsync and Addressables.Release are used to load and release the same Addressable Asset
- Dynamic text is rendered in the background when it is inside the <font> tag
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.