Blender 3.0 not direct importing

My .blend assets are broken, and I'm getting the 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."


Blender has just had a major version update. And the new version seems incompatible with Unity.

 

Tried modifying the python script to say 3.0.0 instead of 2.80.0 to no avail.

 

i'm having issues with all my .blend files saved in v 3.0

 

That work for me. Thank a lot. Now I can edit the Blender file and it correctly update in Unity. Here is the location of the python script in case others are looking for it :
Program Files\Unity\Hub\Editor\2021.1.13f1\Editor\Data\Tools\Unity-BlenderToFBX.py

 

I'm having the same issue. Modifying the python script didn't help.

 

I've also been hitting issues with .blend files not importing since installing Blender 3.0

Something else I noticed though was that imports would still fail after uninstalling all versions of Blender and just installing the 2.93LTS version even though that certainly worked before. There appears to be some caching at play with this issue (at least for me).

After I uninstalled Blender 3 and just installed 2.93LTS...

I was able to nuke my project's Library/ folder and through doing a _full_ reimport for the whole project then .blend files started to import again.

I also found that I could make changes to import settings (such as the scale) to trigger a re-import - but reverting the change would just put it back into a state where it would not import the file. Similarly I could rename .blend files and then they would correctly re-import. (presumably since that state is cached somehow).

I wish I knew what minimal Library/ state could be deleted to avoid the full reimport since I'm now hitting this problem with a much larger projects that's going to take hours to reimport :/

The simplest benign change that seems to work is to just open the .blend file, make a trivial change, then revert and re-save - anything to just change the hash for the file to bypass the cache. Obviously a naff workaround but at least for me I really don't want to do a full reimport of this project if I can help it.

It would also be good to figure out a workaround that lets me keep Blender 3.0 installed - I guess for now I'll just use nightly Blender builds that are just unpacked without being installed.

 

On Windows, it seems that your default opener for .blend files is the one that will be used for Unity importer (not the version on PATH).

 

yeah this sucks really bad i need a fix

wtf it like works in one project but not the other (?) idk whats going on

 

Modifying the python file worked for me, I'm using Blender 3.0.0 and Unity 2020.3.22f1

As stated above, the python file is found at:

C:\\Program Files\Unity\Hub\Editor\{{Your Unity version number}}\Editor\Data\Tools\Unity-BlenderToFBX.py

I changed the line at the top that says:

blender280 = (2,80,0) <= bpy.app.version

to read:

blender280 = (3,0,0) <= bpy.app.version

And that's all I needed to do, hope that helps.

 

doesnt work for me
my path is too idk
D:\Program Files\Unity Editor\2020.3.25f1\Editor\Data\Tools

 

Didn't work for me...

 

Someone should report a bug, and in the report send a small project containing some 3.0 blender files to reproduce the issue. I don't have blender 3.0 Installed or I'd do it.

 

https://issuetracker.unity3d.com/is...e-error-is-thrown-when-blend-file-is-imported

 

I voted. We just need one more.

 

Voted as well... it missing 9 more votes

 

same issue here. need a patch. voted
had to not only reinstall blender 2.93 but also had to reinstall the version i had of unity to clear whatever cache changes it made. none of the py patches people have mentioned worked.

 

Yup me too! - voted!

 

yes me too

 

Damn, for me the quick fix doesn't wanna apply as well. Still 9 votes needed... Anyhow exporting inside Blender to .fbx helps in the short term I guess... Annoying cause I started questioning my process here xD

 

Installing a 2.x version of blender then doing something like:

cd C:\Program Files\Blender Foundation\Blender 2.93
blender.exe -r

in command prompt will register it as the default program for the .blend file, but it won't work correctly for .blend files using 3.0 features like the new geometry nodes.

 

thanks that helped actually, my .blend files suddenly stopped working again but registering them with 2.93 brought them back to life in Unity. Thanks!

 

oh hey it works!!
you want to target the Blender.exe
not launcher lol xD

 

I spent an entire day troubleshooting this issue. Even uninstalling Blender and re-installing older versions didn't work after first installing Blender 3.0. @unity_Etienne 's WORKAROUND worked for me.

 

Thankyou so much.
As long as we have a workaround everything is good, thank you so much.

 

Thanks for that!

 

Maybe this is the right place to ask a for a feature, which is longer in my mind, due to some import problems.

