jonnenauha
commented
12 years ago We have drag and drop import of ogre .scene, .mesh, .material and i think even textures to materials.
We also have blender2ogre http://code.google.com/p/blender2ogre/ that exports meshes, materials, textures and even skeletons to Ogre assets and even makes you a ready txml file that you can double click to view in Tundra. b2rex afaik is not maintained anymore, so I'm not surprised if its not working with current Tundra versions. There is a clear cut wiki page on blender2ogre site that should make installing and using pretty easy.
We have entity editor that you can multi select entities and save them to a separate txml file. You can bring multiple files into your sever by using multiple --file parameters.
If you have a common cube.mesh but that on the web and use the same url in all of your scene if you want to reuse it, no copying of the asset (i.e. no re-authoring each time).
Do you mean by this that you want Tundra to ship with some basic shapes like cube, cylinder, plane etc.? And have some kind of menu to add meshes quickly to the world? I think that is a good idea and I've been thinking of doing this in our code base. But am not sure if its a supported idea for the Tundra core. I think some of the now shipped meshes like Jack.mesh and random textures should be removed to be honest :) They load into mem every time on startup even if you wont need them in your scene.
peterclemenko
An in world object editor would allow for editing objects and entities in Tundra without relying on b2rex. b2rex is very touchy about version numbers, and it would be easier to just have an editor which can create new objects in tundra by importing assets such as models and textures, and creating the objects from the assets in tundra. It would be optimal to then be able to save objects as prefabs in individual prefab configuration files to allow for importing common objects between scenes without having to re-author the same objects in each scene.