Search Issue Tracker
By Design
Votes
0
Found in
Issue ID
1164256
Regression
No
(Asset DB v1) Deleted Metadata is re-imported based on asset (as opposed to on default behaviour) created off
(Asset Importer) Deleted Metadata is re-imported based on asset (as opposed to on default behaviour) created off
Steps to Repro:
1. open a new project using Asset Database V1 in 2019.3
2. create a primitive Sprite asset (e.g. square, triangle, polygon, etc.)
3. view the asset in Explorer and move away the metadata file
4. re-import the sprite to create a new metadata file
Result: The new metadata file is based on the asset.
Expected: The new metadata file is based off default behaviour.
Note: The expected behaviour occurs when using Asset DB V2
-
helppcexpert
Jun 20, 2019 10:18
So as to fix all mistakes and disappointments in your Gmail account you have to check your Gmail mail match up settings in your record. The professionals are much capable in their work and proffer you arrangements which suits your necessities.
+1-855-580-3482 <a href="https://passwordrecoverysupport.us/reset-gmail.php">Fix Gmail Error forgot gmail password helpline number </a>
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
- When "draw instanced" is changed for entire terrain group and then undone, it is only undone for the terrain that was selected
- Custom Inspectors OnDisable still called after Asset has been deleted
- Native Plugin regression from 2018.x results in "DllNotFoundException" error
- [Android] "AndroidETC2FallbackOverride.Quality32BitDownscaled" does not work on an Atlas created with the Legacy Sprite Packer
- Debug.Log() Context not highlighted when pressed after printing in Test Runner's EditMode
Resolution Note (fix version ):
There is no currently documented expectation on this behavior, so the change in behavior brought in by the Assets Pipeline V2 (that also influences V1) is considered the new standard, unless there is a compelling business / workflow reason to keep the old behavior (we couldn't find a strong enough reason so far).