Search Issue Tracker
Fixed in 0.33.0-preview.1
Votes
0
Found in [Package]
0.31.0-preview.3
Issue ID
1302063
Regression
No
[2D Entities] Using Assets located packages return wrong Asset path
How to reproduce:
1. Unzip the attached user's project ("wiros-2d.zip")
2. Delete Packages/2D Entities folder because it contains the potential fix already
3. Delete the Library folder
4. Open the project
5. Load "SampleScene"
6. Select "WorldTest" subscene
7. Notice the error in the inspector
Expected results: When an Asset is in a Package, the CommonAuthoringUtils.GetFullAssetPath method deals with assets outside the Asset folder
Actual results: When an Asset is in a Package, the CommonAuthoringUtils.GetFullAssetPath method will return the wrong path as it assumes it is in the Assets folder.
Reproducible with: 2D Entities 0.29.0-preview.3 - 0.31.0-preview.3 ( 2020.2.3f1, 2021.1.0b3, 2021.2.0a3)
Could not test with: 2018.4.31f1, 2019.4.18f1 (Errors downgrading)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Create and publish WebGL builds” link leads to “Sorry about that, we can't find the page you're looking for.” page
- " Suspected crash in FXC. " shader compiler errors are thrown in a new project when creating a project in Hub with a very long name but below the maximum character threshold
- Long cloud names stretch the space in Hub when the Project dropdown is opened
- OpenGLES3 Graphics API can be used with the "Linear" Color space on unsupported GPUs resulting the error spam
- [Windows] Recommended and Downloaded Learn tabs are empty and have scrollbar
Add comment