Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.3p2
Issue ID
982453
Regression
No
All Blendshape values apply on the first BlendShape field when using blendshapes from .blend file
To reproduce:
1. Extract attached assets and add them to any project
2. Add human2blend and humanFBX to the scene
3. In Hierarchy window, select both of the Body objects of two humans
4. In Inspector window, change Male_age BlendShapes parameters to 100 from Male_age1 to Male_age90 (check .gif for reproduction steps)
Expected: blenshapes apply on specifically set blendshape fields on imported .blend file
Actual: blenshapes apply on top of the first blendshape field as their basis on imported .blend file
Reproduced in: 5.6.5f1, 2017.1.3f1, 2017.2.1p1, 2017.3.0p1, 2018.1.0b3
Note: functions correctly when exported as FBX
Comments (1)
-
JoelFortin
Sep 27, 2018 16:57
Unity supports the import of native external applications like .max, .ma or .blend but, under the hood, Unity opens the corresponding application and export the file to FBX so it can be consumed by Unity. Therefore, the external application must be installed on the machine otherwise, the import of a native file format will simply fail when imported in the project.
The problem here, is by importing a .blend file into a project, Unity will use a specific set of FBX settings to export the FBX from Blender. So, the result may not be the same as a regular FBX that was exported directly from Blender by the user before being imported in Unity.
Although it's not recommended to use native file formats, we still allow this workflow. The users have access to the scripts used by Unity for file conversion so they can be customized. These scripts are located in the "Unity install folder -> Editor -> Data -> Tools". In this specific case ... "Unity-BlenderToFBX.py" script is used to launch Blender.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (2019.1.X):
This is the expected behaviour, the blender-to-fbx conversion script triggers a FBX export from blender with a specific set of parameters. the 'use_mesh_modifiers' parameter prevents the export of blendshapes keys. The alternative and recommended way is to export to FBX from blender.