Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2019.1.0b9
Issue ID
1141239
Regression
No
[Vulkan] Inefficient memory barriers (vkCmdCopyBufferToImage)
Steps to reproduce:
1. Open attached project
2. Open SampleScene
3. Build & Run to an Android device
4. Take a RenderDoc capture
5. Observe that behavior occurs in this sequence:
- Barrier VERTEX | FRAGMENT | COMPUTE -> TRANSFER
- vkCmdCopyBufferToImage
- Barrier TRANSFER -> VERTEX | FRAGMENT | COMPUTE
Expected result: the barriers should not force fragment shading to be complete before any vertex shading
Reproduced in: 2019.1.0b9
Fixed in: 2019.3.0a1
Devices under test:
VLNQA00218, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00010, Samsung Galaxy S8 (SM-G950U), Android 7.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00261, Samsung Galaxy S10+ (SM-G975U), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Add comment