Search Issue Tracker
Fixed in 7.0.0
Votes
6
Found in [Package]
6.8.1
Issue ID
1167156
Regression
Yes
LWRP installation in 2019.3.0a8 yields errors
"Library\PackageCache\com.unity.render-pipelines.lightweight@6.8.1\Runtime\LightweightRenderPipeline.cs(133,46): error CS0122: 'VFXManager' is inaccessible due to its protection level " ---> compilation error appears after installing LWRP package 6.7.1 or 6.8.1
This makes the package unusable.
To reproduce:
- make a new project in 2019.3.0a8
- intall the latest LWRP packag available
- Notice the error
Unable to reproduce in 2019.2.0b8, 2019.3.0a7
Reproducible in 2019.3.0a8
There is a workaround:
- The user needs to remove "Experimental" from the call: UnityEngine.Experimental.VFX.VFXManager.ProcessCamera(camera) in the script LightweightRenderPipeline.cs at line 133
- Save the script and back in Unity, this will trigger the package to compile and work as normal
Comments (2)
-
brighter_leopold
Jul 12, 2019 04:11
Having the same issue. I comment it then LWRP can use...
-
magg
Jul 06, 2019 01:17
Having the same issue. The workaround worked, but the problem reappeared after restart.
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Group Selection title text size is smaller in renaming than the actual font size
- Rich Text is not correctly highlighted when searching through Debug Logs in the Console window
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
Resolution Note (fix version 7.0.0):
Issue addressed in the 7.x series of packages.
Upgrading the VFX Graph and corresponding LWRP/Universal RP to the latest 7.x pacakge versions should resolve the issue.
Note: it's a good idea to also run on the latest 19.3