Game Development Stack Exchange is a question and answer site for professional and independent game developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

As a coder, I don't have much experience in asset creation workflow. I'm trying to figure out the best way to work effectively with Unity + Blender combo. I don't export to FBX, I prefer to work directly with Blender files, with no intermediate export step.

I have parts of the map that I place in the scene: walls, decorations, whole rooms, etc - I keep them in one Blender file. I have models of collectibles, like treasures, keys and the like - I keep them in another Blender file. I have models of characters, which I keep in another one. It has worked OK so far, however I feel like it's not the best way to work. While it makes sense in Blender, it gets messy in Unity.

What is an effective way of working with this combo? Or with asset import in a larger project, in general? Should I export to FBX instead of using Blender files directly? I'd like to understand now how and why to adapt the workflow than have everyone involved being slowed down later.

share|improve this question

Pros of single model per file:

  • Imported nodes contain only what's related to a specific single prefab
  • Editor needs to re-import only what has changed, not the whole file

Cons of single model per file:

  • Can't easily work with multiple models at the same time
  • Can't compare model scale and alignment easily in Blender
  • Can't reuse materials or textures easily
  • Multiple Blender files will take more space than just a few
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.