Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
4
Found in
2021.3.21f1
2022.2.12f1
2023.1.0b9
2023.2.0a7
2023.3.0a3
Issue ID
UUM-31068
Regression
No
Can't import asset via Package Manager when it consists of sub-packages and one of them is already imported
How to reproduce:
1. Open a new Unity project
2. Download and Import MicroVerse Core Collection https://assetstore.unity.com/packages/tools/terrain/microverse-core-collection-232976
3. Download and Import MicroVerse Masks https://assetstore.unity.com/packages/tools/terrain/microverse-masks-238841
Expected result: Package imports successfully
Actual result: Errors “Could not create directory for asset (asset path)“ occur and package is not imported
Reproducible with: 2021.3.20f1, 2022.2.12f1, 2023.1.0b9, 2023.2.0a7
Could not test with: 2020.3.46f1 (Package not compatible with this version)
Reproduced on: Windows 10
Notes:
- Could not reproduce the issue with other Package collections. Tested with MicroSplat packages
- Not reproducible when the MicroVerse package is imported first
Comments (1)
-
JasonBooth
Jun 01, 2023 17:50
Note this repro is missing a step - you have to install com.unity.splines 2.0 or greater..
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
This is caused by using hybrid packages (UPM in .unitypackage). This is not a supported workflow and the Package Manager teams are currently working on a solution.
Resolution Note (2023.3.X):
This is caused by using hybrid packages (UPM in .unitypackage). This is not a supported workflow and the Package Manager teams are currently working on a solution.