I really like the workflow, that I can directly use blendfiles in unity. Also knowing, that's just a background fbx export job. And there is also the problem: it depends on an external app, which can change. Sometimes my unity projects are longterm (> 1,5 years) and in this time it's likely that I want to update my default blender.

But sometimes this lead to big import strugle in my projects, sometimes noticed too late and saved broken scenes.

Here's my request: every blender version is also available as portable. I'd love to set the path to the blender app, which should be used for import. With this option, it would be possible that we can open a 3 year old unity project and next to the project lies the corresponding blender version and everything works just fine.

In preferences we already have the option to choose editor and set andorid sdk/ndk... pathes, why not make an optional path to the blender exe? So default it uses the installed version, but you can set optional a different path.

This you be great. And I'm sure, not only for me.

 

You should also adress the issue, that someone somehow decieded to add

bake_anim_use_nla_strips=False
bake_anim_use_all_actions=False

to Unity-BlenderToFBX.py

This could fix in some cases an issue, but I think for most people it just removes all animations of the import and replaces it with "Scene"... I mean: after every update of unity I have you search the file and change it in the editor. Maybe this should also be exposed to the import inspector?

 

Adding my voice to this issue, although I am actually still on Blender 2.79 and Unity 2021LTS (where everything basically works?)

This is another thing that gives me such pause to update Unity and Blender.

The blend workflow is amazing, please let us import animations directly from latest versions of blender. This makes me not want to update, even though 2022 fixes some other bugs (and drops support for 2.79 >.> )

 

Best thing would be @Unity: expose these settings as import parametes that they are not written in import.py file but let the used decide, if bake_anim_use_nla_strips and bake_anim_use_all_actions are true or false...

And another very anoying bug we encounter: we have a fbx (exported from blender) with 3 animations... later we increased to 30 animations. But this is not updated in unity. We have to add every single animations afterwards in the import settings.

 

Hello!
This still seems to be an issue!
After upgrading my project to the latest LTS (coming from 2020.3.21), all of my .blend files are now useless inside Unity!
I have tried all of the solutions:
- changing python-file
- Un-installing Blender 3.3 / Re-installing 2.82 (the version that worked before the Unity upgrade)
- @unity_Etienne 's workaround
But nothing makes Unity import my .blend files as it used to do in 2020.3! All of my meshes that were referenced in the .blend file are now missing...

what is going on!?

 

Just ran into this with 2021.3.13f1 and Blender 3.2.2.

Updated to Blender 3.3.1 and still have the same issue.

Also tried in 2021.3.11f1 and 2021.3.12f1 with Blender 3.3.1 and see the same issue.

I don't know what happened but I wasn't seeing this error before.

Also, the files get successfully imported if I open the .blend file, change nothing, save it, then switch back to Unity.

 

Also, the error shows up like this in the Unity Editor:

It would be great if the error message could also say what file could not be imported.

 

I'm sorry that user again run into this issue. Two weeks ago I met some people from unity and had an intense conversation about this. And I really hope, that we get the possibility to set the path to a specific blender version (for this project approved, which can also lay next to the project) and then it doesn't matter which version of blender we have installed... this would make sense for many long term projects with software, which develops fast and where you have mostly multiple versions in use.

 

I found the issue: this only happens when parallel import is enabled.

Maybe Blender doesn't like it when multiple files are being imported at the same time?

In any case, I'll make a bug report.

Edit - here you go: IN-22654

 

This workaround does not seem to work if you install Blender from the Windows Store. The installation is then "hidden" inside the locked-down WindowsApps directory. There is no easy way to change the default application to just Blender this way. Tried with Windows 11 and Blender 3.4.1.0.

 

Yes, disabling parallel import fixes this issue.

 

Still seeing this problem with Blender 3.4.1 and Unity 2020.3.46 LTS. Very frustrating.

 

Is this a typo? 2022 is not in LTS and 2023 is not released to public yet.

 

No worries, I was just confused because you said 'if you're still having issues', which I took to imply that these non-available versions might solve my issues.

 

The same problem when trying to import blender 4 .blend to unity 2022.3.15f1 LTS:
"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."
But works ok with blender 3.5 !!

 

I confirm this issues arises again with Blender 4.0 @George-Ing @unity_Etienne