Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0b1
2019.1.0f2
2019.2.0a2
Issue ID
1150131
Regression
Yes
Render Pipeline Asset cannot be loaded due to Compile errors when upgrading project in Unity 2019
How to reproduce:
1. Open the "1150131.zip" project on Unity 2019 (therefore upgrading it from 2018.3.11f1)
2. Once it loads, observe the Console errors caused by "Assets\HoloToolkit\BuildAndDeploy\Editor\BuildDeployWindow.cs"
3. Open the "SampleScene" scene
4. Open the "Graphics" tab in the Projects Settings window
-- The cube in the scene is pink; Render Pipeline Asset in Projects Settings is set to none; "LightweightRenderPipelineAsset" cannot be set as a Render Pipeline Asset
Expected result: "LightweightRenderPipelineAsset" is set as a Render Pipeline Asset (like before upgrading the project version); the cube in the scene is not pink.
Reproducible with - 2019.1.0b1, 2019.1.1f1, 2019.2.0a2, 2019.2.0a14
Not reproducible with - 2018.3.14f1, 2019.1.0a15, 2019.2.0a1, 2019.3.0a1
Workaround: Reopen Unity or delete "Library" folder from the project directory.
Notes:
- If the HoloLens Toolkit (that causes the Compile errors in step 2) is not present in the project, the issue does not occur.
- The issue is not reproducible when "Library" folder is deleted from the project directory before opening the project.
- The issue is only reproducible once when the opening project on Unity 2019 (not reproducible on reopening).
- The repro project is created using Unity 2018.3.11f1.
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
- VFX Graph Particles render black when using Baked GI in URP Unlit Shader Graph
- Crash on Unity::Joint::SetJointLocalActorFrames when changing connectedBody on a ConfigurableJoint
- WebGL player crashes on RuntimeError when using the Disk LTO code optimization
- All Animators previous animations are activated while transitioning when a second split-off transition overrides the first split-off transition
- Warning that external text editor path does not exist when manually selecting specific code editors such as VSCodium or TextEditor
Resolution Note:
If there are compiler errors in the project, the LWRP package will failed to compiled. That's how packages work in Unity unfortunately. Once the compiler errors are fixed, then LWRP should work fine. Resolving this bug as design as the compiler errors are in third party software.