Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0f3
Issue ID
960431
Regression
No
Scripted shader dependencies are not included when importing Package exported from another Project
How to reproduce:
1. Open attached Unity project "tropical versuch3"
2. Open Assets folder in the Project window
3. Export "mytree2" Prefab with "Include dependencies" enabled
4. Create new Unity project
5. Import exported package
6. Drag Prefab to the Scene
Expected Result: Imported package includes all dependencies of the Prefab when "Include dependencies" is enabled on exporting.
Actual Result: Shaders are not included when imported to the new Project when "Include dependencies" is enabled on exporting.
Reproducible with: 2018.1.0a1, 2017.3.0b5, 2017.2.0f3, 2017.1.2.p2, 5.6.4p1.
-
Giezu
Dec 21, 2017 11:11
Same on 2017.2.0f3, scenes exported with depedencies to package doesn't include hlsl shaders #include'd in .shader files.
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.
Unity QA Team