koobas.hobune.stream
Unity freezes when right-clicking fbx file
When I right click an FBX file in Unity it freezes so badly I have to restart. It does this almost every time. Sometimes Unity freezes when I import the FBX as well. There is a message with an FBX warning when this happens, however since the program has frozen I cannot click on it to see what the message is saying.
I'm using Unity 5.1, and I imported the FBX file from blender.
Edit: the warning is:
ImportFBX Warnings: Mesh 'Object X' has 2 (out of 430) vertices with no weight and bone assigned (they will be assigned to bone #0 with weight 1). The list of vertices: 196, 429
I weight painted the object again, imported a new fbx, and now right clicking doesn't affect the new fbx, but Unity still freezes when I click the old ones. I don't know why this caused such a massive problem, or even if that is the sole cause. Any further information would be appreciated.
Ah, ok. The problem with the model was that it had many separated components that were linked to one armature. That in itself is not a problem. The problem was that Blender decided to create multiple redundant animations for each object. The freezing seems to be the time it took Unity to load all those animations (there must have been about 80).
I've posted on the Blender forum as this is clearly not a Unity problem.
This is not a solution to your problem but meanwhile you manage to solve it, you can paste de .blend file directly to the project folder
That's my preference as it means I can edit the file directly without having to re-import. However, I had to stop doing that as Unity was having difficulty reading the animations off a blend file for some reason (I've posted about this in the past). $$anonymous$$aybe unity 5 has improved?
your object 430 vertices but 2 of them don`t have bone and weight i think you must find them and give them bone and weight to solve that
if problem not solve try another file with FBX format built by blender for test
Thanks man, but that's what I did. Have a look at the edited question. It seems to have fixed the problem. I'm left wondering why a vertex without any weighting assigned causes such a problem. I should probably write directly to unity support as this seems to be a bug.
