Search Issue Tracker
Fixed in 10.0.0
Votes
0
Found in [Package]
7.4.0
Issue ID
1250378
Regression
No
[VFX] Removing texture asset while multiediting working incorrectly
Versions tested: 2019.3.13f1 + 7.x.x/release (7.4.0)
Steps to reproduce:
1) Open attached scene or have two VFX objects in the scene. VFX objects should have texture inputs with textures assigned to it.
2) Multi select both VFX objects in the Hierarchy
3) Delete texture asset (select and press "Delete" or via asset browser select to "None").
4) Observe that texture inputs and other properties disappear during multi edit.
Note: Properties like AnimationCurve and ColorGradient disappear, and properties like Vector, bool, float don't.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment