Search Issue Tracker
Fixed
Fixed in 2020.3.X, 2020.3.43f1
Votes
0
Found in
2020.3.34f1
Issue ID
UUM-1939
Regression
No
[Backport] [Metal] Unity returns that it only supports 8 compute buffers with metal graphics API when it actually supports 32
Steps to reproduce:
1. Open the attached project "Case_1299759"
2. Enter Play mode
3. Press on the white Cube
Expected results: Unity will return the number that is actually available on the device (On Mac it should be 32)
Actual results: Unity returns lower or higher values than actually available on the device (On Mac it shows just 8)
Reproducible with: 2019.4.17f1, 2020.2.1f1, 2021.1.0b1,
Unable to test with: 2018.4 due to project breaking from downgrading
Note:
- macOS and IOS with Metal seem to constantly reproduce this issue.
- Pressing on the Cube will enable 10 compute buffers and then display the cube if according to the console or the red text in the project the supported buffer count is lower then 10 but the Cube is still displayed which means that the device actually supports 10 or more compute buffers and Unity is just displaying them wrong(This happens with IOS and macOS)
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.43f1