Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1311569
Regression
No
[Vulkan] [Metal] [Mobile] Dynamic Resolution is no longer downscaled after assigning Camera targetTexture
How to reproduce:
1. Open the attached "DynamicResTest.zip" Project (Or download the upgraded project from google drive, link in the edits)
2. Make sure Vulkan graphics API is selected
3. Build and run to the Android device
Expected Behavior: The resolution does not change before or after nulling
Actual Behavior: "Before nulling" the resolution is downscaled and "After nulling" the resolution is no longer downscaled
Reproducible with: 2019.4.21f1, 2020.2.6f1, 2021.1.0b8, 2021.2.0a6
Reproducible devices:
VLNQA00335, Samsung Galaxy S20+ 5G (SM-G986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
VLNQA00286, Meizu - (PRO 5), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
iPhone 12 (iOS 14.1)
Note:
- Did not reproduce on win standalone, However, the customer said that he could reproduce this on macOS
- This seems to be Vulkan and Metal specific
- If the issue is not reproducible - try another project (link in the edit)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2021.2.X):
Workaround: Use several cameras.