Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
Issue ID
1191780
Regression
No
ScriptReference/SystemInfo-minConstantBufferOffsetAlignment.html :
The SystemInfo.minConstantBufferOffsetAlignment property is declared to have a bool value while in fact it needs to have an int value. The issue is clearly visible in the documentation below, where the behavior is documented correctly, but the API is not.
--------------
The documentation asserts that the return type would be an integer but the API return type is a bool.
URL: https://docs.unity3d.com/ScriptReference/SystemInfo-minConstantBufferOffsetAlignment.html
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
The SystemInfo.minConstantBufferOffsetAlignment API was tagged as Obsolete and retained with the wrong return value to keep it from breakage in older projects.
It was replaced with SystemInfo.constantBufferOffsetAlignment which will return the correct int value for the constant buffer offset alignment.