Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2018.3.X, 2019.1.X, 2019.2.X
Votes
25
Found in
2018.3.13f1
2019.1.0f1
2019.2.0a11
Issue ID
1144643
Regression
Yes
Editor throws error when importing native 2.7x .blend file, imported file is not recognized
To reproduce:
1. Open user's attached project ("Blank_Project_2019")
2. Reimport all Assets
-- Error in the console, file is not recognized
Expected: File is imported, no error is shown
Actual: File is not imported, error is shown
Reproduced with: 2019.1.0f1, 2019.2.0a11
Not reproduced with: 2017.4.25f1, 2018.3.10f1, 2019.2.0a10
Note:
- Issue is reproducible even with newly created .blend file
- An error is thrown in the console:
"Blender could not convert the .blend file to FBX file.
You need to use Blender 2.45-2.49 or 2.58 and later versions for direct Blender import to work."
Fixed in:
2019.3.0a1
2019.2.0a14
Fix note:
In order for the fix to be effective, Blender 2.8 instead of 2.79 must be set as default program to open native .blend files.
Comments (7)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
soodsean88
Nov 01, 2021 18:05
Thank you for giving us your opinion. and will be used to create works
Deckiers
Aug 21, 2020 05:06
Copy your 3D model source asset file (*.obj, *.fbx, or *.gltf), and all of its dependencies (*.mtl, *.bin, *.png, *.jpg, etc.) into the sampledata folder. Do not copy these source files into your project's assets or res folder, as this will cause them to be included in your APK unnecessarily.
chrisjohn2211
Jun 23, 2020 15:55
same problem with me.
Lee-Jong-Hoon
Apr 22, 2019 14:51
me too error.
I use blender 2.79
kankeus
Apr 20, 2019 05:32
This issue can be fixed temporarily by this:
-Uninstall Blender 2.8
-Install Blender 2.79 or earlier
-Copy 'Unity-BlenderToFBX.py' from 2018.3 or earlier versions to 2019.1 editor folder. (On Mac it's Applications/Hub/Editor/2019.1.0f2/Unity.app/Contents/Tools)
AndyKorth
Apr 18, 2019 20:24
We confirm this issue with our team. We have Blender files that are working in Unity 2018.3.12f1, but fail to import with the same message in Unity 2019.1.0f2.
I have Blender 2.79 installed on this machine.
VincentPaquinUbiant
Apr 17, 2019 15:00
This issue includes incompatibility with versions of Blender inferior to 2.8 (which right now is in beta)
as well as an issue concerning a wrong rotation of the bones, which are orientated differently depending on the version of Blender, therefore breaking retro compatibility.