Search Issue Tracker
Won't Fix
Won't Fix in 6000.2.X
Votes
1
Found in
2022.3.43f1
6000.0.16f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-78807
Regression
No
Read/Write error is thrown when making an AsyncGPUReadback request to a Native Array
How to reproduce:
1. Open the attached project "AsyncGPUReadbackBug.zip"
2. Enter Play Mode
3. Press Spacebar
Expected results: No errors are thrown
Actual results: "AsyncGPUReadback - NativeArray does not have read/write access" is thrown
Reproducible with: 2022.3.44f1, 6000.0.17f1
Could not test with: 2021.3.43f1 (compilation errors in the Console window)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.2.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.