When importing a mesh as skeletal mesh and using any of the MikkTSpace or option to "Import Normals and Tangents" will cause the normals to import incorrectly. If using the Compute Normals or Import Normals option and setting it to "Built in" rather than MikkTSpace the normals will calculate correctly for the skeletal mesh.
Example asset attached, simple box mesh.
Image comparison of Static Mesh vs Skeletal Mesh import of same mesh. Static Mesh on the Left and Skeletal Mesh on the right.
Tested in:
4.11 Preview 1 CL- 2810555
4.11 releases CL-2824708
4.12 - Dev-Rendering CL-2824562
1. Open UE4
2. Import any mesh asset as Skeletal Mesh (box mesh attached to this report)
3. In the import options use any fo the "Normal Import Methods" with MikkTSpace set
Regression: Yes
Results: When using the MikkTSpace Normal Generation Method or Import Normals and Tangents will result in incorrect normals
Expected: Normals should look correct based on the mesh
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
Delay nodes occasionally don't fire the "Completed" output in a nativized build
An error occurred while trying to generate project files !?
I am not able to find world outliner how to enable it?
Installer 4.10 failed with error code R-1603
I can't open my map from the editor.
UE5.0.2 How to resolve error code (Xcode install) when trying to launch UE5.0.2 after install
Head over to the existing Questions & Answers thread and let us know what's up.
0 |
Component | UE - Graphics Features |
---|---|
Affects Versions | 4.11, 4.12 |
Target Fix | 4.11 |
Created | Jan 12, 2016 |
---|---|
Resolved | Apr 11, 2016 |
Updated | May 2, 2018 |