Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b7
Issue ID
1093344
Regression
No
Script compile errors prevent packages from installing correctly
I was trying to get an older package from the a$ to work, that needed post processing... For that, I wanted to install the Post Processing package from Package Manager. After downloading the package, I noticed that various components of that package don't work because the script compile erros from that particular asset prevent the PostProcessing from installing itself properly, although they are 2 totally different systems.
In this case, I needed the Post processing package to properly fix this A$ asset, so I ended up with a Chicken-and-Egg kind of problem.
Repro steps:
- download this smaller package https://oc.unity3d.com/index.php/s/63CCYvuNLpmDZjC or the full .unitypackage from the comments
- open it and notice the compiler error
- open Package Manager and add PostProcessing to your project
- after the loading bar finishes, try to add a Post Processing Volume to the Camera object and notice that the component is not there.
- For this small example, it seems that you can restart the project and the PostProcessing package does end up compiling before you get the compile error again, but for the package you get from OC, this workaround doesn't work.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
In this case there are two possible fixes. Either replace the v1 installation that lives in the Assets folder by the latest v1 version (found here) or delete that same PostProcessing folder and install v2 through the package manager.
Side note: assets from the store that come bundled with official Unity packages are bound to fail at some point, either because of a version incompatibility or because the package has already been imported by another asset that bundles it too... This is risky.