Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.2.0b2
2020.3
2020.3.17f1
2021.1
2021.1.0a1
2021.2
2022.1
Issue ID
1365939
Regression
Yes
Compute Buffer errors in the Player.log when building project with Vertex Compression set to Everything
Reproduction steps:
1. Open the attached project "1074438-IvalidStride.zip"
2. Open the "SampleScene" Scene
3. Set Vertex Compression to Everything in Edit > Player Settings > Other Settings > Vertex Compression
4. Build and run the project
5. Observe the Player.log file from "%USERPROFILE%\AppData\LocalLow\CompanyName\ProductName\Player.log"
Expected result: There are no errors in the Player.log file
Actual result: In the Player.log file occurs the following error: "Invalid stride 1 for Compute Buffer - must be greater than 0, less or equal to 2048 and a multiple of 4"
Reproducible with: 2020.2.0b2, 2020.3.19f1, 2021.1.0a1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a10
Not reproducible with: 2019.4.30f, 2020.2.0a21, 2020.2.0b1
Note:
- Not reproducible on MacOS
Comments (1)
-
IBingGo
Aug 08, 2023 09:27
Unity2021.2.5f1c302 find
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
- HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
- 2D Sprite Renderer in front is affected by Sprites in the background when using Sorting Layers and a Shadow Caster 2D with Self Shadow
- Modifying UI Prefab child's Height only confirms the first 1 or 2 digits when the Scene is newly opened or the Prefab is newly created
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
Resolution Note (fix version 2022.2):
Fixed in: 2022.1.0b1
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.8f1
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.26f1