Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a7
Issue ID
1168181
Regression
No
New warning from one particular .FBX when using Asset Pipeline v2
Candle_Set.FBX file (you can find it in attached project) started to introduce warning in 2019.3 (uses Asset Pipeline v2).
There is no warning in 2019.3.0a3.
But there is warning in 2019.3.0a7 and a9.
So it could be a regression or improvement.
How we can reproduce it using the example you attached
1 Simply open attached project in 2019.3.0a7 or later build
(To reproduce this warning in already opened project - select Candle_Set.FBX file in Project view, click Right Mouse Button and select Reimport )
Actual results: 2 same warnings appear in Console:
"Identifier uniqueness violation: 'Name:Candle, Type:Mesh'. Multiple Objects with the same name/type are generated by this Importer. There is no guarantee that subsequent imports of this asset will properly re-link to these targets."
Expected results: not sure if this is a regression or improvement
----
Note: The warning was recently pulled down to the base importer (used to be only in the scripted importer) so it may start appearing in more asset types.
However it's not a regression, it's just the pipeline giving more info to the user in a situation that was just silently happening before already.
Comments (3)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
milekfarion
Jun 16, 2020 15:27
The problem is in the 2019.4.0f1
mgear
Mar 19, 2020 16:02
still happening in 2020.1.0b2
Lynxed
Jan 13, 2020 15:31
This has to be optional. When i have an fbx with a thousand objects, that are named the same (for parsing reasons), i don't want to wait for Unity to show me all those warnings.