Search Issue Tracker
Fixed
Fixed in 6000.5.0b1, 6000.6.0a1
Votes
0
Found in
6000.0.58f2
6000.3.9f1
6000.5.0a6
6000.6.0a1
Issue ID
UUM-132893
Regression
No
Warnings about conflicting assemblies are shown when the custom packages have Microsoft AI DLLs
Reproduction steps:
1. Supply the Editor with additional Microsoft AI DLLs
2. Observe the warnings
Actual result: “DLL is conflicting with an assembly shipped with Unity and will be ignored” warning messages are shown
Expected result: These warnings should not be shown if the packages are configured correctly
Reproducible with: 6000.5.0a4
Reproducible on: Windows 11 (by reporter)
Not reproducible on: No other environments tested
Note: Not reproduced by CQA
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Fixed in 6000.5.0b1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.6.0a1
Resolution Note (fix version 6000.6.0a1):
Fixed in 6000.5.0b1