Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2018.3.0a1
2018.3.3f1
2019.1.0a1
2019.2.0a7
Issue ID
1121794
Regression
Yes
SkinnedMeshRender with blend shapes gives "Thread group size must be above zero" error when GPU skinning is enabled
Reproduction steps:
1. Open the attached project named "Case_1121794"
2. Try to move the "ExampleScene" object in the Sample scene
3. Observe the console
Expected result: No error messages are thrown
Actual result: Error messages are thrown
Reproducible with: 2018.3.9f1, 2019.1.0a8, 2019.2.0a7, 2019.2.0a8
Not reproducible with: 2019.1.0a9, 2019.1.0b7, 2019.2.0a6
Could not test with: 2017.4
Notes:
Could not test with 2017.4 due to overhauled prefabs
With 2019.2.0a7 and above no more pink textures are shown, however, the error messages remain
The bug is caused by one of the 'o' objects located in the prefab(Snapshot_1121794_V1)
Comments (3)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
jeromeWork
Mar 05, 2020 09:56
March 2020 and still not ported to 2018.4?
Getting the issue too.
AndyKorth
Oct 10, 2019 21:15
I would also love to see this issue backported. We're locked into 2019.1 at the moment and we're running into it, but only when the blendshapes are enabled:
https://i.imgur.com/aSAYyM6.png
daisySa
May 12, 2019 23:35
This issue doesn't occur in 2017.4; it only began when we upgraded to 2018.4. It's a massive issue for us as disabling GPU skinning drops our frame rate from 60 fps to 35 fps in some scenes.
Does anyone know roughly how long it will take for this to be back-ported to 2018.4?