Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X
Votes
0
Found in
2021.3.39f1
2022.3.30f1
6000.0.3f1
Issue ID
UUM-72886
Regression
No
[Android][Vulkan] SSAO is rendered in the incorrect position when using the pre-rotation
Steps to reproduce:
1. Open the “PreRotationIssue” project
2. Build And Run the project on the device
3. Observe the device’s screen
4. Rotate the device if orientation is not in landscape
Expected result: The SSAO is rendered around the “Cube” GameObjects
Actual result: The SSAO is rendered far from the “Cube” GameObjects
Reproducible with: 2021.3.39f1, 2022.3.30f1, 6000.0.3f1
Testing environment: macOS Sonoma 14.4.1 (Intel), Windows 11 (by user)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00472 - samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
Workaround: Enable “Opaque Texture” in Universal Render Pipeline Asset (Mobile_RP Asset)
Notes:
- Isn’t reproducible when “Apply display rotation during rendering” is disabled
- Doesn’t reproduce in Play Mode
- Couldn’t test with OpenGLES or Metal (iOS) as pre-rotation available only for Vulkan
- Doesn’t reproduce when the device’s orientation is in portrait
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Soft keyboard is missing the "OK" button on Android
- The Profiler ignores a modified targetFrameRate when profiling Edit mode
- [General] Package manager takes 15 minutes to load
- Asset's Inspector information is no longer displayed when docking the Search Window
- Crash on Object::GetCachedScriptingObject when entering Play Mode
Add comment