Search Issue Tracker
Fixed in 2022.3.52f1
Fixed in 2022.3.X, 6000.0.X, 6000.1.0a1, future release
Votes
2
Found in
2022.3.35f1
6000.0.8f1
6000.1.0a1
Issue ID
UUM-74644
Regression
Yes
[Android]Artifacts in video file on Android player
Reproduction steps:
1. Open the attached project “BugRepro”
2. Build And Run on Android
3. Observe the video
Expected result: The video plays correctly (i.e. no artifacts)
Actual result: The video displays some artifacts
Reproducible with: 2022.1.0a13, 2022.3.35f1, 6000.0.8f1
Not reproducible with: 2021.3.39f1, 2022.1.0a12
Reproducible with these devices:
VLNQA00518 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 13
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9
VLNQA00591 - Samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
VLNQA00278 - Xiaomi Redmi Note 7 (Redmi Note 7), CPU: Snapdragon 660, GPU: Adreno 512, OS: 9.0.0
VLNQA00139 - Vivo Xplay6 (vivo Xplay6), CPU: Snapdragon 820 MSM8996, GPU: Adreno 530, OS: 7.1.1
Testing environment: Windows 11 23H2 (22631.3007), Windows 11 (10.0.22631) 64bit (user’s)
Not reproducible environment: No other environment tested
Notes:
- Not reproducible in the Editor (Play Mode)
- Not reproducible on Standalone (Windows build)
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 6000.1.0a1):
verified as fixed in 6000.1.0a4