- Home /
Problem about exporting blend files in 4.3
Hello everyone.I have been using unity for couple of months and I could easily drag and release blend files to the unity. Now there is a problem as many people know : 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. My Unity version is 4.3 and Blender version is 2.69 which both are last versions. I read almost every post about exporting blend files but nothing could help me. I uninstall 4.3 and return 4.2 but the problem is same. I also change blender versions but always for some files it gives this error. It seems that only solution exporting manually in blender and then dragging it. But when i do this it comes with camera inside and other stuffs and also it divide my model into parts. So its give problems about component such as collider etc...(briefly its not the same file as draging to the unity like old way) Also when i export manually the .fbx files has bigger memory than normal.
Long story short i am looking for real solution. How can i export my blend files easily like i used to do. 2 weeks ago there were no problem and now it is. I will be thankfull if anyone can help me about this annoying situation.
And could you change the title of the question to add "Blender 2.69", because it seems as though it is a problem associated with this version specifically. It will be easier to find for anyone else...
As i remember its doing this also 2.68 . I found a solution just on 2.67
I had the problem on 2.68, and updated to 2.69 and works fine.
It's like every person has a different experience. GraviterX, just try and save the model in edit mode and try and import and tell me if it works out...
I agree with Hatredalper. I downgrade to 2.67 and it's work.
Answer by David Kamunyu · Jan 21, 2014 at 01:32 PM
Hey, Hatredalper, I was in the same exact situation, and the weirdest part was I could edit in Blender (2.69) and after Unity (4.3.1) imports the changes, everything would be as right as rain. Then I got the bug and it kept recurring and I just couldn't understand it. I even went as far as rolling back to Blender 2.68.
So after looking around, it turns out that if you save your .blend file in Blender while in Edit Mode, it will throw the error, but in Object Mode, everything will be cool. I have tested this and it works for me, so maybe it will work out for you as well. Let me know how it goes though.
Good luck
Oh, just found where I got the tip, thanks to chrisall76
Its interesting $$anonymous$$. Thanks for your concern. I will try It some time thank you.
This was the solution for me. Thanks! (I'd upvote, but just created my account and don't have 15 points.)
No worries, but even I just borrowed the info, so it is all cool. Just don't forget to mark the question answered :) Happy game deving!
This solution worked for me right as rain. Why doesn't Unity just update the Blender importer to force the model into object mode first?
Answer by Fornoreason1000 · Nov 25, 2013 at 05:04 AM
Does Blender still have the .FBX export in File/Export? use that since they are usually smaller than .blend files i do the same with Max even though .max import work.
Do the conversion inside blender, it saves the hassle with unity whinging about it and is cheaper storage wise. To do this go to File/Export/Export FBX,
Now last time i used blender it had no FBX import :(, if this is still true, make a folder outside you project folder call it whatever you like(e.g "MyBlenderModels") and save the .Blend files there.
when you want to edit your .fbx model, open the .blend file for it , do your editing and overwrite the .fbx in your project. thus updating it.
its a little more annoying than just jamming it in the Assets folder but i think i had this problem with 2.56 when it came out, told both Unity and Blender and they blamed each other lol.
Yeah as i mentioned blender has fbx import/export capability but i dont like because of the reasond i told. $$anonymous$$aybe i am wrong this is the right way but i still feel exporting blend files manually vs. dragging to the unity(old way) has differences. By the way thank you for your concern.
The problem is that unity doesn't know what Blender you are using(the definition 2.69 doesn't exists as far as unity is concerned),
you can either downgrade blender or do as i suggested. there is zero difference in the actual model itself when exporting manually. I advise the latter.
as for the camera and light being included, try selecting the light and cams, then invert the selection, then export. that should rid them if blender is smart on the way it exports things. or just delete them,
2 weeks ago did you update blender that started this issue?
yes i think this issue started with update 2.69 . I downgrade to 2.67 and try but it was the same problem.I think its like a curse and there is no way back :) I guess i ll export blend files manually from now on but it would be a better if unity can solve this problem. Or any other solution to turn the old way would be better. But anyway thank you for help i appreciated.
As I said earlier, I told them about it(back in Unity3.5) and they said it was because Blender changed their API.
when i confronted the Blender Devs about it. they said it was because they way that unity hooks blender to force an import and they can't fix it because they don't know what unity does.
it may start working again after an Update for Unity but don't expect a miracle.
This approach from both of sides doesnt make sense really. Anyway it seems cant do anything, we have to wait...
Answer by Sinned Angel · Jan 18, 2014 at 07:26 PM
Hi, I got the the problem and I think I have figured out the answer, in my case at least. But I just want to share just in case if anyone has the same problem with me.
Apparently the problem occurred if I switch the input preset to other than blender (maya/max). Because when I tested switching back to 2.68, it works. But when I switch the preset to maya, the problem reoccured. So I tried to switch the 2.69 preset back to blender, everything works fine again.
Your answer
