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
- Texture displays visual artifacts and has a broken aspect ratio when it is imported in RGB 48-bit format
- Diagnostic Warning Resets When Navigating Away and Returning to Diagnostics Settings
- Checkbox Collides with Text in Shader Graph Preferences Settings
- Crash on mecanim::animation::TransformValuesFromClip when entering the Play Mode in a project with Animancer Pro v8
- Connection to Named Pipes fails when server and client are run
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