Search Issue Tracker
Fixed
Fixed in 6000.0.25f1, 6000.1.0a2, 7000.0.0a11
Votes
0
Found in
6000.0.22f1
Issue ID
UUM-83598
Regression
Yes
The Random Value option in the Set Attribute Block gets disabled and the "B"/"Max" value lost when upgrading to Unity 6
How to reproduce:
1. Unzip the “VfxAttribTest-2022“ project
2. Open it in the 2022.3 LTS
3. Observe the value of the Random (Uniform) Set Attribute in the “Test.vfx“ asset
4. Close the project and open it with Unity 6
5. Observe the Set Attribute of the “Test.vfx“ asset
Expected result: The Random setting stays set to Uniform and the “Max”/”B” properties value is transferred without changes
Actual result: After the migration the Set Attributes Random Setting gest set to Off and the “Max”/”B” properties value gets set to 0 losing its previous value of 1
Reproducible with: 2023.3.0a14, 6000.0.22f1
Not reproducible with: 2021.3.44f1, 2022.3.49f1, 2023.3.0a11
Could not test: 2023.3.0a12, 2023.3.0a13 (“Test.vfx“ got corrupted after the upgrade)
Reproducible on: macOS 14.6.1 (Intel)
Not reproducible on: Windows 10 Pro (22H2)
Note:
- Migration between 2021.3 and 2022.3 does not cause any issues
- Migrating from 2021.3 to Unity 6 reproduces the issue too
- Could not find the exact FAV, more information in the comments
- After the migration, you might get the error “Exception while sanitizing model: Set 'CustomAttribute' Random (Uniform) (Float) of type UnityEditor.VFX.Block.SetCustomAttribute: System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.“ (Full error in the comments)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment