Is there a way of extending support for other file import? I mean, for example to create an importer for ASE files ( ASCII Extended mesh format ), which put them in our project to build the mesh and associated materials. I currently use a script to do this work.
I guess what you could try is to write an AssetPostprocessor implementing OnPostprocessAllAssets. That gives you the paths to all assets being imported, so you can check those paths for the extensions you are interested in.
When you find any assets you want to process, load the data for those paths using .NET file handling functions, and create Meshes or other objects as needed. Then assign those objects back to the asset using AssetDatabase.AddObjectToAsset().
answered Jan 13 '10 at 12:52 PM
jonas echterhoff ♦♦