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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Add comment