Search Issue Tracker

Won't Fix

Votes

0

Found in

2020.3.42f1

2021.3.15f1

2022.2.1f1

2023.1.0a21

Issue ID

UUM-21710

Regression

No

[Android] Failed to create a custom MSAA Render Texture when building on ARM devices

-

Reproduction steps:
1. Open the attached project "MSAABlackScreenTest_Android"
2. Build and run on an ARM device
3. Observe the Android LogCat window

Expected result: No errors in the LogCat
Actual result: Error “RenderTexture.Create with bindMS failed: antiAliasing 2 with unsupported format - RGBA16 SFloat.” appears

Reproducible with: 2020.3.42f1, 2021.3.15f1, 2022.2.1f1, 2023.1.0a21

Reproducible with devices:
VLNQA00332, Samsung Galaxy XCover4 (SM-G390F), Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00325, Samsung Galaxy Note10 (SM-N970F), Android 12, CPU: NOT FOUND, GPU: Mali-G76
VLNQA00231, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830

Does not reproducible with devices:
VLNQA00318, Oneplus OnePlus 7 Pro (GM1913), Android 11, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76

Reproduced on: Windows 10 Enterprise 21H2

  1. Resolution Note:

    Mali GPUs don't support MSAAx2. Use https://docs.unity3d.com/ScriptReference/SystemInfo.GetRenderTextureSupportedMSAASampleCount.html to detect if the expected samples count is supported.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.