Search Issue Tracker
By Design
By Design in 2023.3.X
Votes
0
Found in
2022.3.10f1
2023.1.14f1
2023.2.0b10
2023.3.0a6
Issue ID
UUM-49329
Regression
No
Warnings that TAA is enabled but will be disabled because MSAA is enabled at the same time are spammed in Console when entering Play Mode
How to reproduce:
1. Open any project with an RP installed
2. In a Scene select your Camera GO and in the Inspector enable AA under "Rendering"
3. Open your Render Pipeline Asset and in the inspector enable AA under "Quality"
4. Enter Play Mode and observe the Console
Actual result: Warnings like "Disabling TAA because MSAA is on. UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)" are spammed in the Console
Expected result: The Warning only logs once in the Console
Reproducible with: 2022.3.10f1, 2023.1.14f1, 2023.2.0b10, 2023.3.0a6
Not reproducible with: 2021.3.29f1 (No TAA in Camera)
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
- Too little validation messages in the "WebAssembly Language Features" Memory settings
- Project Settings Search Highlights are misaligned when using the Bitmap Text Rendering Mode
- "GetControlID at event ValidateCommand returns a controlID different from the one in Layout event" Warning is thrown when undoing the deletion of Sprite Shape Profile
- Memory related fields in the "WebAssembly Language Features" can be set to the negative numbers
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
Resolution Note:
The console has an option to Collapse logs to only show the first instance.
There's a way to log a warning only once, however that will also come with a cost. The proper fix here is to address the behavior that the warning warns about, in this case either disable MSAA or TAA.
Resolution Note (2023.3.X):
The console has an option to Collapse logs to only show the first instance.
There's a way to log a warning only once, however that will also come with a cost. The proper fix here is to address the behavior that the warning warns about, in this case either disable MSAA or TAA.