Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a1
2018.3.0a4
Issue ID
1059678
Regression
Yes
Dependencies are not included while exporting a scene package
Dependencies are not included while exporting a package with scene asset.
Steps to Reproduce:
1. Create a new project.
2. Add a GameObject to the scene.
3. Create a prefab of that game object.
4. Create a script and attach it to the game object in the hierarchy.
5. Save the scene.
6. Select the scene in the project window and right click to select export package.
7. Make sure you have selected include dependencies.
Actual Result: No dependencies are included while exporting scene.
Expected Result: Dependencies should be included. ( Prefab, Script should be included in this case)
Reproducible on: 2018.3.0a1, 2018.3.0a5
Working On: 2018.2.f2
Note:
- Appear Always
- Appears on both OSX and Windows
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
Add comment