Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.4.0b5
Issue ID
767857
Regression
Yes
[Skinning] Skinning broken on Mac since 5.4 (OpenGL issue?)
Character skinning is broken on MacOS
1. What happened
Most, if not all, characters with skinning (joints binded to mesh vertex) are broken (mesh flickers, rotates, vertexes fly away for a few seconds, etc.) on MacOS with default Unity settings.
see attached gif
Workaround:
Enabling... Project Settings > Player > GPU Skinning option fixes these issues.
2. How we can reproduce it using the example you attached
This can be reproduced with about any skinned character scene, or attached example (fbx is a bit long to load).
-Open project
-Open SkinIssue scene
-Select Main Camera and move it in the scene view
bug: skinned mesh does wierd things in the Scene and Game windows
This is a regression from 5.3.2p2 (does not repro in this version)
This looks like a MacOS only issue.
repro since at least 5.4.0b1 (c64972211218)
also repro in 5.4.0b5 (9e4e230b6d3e)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
kishandas24
Dec 06, 2021 11:12
i m also facing same problem but apple store ask a huge money so what can i do.
http://issuetracker.unity3d.com/issues/character-skinning-is-broken-on-macos
garix1234
Jul 10, 2019 09:32
Now just hurry up and join this website http://gethelpwindows10.com then search your any issue if you want solution in window 10.
Lord Emperor
Mar 09, 2016 16:50
Marked as fixed in the 5.3.3p2 patch notes, but issue still exists. Switching to Graphics API to OpenGL2 is a temporary solution.