Search Issue Tracker
Third Party Issue
Fixed in 2019.4.X, 2020.3.X, 2021.2.X, 2022.1.X
Votes
38
Found in
2019.4
2020.3
2021.2
2022.1
2022.1.0b2
2022.2
Issue ID
1393481
Regression
No
"Blender could not convert the .blend file to FBX file" error is thrown when .blend file is imported
"Blender could not convert the .blend file to FBX file" error is thrown when .blend file is imported and Blender 3.0.0 is the default version for opening .blend files
How to reproduce:
1. Ensure that Blender is not installed
2. Install and run Blender 2.93 (https://download.blender.org/release/Blender2.93/)
3. Save the file (File > Save As) and close Blender
4. Create a new Unity project
5. Import the saved .blend file into the project
6. Install and run Blender 3.0.0 (https://www.blender.org/download/)
7. Open the saved .blend file and ensure it was opened with Blender 3.0.0 (Blender logo in the top-left toolbar > About Blender)
8. In the Unity project's Project window, right-click the .blend file and select "Reimport"
9. Inspect the Console window (Window > General > Console)
Expected result: No errors are seen in the Console
Actual result: "Blender could not convert the .blend file to FBX file. " error is seen in the Console
Reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b4, 2022.2.0a2
Full error:
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.
-
kimsmiel743
Oct 26, 2024 07:59
Hello, as a newbie to cryptocurrency trading, I lost a lot of money trying to navigate the market on my own, then in my search for a genuine and trusted trader/broker, i came across Trader Bernie Doran who guided and helped me retrieve my lost cryptocurrencies and I made so much profit up to the tune of $60,000. I made my first investment with $2,000 and got a ROI profit of $25,000 in less than 2 week. You can contact this expert trader Mr Bernie Doran via Gmail : BERNIEDORANSIGNALS @ GMAIL . COM or telegram - IEBINARYFX and be ready to share your experience, tell him I referred you
-
Bee_Sting
Sep 06, 2023 06:36
Hello All,
I have stumbled into this issue myself on my desktop with Unity 2022.3.4 and here's what I did to fix it (as of 9/6/2023):
1.) Close your current session of Unity.
2.) Go to Blender's website and download the latest version (usually for Windows).
--NOTE: You should be downloading the regular promoted Installer; the portable installer is the zip with the blender-launcher Application file mentioned in Etienne's link, which WILL NOT get recognized as an actual Blender install by Unity should you try to do the "Open With..." using the Blender 3.6.xx blender executable from the blender-launcher file.
3.) Once you got your Blender 3.6 (or 3.0+ generally) installed, you're going to navigate to the Asset directory where your broken .blend is located in your Unity Project folder. Do this in your (Windows) File Explorer.
4.) Left-click once on the .blend file to highlight-select it.
5. Then, hover over the "Open v" small icon next to "Properties" in the upper right of the File Explorer header Tool bar.
6.) Drop down the list and select "Choose Another App".
7.) Select the appropriate Blender install (which will normally just appear as "Blender" application). Check the box "Always Use This App" at the bottom of the dialog box.
--NOTE: IT's advised you figure out in advance which is the correct 3.0+ Blender by testing the "Choose Another App" to open the model with leaving the "Always Use This App" unchecked and viewing Blender's version once the program is launched.
8.) If the modeled opened in Blender 3.0+ successfully, then you're good to go from here on out.
9.) Re-open your Unity Project (delete the Library folder for a full-reload) and then once in, go to the .blend model that's broken inside Unity and now click "Re-import".
--If correct, Unity should spit no error and your model should load.These are updated steps post when Blender now default installs to the restricted %AppData% directory that a normal internal Open With... can't access which is why we had to use the File Explorer's "Open v" then "Choose Another App". This also rendered the blender-launcher bush-fix from Etienne's thread usually ineffective since the blender-launcher location in C:/ProgramFiles no longer exists for the up-to-date Blender wizard install (again, it's in %AppData% now). Additionally, Unity will use the OS default application association with .blend files so a PATH Environment Variable fix won't do the trick. Thus, we had to manually trigger an embedded "Choose Another App" to get an "Always Use This App" checkbox to perform this OS default application reassignment for .blend files.
Frustrating I know, but hopefully this one comment will reach more people who come into contact with this issue later down the line.
-
iamarugin
Jul 07, 2023 09:45
I don't know why it is closed, but this issue is still present in Unity 2021.3.20 and when using blender 3.4.1
-
iamarugin
Jan 23, 2023 10:57
Why this is marked as resolved for 2021? IT IS NOT FIXED IN THE LATEST 2021.3.16! Project is COMPLETELY BROKEN BECAUSE OF THIS.
-
unity_Etienne
Jan 21, 2022 23:15
You can find help on this in this thread:
https://forum.unity.com/threads/blender-3-0-not-direct-importing.1207969/ -
EndWggn
Jan 20, 2022 20:49
Was hoping the newest unity release would fix this. Still broken! Please fix ASAP, many indies use Blender as their modeling software for Unity projects!
-
bobthenob
Jan 18, 2022 19:02
this is a pain for me as i have a lot of blend files in my projects that i want in other unity projects
-
mediapod_uk
Jan 17, 2022 10:03
This is a pretty desperate issue for me!
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
Resolution Note (2022.2.X):
This issue was caused by a change in the way Blender launches its executables which broke Unity .blend conversion workflow.
The fix is now included in Blender v3.0.1 and later, so please make sure Windows is using these as its default.
If changing the default executable is problematic you can find some help in this forum thread:
https://forum.unity.com/threads/blender-3-0-not-direct-importing.1207969/