Reproduction steps:
1. Open the attached “IN-75498_Android MSAA issue_2022.2.0b15_First Affected Version.zip“ project
2. In the Build Settings window, select the Android platform and press the “Switch Platform” button (skip this step if Android is already the active build platform)
3. Open the “SampleScene”
4. Select the “Quality URP Config“ asset from the “Settings” > “Project Configuration” folder in the Project window
5. In the Inspector window, set the “Quality” > “Anti Aliasing (MSAA)” property to “Disabled”
6. On the right of the Game view Control Bar, click on the “Stats” button to show the Statistics overlay
7. Enter Play mode
8. Observe the “FPS” in the Statistics overlay
9. It might take up to a minute or two until the FPS stops gradually increasing (when entering Play mode for the first time after opening the project)
10. Now set the same “Anti Aliasing (MSAA)” property to “8x”
11. Observe the “FPS” in the Statistics overlay (might need to wait a bit again for the FPS to settle)

Expected result: Framerate decreases by about 10 FPS
Actual result: Framerate drops from ~145 FPS to ~42 or even ~0.5 FPS

Reproducible with: 2022.2.0b15, 2022.2.21f1, 2022.3.31f1, 2023.3.0b10
Not reproducible with: 2021.3.39f1, 2022.2.0b14, 6000.0.0b11, 6000.0.4f1

First Affected Version (FAV): 2022.2.0b15
Fixed in: 6000.0.0b11

Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested

GPU tested: NVIDIA Geforce RTX 2080 Super with Max-Q Design

Performance @ 2560x1440 Game view resolution:
- Desktop (MSAA Disabled): ~200 FPS
- Desktop (MSAA 2x): ~190 FPS
- Desktop (MSAA 4x): ~190 FPS
- Desktop (MSAA 8x): ~190 FPS
- Android (MSAA Disabled): ~160 FPS
- Android (MSAA 2x): ~160 FPS
- Android (MSAA 4x): ~110 FPS
- Android (MSAA 8x): ~75 FPS

Performance @ 3840x2160 Game view resolution:
- Desktop (MSAA Disabled): ~170 FPS
- Desktop (MSAA 2x): ~170 FPS
- Desktop (MSAA 4x): ~160 FPS
- Desktop (MSAA 8x): ~160 FPS
- Android (MSAA Disabled): ~145 FPS
- Android (MSAA 2x): ~110 FPS
- Android (MSAA 4x): ~65 FPS
- Android (MSAA 8x): 0.5-42 FPS

Notes:
- Reproducible with (Graphics APIs): Direct3D11, Direct3D12, Vulkan
- Could not test with (Graphics APIs): OpenGLCore 4.5 (crashing), OpenGL ES 3.2 (limited to 60 FPS)
- Direct3D12 experiences the most severe performance degradation out of all the Graphics APIs tested
- Graphics APIs can be changed in the Project Settings window > “Player” > “Windows, Mac, Linux settings” > “Other Settings” > “Graphics APIs for Windows” (available only when the “Auto Graphics API for Windows” option is unchecked)
- The expected and actual results will differ based on the hardware in use (mainly on the GPU). The provided FPS figures are for relative comparison purposes only
- With high enough Game view resolutions (i.e. 4k (3840x2160) and higher), the 8x MSAA can be so taxing for the GPU that the framerate drops to 0.5-6 FPS. This doesn’t happen at his level load when the active build platform is “Windows, Mac, Linux” because MSAA does not have such a performance impact then
- The Game view resolution can be increased by going to the Aspect ratio menu on the Game view Control Bar and pressing the “+” button to add a custom resolution (i.e. 3840x2160)
- Load on the GPU can also be increased by increasing the “Render Scale” property right under the “Anti Aliasing (MSAA)” property in the Inspector when the “Quality URP Config“ asset is selected
- Load on the GPU can also be increased by enabling HDR in the Project Settings window > “Player” > “Android settings” > “Other Settings” > “Allow HDR Display Output*” > “Use HDR Display Output*” and then in the “Quality URP Config“ asset right above the “Anti Aliasing (MSAA)” property in the Inspector
- See internal comments for Profiler screenshots of CPU and GPU usage during certain frames (Profiler was not running during actual performance testing)