Search Issue Tracker
In Progress
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
4
Found in
6000.0.54f1
6000.2.0b12
6000.3.0a3
6000.4.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)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
mashixuan8
Aug 11, 2025 09:39
Need this solved ASAP