Search Issue Tracker
Duplicate
Votes
3
Found in
2019.3.0a1
2019.3.0f5
2020.1
Issue ID
1216577
Regression
Yes
AssetDatabase RenameAsset renames child Scriptable Object Asset Pipeline version 2
How to reproduce:
1. Open attached project "AssetRenameBug.zip"
2. Make sure that Asset Pipeline version 2 is selected (Project Settings -> Editor -> Asset Pipeline -> Active version 2)
3. In Project window, right-click -> Create -> ScriptableObject -> DialogueInteractionGraph
4. Observe the names of the created object and its child (xNode window is opened)
5. In the xNode window, click "Rename Asset File" button
5. Observe the names of the created object and its child
Expected result: the created object name is "Dialogue Graph Renamed", child name is "Interaction Context"
Actual result: the created object name is "Dialogue Graph Renamed", child name is "New Dialogue Interaction Graph"
Reproducible with: 2019.3.0a1(ver2), 2019.3.0f6(ver2), 2020.1.0a22(ver2), 2020.1.0a25(ver2)
Not reproducible with: 2019.2.20f1(ver2)
Could not test with: 2017.4.36f1, 2018.4.17f1(Asset Pipeline version 2 was not present)
Notes:
The issue only reproduces with Asset Pipeline version 2 on 2019.3.0a1 and newer. The issue does not reproduce on Asset Pipeline version 1
-
Ratslayer
Feb 04, 2020 15:24
I can reproduce this bug on 2019.3.0f6. Can't rename custom xnode graph objects as a result.
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
- [iOS] WebCamDevice.availableResolutions returns a single resolution with width and height both 0 on some iOS devices
- Editor freezes when selecting a GameObject in Play Mode with a script containing a public byte array
- Saving moves Toggle Button Group buttons to the wrong place in hierarchy
- [iOS] Visual artifacts are visible when the camera's feed is rendered to a texture
- Error "cannot map expression to ps_4_0 instruction set" in Shader Graph preview when using the GATHER_RED_TEXTURE2D macro in custom hlsl function
This is a duplicate of issue #1189089