Search Issue Tracker
Fixed
Fixed in 6000.4.0b9, 6000.5.0a7
Votes
5
Found in
6000.0.54f1
6000.2.0b12
6000.3.0a3
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113364
Regression
No
Foveated Rendering is disabled when Anti Aliasing (MSAA) is enabled while using Vulkan
Reproduction steps:
1. Open the attached project “ReproProject“
2. Make sure the headset is connected (in case of Meta Quest, connect to the PC using wired Link or Air Link)
3. Find the render pipeline asset (Assets/Settings/PC_RP.asset), set “Anti Aliasing (MSAA)” to 2x, 4x, or 8x
4. Put on the headset and enter into Play Mode
5. Observe the result
Expected result: Foveation feature is working, the background will print out the shading rate, and you should see circular regions of 1x1, 2x2, and 4x4 shading rates
Actual result: The foveation is disabled, and the warning “Foveated Rendering disabled. Exceeded max sample count: 2 MSAA samples * 16 shading rate samples > 16 samples.” is being logged continuously in the Console Window
Reproducible in: 6000.0.54f1, 6000.1.14f1, 6000.2.0b12, 6000.3.0a3
Reproducible on: Windows 11
Not reproducible in: No other environments tested
Reproducible on devices:
- Oculus Quest 3 (Quest 3), CPU: Snapdragon XR2 Gen 2 (SM8550), GPU: Adreno (TM) 740
- Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650
Notes:
- Couldn’t find regression point because of long testing time, and inconsistency in reproduction (more info in the internal notes)
- Only reproducible with Vulkan
Comments (1)
-
mashixuan8
Aug 11, 2025 09:39
Need this solved ASAP
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
- Texture generator reference image fails despite valid size
- Agent mode can enter infinite execution loop
- AI Gateway responses contain duplicated sentences
- Texture 2D asset is created when promoting a generated Cubemap to a new asset
- Unable to copy multiple paragraphs from Assistant responses
Resolution Note (fix version 6000.5.0a7):
Fixed in 6000.5.0a7
Resolution Note (fix version 6000.4.0b9):
Fixed in 6000.4.0b9