Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.46f1
2022.3.53f1
6000.0.30f1
6000.1.0a7
Issue ID
UUM-90142
Regression
No
Post Processing SMAA breaks when HDR mode R11G11B10 is selected and Color Space is changed
Reproduction steps:
1. Open the attached “Post Processing SMAA.zip” project
2. Navigate to the “Camera Settings” in the Project Settings (Edit > Project Settings > Graphics)
3. Under “Tier Settings” find the “High (Tier 3)” settings
4. In the “HDR Mode” property switch from “FP16” to “R11G11B10”
5. Navigate to Player settings in the Project Settings
6. Switch the Color Space
7. Observe the model in the Game view
Expected result: The Subpixel Morphological Anti-aliasing is applied to the model
Actual result: The Subpixel Morphological Anti-aliasing is not applied to the model
Reproducible with: 2021.3.46f1, 2022.3.53f1, 6000.0.30f1, 6000.1.0a7
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Notes:
- Might not be related exactly to switching Color Space as changing the HDR mode back to “FP16” and restarting the project, also makes the SMAA work correctly
- The SMAA setting is applied on the Camera Component in the Post-process Layer
- Appears only to reproduce if the “R11G11B10” is selected under the “High (Tier 3)” setting
- Does not appear to reproduce in the Player
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Hello there,
Thanks for the report. After reviewing this, we’ve found that this issue is pretty rare and difficult to reproduce. While we strive to address all issues, we have to prioritize fixes that impact a larger portion of users or significantly affect functionality.
We’ll continue to monitor similar reports, and if this issue becomes more prevalent, we’ll revisit it. In the meantime, please don’t hesitate to reach out if you encounter other concerns or need assistance.