| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| public:t-gede-14-1:lab6 [2014/02/24 14:41] – [Preparation] marino | public:t-gede-14-1:lab6 [2024/04/29 13:33] (current) – external edit 127.0.0.1 |
|---|
| ===== Discussion ===== | ===== Discussion ===== |
| |
| Discussion thread for this lab is here: [[https://piazza.com/class/hq7dlipqggr2qe|Lab 5 Discussion Thread]] | Discussion thread for this lab is here: [[https://piazza.com/class/hq7dlipqggr2qe|Lab 6 Discussion Thread]] |
| |
| ===== Goal ====== | ===== Goal ====== |
| ===== Preparation ===== | ===== Preparation ===== |
| | |
| For the bonus point you might have to replace the pk3 file /Ogre1.9_vc100/OgreSDK_vc10_v1-9-0 | For the bonus point you might have to replace the pk3 file ''/Ogre1.9_vc100/OgreSDK_vc10_v1-9-0 |
| /media/packs/chiropteraDM.pk3 | /media/packs/chiropteraDM.pk3'' **Use of course your own Ogre sdk path.** |
| |
| with this pk3 file: {{:public:t-gede-14-1:chiropteradm.zip| chiropteraDM.zip}} **Rename it back to chiropteraDM.pk3, make sure to change the extension of the file to pk3** | with this pk3 file: {{:public:t-gede-14-1:chiropteradm.zip| chiropteraDM.zip}} **Rename it back to chiropteraDM.pk3, make sure to change the extension of the file to pk3** |
| | |
| | The original file in the OgreSdk folder seemed to be missing a few textures, for this one I replaced the missing textures with one colored textures. |
| ===== Lab Project ===== | ===== Lab Project ===== |
| |
| Follow these steps to complete the lab project: | Follow these steps to complete the lab project: |
| |
| - **Create a New Project** Create a new empty project called "Lab5" in the same way you have created new projects for other lab projects, you can use the provided {{:public:t-gede-14-1:lab6_handout.7z|base}} from Lab2. | - **Create a New Project** Create a new empty project called "Lab6" in the same way you have created new projects for other lab projects, you can use the provided {{:public:t-gede-14-1:lab6_handout.7z|base}} from Lab2. |
| - **Create a Manual Grass Object** You will use the ''createManualObject()'' method in Ogre to specify new geometry inside your code representing a single bundle of grass straws. This method is handy for simple geometries or when you want to procedurally generate them. The grass bundle you create is essentially a set of three quads, each at a 60 degree angle to the next, and that all crossing in the middle - producing a star with 6 spikes if viewed from the top. If viewed from the side, you always see the front of one or two quads, regardless of where you stand. You can therefore make this object hold a texture that is visible from all directions, a property that is called **billboarding**. To get started, create a new method in your ''MyApplication'' class which you should call ''createGrass()''. Inside this method construct the quads and assign grass tecture to them. You construct them by specifying all the vertices first (in model space) and then the indices of each triangle that make up the three quads. Here is the code with the initialization of the manual object and the first quad specified: <code> | - **Create a Manual Grass Object** You will use the ''createManualObject()'' method in Ogre to specify new geometry inside your code representing a single bundle of grass straws. This method is handy for simple geometries or when you want to procedurally generate them. The grass bundle you create is essentially a set of three quads, each at a 60 degree angle to the next, and that all crossing in the middle - producing a star with 6 spikes if viewed from the top. If viewed from the side, you always see the front of one or two quads, regardless of where you stand. You can therefore make this object hold a texture that is visible from all directions, a property that is called **billboarding**. To get started, create a new method in your ''MyApplication'' class which you should call ''createGrass()''. Inside this method construct the quads and assign grass tecture to them. You construct them by specifying all the vertices first (in model space) and then the indices of each triangle that make up the three quads. Here is the code with the initialization of the manual object and the first quad specified: <code cpp> |
| Ogre::ManualObject* manual = _sceneManager->createManualObject("grass"); | Ogre::ManualObject* manual = _sceneManager->createManualObject("grass"); |
| manual->begin("Examples/GrassBlades", Ogre::RenderOperation::OT_TRIANGLE_LIST); | manual->begin("Examples/GrassBlades", Ogre::RenderOperation::OT_TRIANGLE_LIST); |
| grassNode->attachObject(manual); | grassNode->attachObject(manual); |
| </code>To add the two missing quads, use the following corner vertex positions: Quad 2 = (2.5,0,4.3),(-2.5,10,-4.3), (-2.0,0,-4.3), (2.5,10,4.3), Quad 3 = (2.5,0,-4.3),(-2.5,10,4.3),(-2.0,0,4.3),(2.5,10,-4.3). Don't forget to give the vertices texture coordinates, which are the same for all quads. Now call ''createGrass()'' from your ''createScene()'' method and you should see a single bundle of grass right in the middle of the scene. | </code>To add the two missing quads, use the following corner vertex positions: Quad 2 = (2.5,0,4.3),(-2.5,10,-4.3), (-2.0,0,-4.3), (2.5,10,4.3), Quad 3 = (2.5,0,-4.3),(-2.5,10,4.3),(-2.0,0,4.3),(2.5,10,-4.3). Don't forget to give the vertices texture coordinates, which are the same for all quads. Now call ''createGrass()'' from your ''createScene()'' method and you should see a single bundle of grass right in the middle of the scene. |
| - **Instance Grass Object** To create multiple instances of the object you created, you need to first convert it into a proper Ogre **Mesh**. In the ''createGrass()'' method, **replace** your last two lines with the following line:<code>manual->convertToMesh("BladesOfGrass"); | - **Instance Grass Object** To create multiple instances of the object you created, you need to first convert it into a proper Ogre **Mesh**. In the ''createGrass()'' method, **replace** your last two lines with the following line:<code cpp>manual->convertToMesh("BladesOfGrass"); |
| </code> This essentially creates a new model with the name "BladesOfGrass", which you can now refer to in subsequent ''createEntity(<name>)'' calls. So do that next: Let's create 2500 instances of this model, spread across the ground in a 50x50 square patch! You can do this using a nested for-loop (over i=0-49 and j=0-49) and inside the loop do the following:<code> | </code> This essentially creates a new model with the name "BladesOfGrass", which you can now refer to in subsequent ''createEntity(<name>)'' calls. So do that next: Let's create 2500 instances of this model, spread across the ground in a 50x50 square patch! You can do this using a nested for-loop (over i=0-49 and j=0-49) and inside the loop do the following:<code cpp> |
| Ogre::Entity* ent = _sceneManager->createEntity("BladesOfGrass"); | Ogre::Entity* ent = _sceneManager->createEntity("BladesOfGrass"); |
| Ogre::SceneNode* node = _sceneManager->getRootSceneNode()->createChildSceneNode(Ogre::Vector3(i*3,-10,j*3)); | Ogre::SceneNode* node = _sceneManager->getRootSceneNode()->createChildSceneNode(Ogre::Vector3(i*3,-10,j*3)); |
| node->attachObject(ent); | node->attachObject(ent); |
| </code>Notice that you are not naming each entity or node when you create them! But Ogre requires unique names for each of its nodes and entities. When a name is not given, Ogre actually assigns unique names. you can take a look at these names by printing them out inside the loop:<code> | </code>Notice that you are not naming each entity or node when you create them! But Ogre requires unique names for each of its nodes and entities. When a name is not given, Ogre actually assigns unique names. you can take a look at these names by printing them out inside the loop:<code cpp> |
| std::cout << node->getName() << "::"<< ent->getName() << std::endl; | std::cout << node->getName() << "::"<< ent->getName() << std::endl; |
| </code>(Just remember to remove the print-outs for later steps). Do you notice that with 2500 grass models the rendering has slowed dramatically? | </code>(Just remember to remove the print-outs for later steps). Do you notice that with 2500 grass models the rendering has slowed dramatically? |
| - **Optimize using Static Geometry** If we assume that the each grass model will stay in the same location in world space throughout your application life, we can optimize rendering by bundling them up into a packet of pre-transformed static geometry. First create a single new ''StaticGeometry'' instance. Add this line after the ''convertToMesh'' call:<code>Ogre::StaticGeometry* field = _sceneManager->createStaticGeometry("FieldOfGrass"); | - **Optimize using Static Geometry** If we assume that the each grass model will stay in the same location in world space throughout your application life, we can optimize rendering by bundling them up into a packet of pre-transformed static geometry. First create a single new ''StaticGeometry'' instance. Add this line after the ''convertToMesh'' call:<code cpp>Ogre::StaticGeometry* field = _sceneManager->createStaticGeometry("FieldOfGrass"); |
| </code> And now, instead of instancing the grass entities into the scene graph directly, we add them into the static geometry object in the body of our nested for-loop. So, the body of the loop becomes: <code> | </code> And now, instead of instancing the grass entities into the scene graph directly, we add them into the static geometry object in the body of our nested for-loop. So, the body of the loop becomes: <code cpp> |
| Ogre::Entity* ent = _sceneManager->createEntity("BladesOfGrass"); | Ogre::Entity* ent = _sceneManager->createEntity("BladesOfGrass"); |
| field->addEntity(ent,Ogre::Vector3(i*3,-10,j*3)); | field->addEntity(ent,Ogre::Vector3(i*3,-10,j*3)); |
| </code> Finally, after we have added all the entities to our ''field'', we need to ask the static geometry to "bake"/optimize with the following call: <code>field->build(); | </code> Finally, after we have added all the entities to our ''field'', we need to ask the static geometry to "bake"/optimize with the following call: <code cpp>field->build(); |
| </code>Now you should try running the scene again and see if there is any improved performance! | </code>Now you should try running the scene again and see if there is any improved performance! |
| - **Testing Another Scene Manager** The so called "world geometry" of a game is often considered static and can be highly optimized for rendering. One optimized format for representing a static world is the BSP level format used originally by id's Quake engine. Ogre can read worlds in this format and display them using the ''BspSceneManager''. To try this, add the following method in your application<code> void loadQuakeMap() { | - <box green 100% | Bonus point>**Testing Another Scene Manager** The so called "world geometry" of a game is often considered static and can be highly optimized for rendering. One optimized format for representing a static world is the BSP level format used originally by id's Quake engine. Ogre can read worlds in this format and display them using the ''BspSceneManager''. To try this, add the following method in your application<code cpp> void loadQuakeMap() { |
| // add the Quake archive to the world resource group | // add the Quake archive to the world resource group |
| Ogre::ResourceGroupManager& rgm = Ogre::ResourceGroupManager::getSingleton(); | Ogre::ResourceGroupManager& rgm = Ogre::ResourceGroupManager::getSingleton(); |
| rgm.loadResourceGroup(rgm.getWorldResourceGroupName(), false); | rgm.loadResourceGroup(rgm.getWorldResourceGroupName(), false); |
| } | } |
| </code>Of course replace the absolute path here with a path that is correct on your system. To initialize the camera to properly view this map (it's actually rotated), add the following camera initialization method:<code> void setupQuakeMapView(Ogre::Camera* cam){ | </code>Of course replace the absolute path here with a path that is correct on your system. To initialize the camera to properly view this map (it's actually rotated), add the following camera initialization method:<code cpp> void setupQuakeMapView(Ogre::Camera* cam){ |
| // modify camera for close work | // modify camera for close work |
| cam->setNearClipDistance(4); | cam->setNearClipDistance(4); |
| } | } |
| </code> | </code> |
| Finally, you need to tell Ogre to use the BSP scene manager, which you do when you create your scene manager in the ''startup()'' method of your application. You can name the scene manager explicitly like this:<code>_sceneManager =_root->createSceneManager("BspSceneManager"); | Finally, you need to tell Ogre to use the BSP scene manager, which you do when you create your scene manager in the ''startup()'' method of your application. You can name the scene manager explicitly like this:<code cpp>_sceneManager =_root->createSceneManager("BspSceneManager"); |
| </code> Now you have everything you need to display the Quake level, all you have to do is to call ''loadQuakeMap()'' and ''setupQuakeMapView(camera) from your ''startup'' method and comment out some of the other things you don't wish to include (e.g. the grass above). Also, you may want to free up the camera movement (i.e. go back to the free mouse movement of camera, instead of having camera following the Ogre). | </code> Now you have everything you need to display the Quake level, all you have to do is to call ''loadQuakeMap()'' and ''setupQuakeMapView(camera) from your ''startup'' method and comment out some of the other things you don't wish to include (e.g. the grass above). Also, you may want to free up the camera movement (i.e. go back to the free mouse movement of camera, instead of having camera following the Ogre). |
| | </box> |
| |
| | |
| ===== When You Are Finished ===== | ===== When You Are Finished ===== |
| |
| Upload your **commented source files** into Lab6 in MySchool (zip them up if more than one). The lab projects will not be graded, but their completion counts towards your participation grade. | Upload your **commented source files** into Lab6 in MySchool. The lab projects will not be graded, but their completion counts towards your participation grade. |
