Differences

This shows you the differences between two versions of the page.

--- public:t-gede-12-1:lab_2 [2012/02/02 13:37] – [What to Try] hannes
+++ public:t-gede-12-1:lab_2 [2024/04/29 13:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Lab 2: Getting Meshes and Materials into Ogre 3D ======
-<note warning>Under construction</note>
 ===== Required Tools =====
@@ Line 22: / Line 20: @@
     * Add the line **FileSystem=Models** in the **Popular** section of your application's **resources.cfg** (This tells your application that it should search for named resources in this folder)
   - Create a model in Blender (even just use the default cube you get when you start up Blender)
+    * There is a lot of good resources on Blender modeling, including the [[http://www.blender.org/education-help/tutorials/getting-started/|Official Getting Started]] tutorials
     * It is a good idea to save your model in the Blender file format early and often
     * Pay attention to what you name your geometry, this becomes the name of the exported mesh
@@ Line 28: / Line 27: @@
   - Run the **OgreXMLConverter** command line tool on the exported **XML** mesh file to turn it into a binary Ogre **mesh** file
   - Create an **Entity** in your Ogre application from the mesh you just exported
-    * In C++ it would look like this:<code>Ogre::Entity* mycube = mSceneMgr->createEntity("MyCube", "MyCubeMesh.mesh");
+    * In C++ it would look like this:
+        <code cpp>        Ogre::Entity* mycube = mSceneMgr->createEntity("MyCube", "MyCubeMesh.mesh");
         Ogre::SceneNode* cubeNode = mSceneMgr->getRootSceneNode()->createChildSceneNode();
         cubeNode->attachObject(mycube);
@@ Line 37: / Line 37: @@
 Here are things you should now play with:
+  * Open up your exported **mesh** **XML** file and make sure you understand its structure
-  * Open up your exported mesh **XML** file and make sure you understand its structure
+  * Try changing values inside the exported **mesh** **XML** file and observe the changes in your Ogre application, but remember to run the OgreXMLConverter again!
-  * Try changing values inside the exported mesh **XML** file and observe the changes in your Ogre application, but remember to run the OgreXMLConverter again!
   * Notice that inside the **XML** file the submesh refers to a **Material** by name, find the corresponding ** *.material ** file in your model folder (it got exported along with the mesh XML file) and read through it. This is the material that Ogre reads in along with the mesh.
-  * Try changing values inside the exported material file and observe the changes in your Ogre application (you do not have to run the OgreXMLConverter again for this, the material is already in the right format)
+  * Try changing values of the material (e.g. the diffuse values) inside the exported material file and observe the changes in your Ogre application (you do not have to run the OgreXMLConverter again for this, the material is already in the right format)
+  * Create a new material inside the same material file, by copy-pasting the material definition and changing its name (e.g. into **BlueMaterial**) and give it different values (e.g. making the diffuse color blue).
+    * To test this new material, you can simply assign it to any entity in your Ogre application with the **setMaterialName** method like this:
+  <code cpp>    myCube->setMaterialName("BlueMaterial");</code>
+  * See if you can create several entities from your original mesh, but assign different materials to each of them