Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.37f1
6000.0.10f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
7000.0.0a1
Issue ID
UUM-75485
Regression
No
[Android] Artifacts are present when using specific material and shader on devices with Exynos
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Switch to Android Platform
4. Build and run
5. Observe the Player
Expected result: No artifacts exist
Actual result: Artifacts are present on blue sphere
Reproducible with: 2022.2.0b15, 2022.3.37f1, 6000.0.10f1
Not reproducible with: 2021.3.40f1, 2022.2.0b14
Reproducible on:
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: Exynos 9 (9825), GPU: Mali-G76
Not reproducible on:
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- Reproducible with Vulkan and OpenGLES3
- Reproducible with IL2CPP and Mono
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
User defined shader is requesting depth information incorrectly.
Instead of using:
TEXTURE2D(_CameraDepthAttachment);
SAMPLER(sampler_CameraDepthAttachment);
To get camera depth data, please use "LoadSceneDepth(uint2 pixelCoords)" included in "Packages/com.unity.render-pipelines.universal/ShaderLibrary/DeclareDepthTexture.hlsl". This will fix any artifacts observed from sampling camera depth attachment.
Another alternative would be to replace "_CameraDepthAttachment" with "_CameraDepthTexture" to receive correct data. However, this is unrecommended legacy solution.
Resolution Note:
Postpone, U7 ports.