question regarding issue #1189089

Hello there !

How glad was I to see this https://issuetracker.unity3d.com/is...hen-parent-scriptable-object-asset-is-renamed mentionned in the changelog of the most recent 2019.3 (here https://unity3d.com/unity/whats-new/2019.3.10).

But then the issue page says "postponed" and resolution notes say "fix version 2020.1".

What does it mean ? Is it backported to 2019.3 but ticket wasn't updated or is it only fixed in 2020.1 ?

Trying to understand semantics here

Thanks for reading

 

My interpretation would be that this will not be backported to 2019.3.

As they say in their comment, it a rewrite of the name handling (which is considered being a new feature). And such a rewrite is most likely not backported.

 

The resolution note on the public issue says: "Requires a system rewrite of how we handle main object name. This is considered a feature"
https://issuetracker.unity3d.com/is...hen-parent-scriptable-object-asset-is-renamed

AssetDatabase v2 is available in Unity 2019.4 too. This bug is quite a dealbreaker to work with ScriptableObject assets for me and I would like to know whether it gets fixed in 2019.4.

The public issue reads like it's fixed for Unity 2021.1 only.

I'm working with nested ScriptableObject assets a lot. If the fix won't land in 2019.4 and future 2020.4, it makes not much sense to use AssetDatabase v2 for the next 2-3 years (for me).

Which would be a bummer, because AssetDatabase v2 was advertised as the better/faster replacement and I would like to enjoy fast asset refreshes when I switch between applications.

 

That's good news indeed, thank you for the update!

 

Awesome news indeed ! thanks a lot (b14 is a godsend, feels like works better than anything before haha )