Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.0.7
Issue ID
1139715
Regression
No
Post Processing Profile has no effect when it was added from script until recompiling scripts
How to reproduce:
1. Open attached project "UnityTest.zip"
2. Click "Window" > "Weather Maker" > "Setup Post Processing"
3. Observe Game View
Expected result: Post Processing is applied
Actual result: Post Processing is not applied
Reproducible with - 2018.3.12f1
Package reproducible with - 2.0.7, 2.1.5
Notes:
1) Could not reproduce with 2017.4, 2019.1 and 2019.2 because of Editor errors
2) Could not reproduce with earlier than 2018.3.0b10 versions because of Editor errors
3) Could not reproduce with earlier than 2.0.7 package versions because of Editor errors
4) Entering Play Mode fixed the issue
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Resolution Note:
This is a bug with the script that creates the post-processing profile, not post-processing itself.
When you create settings in a profile you should not create new parameters but use the existing ones as seen in the documentation (ideally they should be read-only but the way the Unity serialization works gets in the way unfortunately).
So, instead of:
Bloom bloom = profile.AddSettings<Bloom>();
bloom.intensity = new FloatParameter { value = 3.0f, overrideState = true };
You should use:
Bloom bloom = profile.AddSettings<Bloom>();
bloom.intensity.Override(3.0f);