Search Issue Tracker
Fixed in 4.2.0
Votes
1
Found in [Package]
3.0.0
Issue ID
1068455
Regression
Yes
[LWRP] MSAA does not work when Allow HDR is disabled
Steps to reproduce:
1. Open user-submitted project
2. Load Scene SampleScene
3. Pick object Switcher and click CycleCamera to see various rendering outputs:
3.1. LdrMsaa (active initially) has HDR disabled and MSAA enabled. No MSAA is seen
3.2. HdrMsaa has HDR enabled and MSAA enabled. MSAA is seen
3.3. LdrMdaaPp has HDR disabled, MSAA enabled and PostProcessingStackV2 attached (no volumes, effects or post-AA). MSAA works without HDR enabled in this case
Expected result: MSAA works regardless of HDR
Actual result: MSAA only works when HDR is enabled
Reproduced with: 2018.2.2f1, 2018.3.0a8
Not tested with pre-2018.2 due to backwards incompatibility
Additional user note: MSAA can be forced by changing the pipeline settings Render Scale. Cycle to the original LdrMsaa camera and observe that MSAA is not seen. Change the Render Scale in the LightweightAsset settings to something like 1.2 and notice that MSAA appears to work then
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 4.2.0):
Camera now resolves MSAA correctly when used with or without HDR and post