Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
1
Found in
2018.4
2019.4.3f1
2020.2
Issue ID
1269149
Regression
No
The Build does not fallback to CPU skinning when DirectX has feature level 10.1 or lower
Reproduction steps:
1. Open the attached "case_1269149" project
2. Build and run the project with "-force-feature-level-10-1"
Expected result: the Build switches to CPU skinning and the mesh is rendered
Actual result: the Build stays on GPU skinning and the mesh is not rendered
Reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.2f1, 2020.2.0a20
Note: an error message "Platform does not support compute shaders" is thrown when trying to call SetBlendShapeWeight method
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
- MSB3277 conflicts between different versions of "System.Numerics.Vectors" when using DotNet 11.0
- "Cannot create Settings Providers for: CreateAllChildSettingsProviders" error is thrown in the Console after fixing PolySpatial visionOS package validation error after installing XR Interaction Toolkit VisionOS Sample
- "Unable to find style 'VideoClipImporterLabel' in skin 'GameSkin' " warning thrown when converting the Video Clip Inspector to a floating window in Play mode
- Unclear "Failed to start primary listening socket" error when launching the Multiplayer Play Mode second player and many Unity instances are running
- The cogwheel button in the Build History window gets distorted when the Build History window is resized or options are ticked in the toolbar
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0b2
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.7f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.12f1
Resolution Note (fix version 2018.4):
Fixed in: 2018.4.28f1