Search Issue Tracker

Active

Under Consideration for 2021.3.X

Votes

1

Found in

2021.3.19f1

2022.2.11f1

Issue ID

UUM-32116

Regression

No

MSAA is not applied on Quest 2 using Built-In Render Pipeline and Vulkan

--

-

Steps to reproduce:
1. Open the attached project "QuestMSAABug.zip"
2. Notice there is only one Quality Level and Anti Aliasing is set to 4x.
3. Build and run the project on a Quest 2 device
4. Notice no MSAA is applied, but the panel and debug log will state MSAA is set to 4x.
5. Now change the Anti Aliasing in the Quality settings to disabled.
6. Rebuild the project and run it again on a Quest 2 device
7. Notice there is no visual difference to the previous build.

Expected results: MSAA is applied on Quest 2 using Built-In Render Pipeline
Actual Results: MSAA is not applied on Quest 2 using Built-In Render Pipeline

Reproducible on: 2021.3.19f1, 2022.2.11f1.

Notes:
-The Quality MSAA/Antialiasing settings is not applied on Quest 2 using the Built-In Render Pipeline.
The API reports the set value, though the image is heavily jagged, and the underlying render target texture has a sample count of 1. Moreover, there is no visual difference when MSAA is set to Disabled.
OpenXR setting Depth Submission Mode set to 16 bit or 24 bit instead of disabled using Vulkan seemed to cause this issue

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.