Search Issue Tracker

In Progress

Fixed in 2022.3.53f1, 6000.0.23f1

Fix In Review for 2021.3.47f1

Under Consideration for 6000.1.X

Votes

17

Found in

2021.3.37f1

2022.3.26f1

6000.0.0b16

6000.1.0a7

7000.0.0a1

Issue ID

UUM-71363

Regression

No

[Android] [Vulkan] "VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT" not added on some Android devices to "2D Colour Attachment"

--

-

How to reproduce:
1. Open the “IN_74879” project
2. Open the “SampleScene”
3. In the Build Settings make sure the Android Platform is selected
4. Enable development build
5. In the “Run Device” dropdown, select the desired device
6. Press Build And Run
7. Open the RenderDoc program (left link to download in the comments) and select the “Replay Context” button in the bottom left corner and select your Device.
8. In the Launch Application window, select the “...” icon next to the Executable Path text and find the projects player activity. It should be called “com.DefaultCompany.RenderPassAPI/com.unity3d.player.UnityPlayerActivity”
9. Press the “Launch” button to open the project on the Android device
10. After the project has run past the splash screen, in RenderDoc select “Capture Frame Immediately”
11. Open the new capture by double-clicking
12. In the Resource Inspector window (if not visible go to Window → Resource Inspector) select any 2D Colour Attachment from the Resource List and open it by double-clicking
13. In the Resource Initialisation Parameters section, expand the “vkCreateImage” parameter and then expand the “CreateInfo”
14. Search for “VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT“

Expected result: “VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT” is in the “CreateInfo”
Actual result: “VK_IMAGE_USAGE_TRANSIENT_ATTACHMENT_BIT” is missing

Reproducible with: 2021.3.37f1, 2022.3.26f1, 6000.0.0b16

Testing environment: Windows 10 Pro
Not reproducible on: No other environment tested

Reproducible with these devices:
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
OnePlus 7T Pro, GPU: Adreno 640 (user reported)

Not reproducible with these devices:
Samsung S24 Ultra, GPU: Adreno 750 (user reported)
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76

Notes:
- User mentioned this issue is reproducible on Adreno 5xx and 6xx devices

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.