navi homePPSaboutscreenshotsdownloaddevelopmentforum

Changes between Version 4 and Version 5 of content/tools/FromBlenderToOrxonox

Feb 27, 2017, 5:05:20 PM (3 years ago)

Updated to Blender 2.69


  • content/tools/FromBlenderToOrxonox

    v4 v5  
    11= Exporting Objects From Blender To Orxonox =
    3 ''Checked with Blender 2.49b on 6. Mar. 2010 by [wiki:Deca beni]''
     3''Checked with Blender 2.69 on 27 Feb. 2017''
    55This page explains how to export 3D models from Blender and view them in a Level in Orxonox.
    1111=== Prerequisites ===
    13 To export to mesh we first need the 'Blender Exporter' and the 'Ogre Command-line Tools'. Get them from the [ Ogre Tools Download Page]. For Blender 2.49b, you will need to have Python installed on your system, version 2.5.2 or higher. If you use Linux, you will most probably already have Python installed.
     13To export to mesh we first need the 'Blender Exporter' and the 'Ogre Command-line Tools'.
     15The Blender exporter works well with [ Blender 2.69], other versions haven't been tested.
     17The Ogre command-line tools are available [ here (Windows and Mac)].[[BR]]
     18On linux, its called 'ogre tools'. We need the 'ogre-1.8-tools' version. For the ETH tardis PCs I uploaded the binary [ here]
    1520==== Blender Exporter ====
    17 If a system wide installation is intended, unpack the zip archive you downloaded from the Ogre webpage into /usr/share/blender/scripts. If only a local installation in required or possible (probably due to the lack of permissions), unpack it somewhere in your home dir, ~/.blender/scripts/ is suggested.
     22Download the addon [ here] (
    19 '''Note:''' On the Tardis computers of D-ITET, the Blender Mesh Exporter is already installed.
    21 '''Note 2:''' The manual for the OGRE Meshes Exporter can be found [ here].
     24In Blender, open 'User Preferences' -> 'Install from file ...'.[[BR]]
     25Then choose the .zip file and activate the addon.
    2428==== Command-line Tools ====
    26 Download and extract to any location you want, just remember where. With Windows it should usually extract automatically to C:\OgreCommandLineTools
     30Download and extract to any location you want, just remember where.
    2832=== Exporting to mesh ===
    30 [[Image(wiki:BlenderExport:export.png, right)]]
    31  1. Make sure your model reaches the [wiki:BlenderGuidelines general guidelines for a mesh].
    3234 1. Check if all textures for your objects are loaded into Blender.
    3335 1. Make sure your materials don't still have the generic name ('Material', 'Material.001', ...), otherwise Orxonox might not choose the correct material for your model.
    34  1. It is very helpful, to name your objects and data blocks if you have not done so already (see picture).
    35  1. Open the export dialog (File -> Export -> OGRE Meshes). If this option doesn't show up, update the menus (Scripts Windows -> Scripts -> Update Menus). If it still doesn't show up, make sure you have installed the script correctly and you have python installed. Verify in the User Preferences Window under ''File Paths'', that the path to Python scripts is correct.
    36  1. Select the model. Hit Preferences and provide the Path to the Ogre Command-line Tools (e.g. C:\OgreCommandLineTools), return to the main window. Check "OgreXML Converter", uncheck "Copy Textures", if your texture resides in the same folder as your blend file. Pick a sensible filename for your material under Material Settings.
    37  1. Hit Export.
     36 1. Name your objects and meshes
     37 1. Open the export dialog (File -> Export -> Ogre 3D). If it doesn't show up, make sure you have installed the script correctly.
     38 1. Select the model and hit Export. This will produce a '.mesh.xml' file
    39 This will create (at least) 4 new files in the blend-file-folder: a .mesh file, a .mesh.xml file, and a .material file. Most likely, a log file of the OgreXML Converter will be produced also. Ignore it for now.
     40Then you need to manually convert them with the XML converter.
    41 Check if the new created .mesh file is version 1.41 or 1.40 (open it with gedit or any editor and have a look at the first lines). If your exported mesh has 1.41 you have to export the .xml file by yourself using the following steps:
     42In Windows, drag the file on the XML converter executable.[[BR]]
     43In Linux, open a terminal and execute {{{./OgreXMLConverter fileName.mesh.xml}}}
    43  1. Download and extract the OgreXMLConverter from [ here]
    44  2. Copy the .mesh file from the previous exported Mesh (exported from Blender) into the OgreXMlConverter folder
    45  3. Use the following command to create a 1.40 version mesh
    46 {{{
    47 #!html
    48 <pre class="wiki" style="white-space:normal;">
    49 wine OgreXMLConverter yourmesh.xml
    50 </pre>
    51 }}}
     45This will create (at least) 2 new files: A .mesh file and a .material file. Most likely, a log file of the OgreXML Converter will be produced also.
    53 The material filename will be the one you chose in the export dialog. This file contains all materials that are used in your scene, so if you export several meshes from the same scene (blend-file), you will only need one material file.
    55 The name of the two mesh files will be the one you picked in the material window (see picture). The .mesh.xml file is a XML file containing the data of your object. Because you checked "OgreXML Converter", the XML file was directly converted to the binary mesh file, which we need to load the model into the game.
    5748=== To Orxonox ===