Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.2.0b10
2023.1.0a20
2023.3.0a1
Issue ID
UUM-20264
Regression
Yes
[Android] Visual Effects aren't rendered when building for Snapdragon 865 and Snapdragon 765 devices
How to reproduce:
1. Open the attached “In-21781_VFXGraphTest.zip“ project
2. Build and Run the “SampleScene“ Scene for Android
3. Observe the Scene
Expected result: “spark02_loop“ Visual Effects are rendered
Actual result: “spark02_loop“ Visual Effects are rendered
Reproducible with: 2022.2.0a17, 2022.2.0b10, 2023.1.0a20
Not reproducible with: 2020.3.42f1, 2021.3.12f1, 2022.2.0a16
Reproducible with these devices:
Samsung Galaxy Z Fold2 5G (SM-F916U), Android 10, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
Samsung Galaxy S20 FE 5G (SM-G781B), Android 11, CPU: Snapdragon 865 SM8250, GPU: Adreno (TM) 650
Xperia 5 Ⅱ SO-52A Android 10 (Snapdragon 865)
Galaxy Note20 Ultra 5G SC-53A Android 10 (Snapdragon 865+)
Pixel5a Android12 (Snapdragon 765G)
Not reproducible with these devices:
Samsung Galaxy Z Flip3 5G (SM-F711B), Android 12, CPU: Snapdragon 888, GPU: Adreno (TM) 660
Qualcomm (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Surface Duo2 Android 11 (Snapdragon888)
Galaxy S10+ SM-G975N Android 11 (Exynos 9 Octa 9820)
Pixel 4 Android 10 (Snapdragon 855)
LG G7 thinQ Android 8 (Snapdragon 845)
Pixel 6 Android 12 (Tensor)
Notes:
- The issue was reproducible with Vulkan, OpenGLES3, and Auto Graphics API’s
- Sometimes the issue wasn’t reproducible with 2023.1.0a20 (couldn’t find a reason)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note:
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.