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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note (2021.2.X):
Workaround: Use several cameras.