Center for Analysis and Design of Intelligent Agents

User Tools

Site Tools

Trace:
public:t-gede-14-1:lab5

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
public:t-gede-14-1:lab5 [2014/02/16 11:56] – [Lab Project] marinopublic:t-gede-14-1:lab5 [2024/04/29 13:33] (current) – external edit 127.0.0.1
Line 13: Line 13:
 ===== Preparation ===== ===== Preparation =====
  
-No special preparation is required - preparing the joypad is explained in the project steps below.+No special preparation is required - preparing the joypad is explained in the project steps below. You do not have to use the latest lab as a base for this one, you can use the base of lab2 or any other **//except lab1//** if you feel like the project has become to bloated. 
  
 **NOTE:** To get the joypads to start sending data, you may have to press a **Mode** button in the center of the device. This is true for the joypads handed out in the lab class! **NOTE:** To get the joypads to start sending data, you may have to press a **Mode** button in the center of the device. This is true for the joypads handed out in the lab class!
 +
 +
  
 ===== Lab Project ===== ===== Lab Project =====
Line 22: Line 24:
  
   - **Create a New Project** Create a new empty project called "Lab4" in the same way you have created new projectsfor other lab projects.   - **Create a New Project** Create a new empty project called "Lab4" in the same way you have created new projectsfor other lab projects.
-  - <box green 100% | **2. half a Bonus pt :),** lets reuse the blasted resources and plugins files. !> +  - <box green 100% | **2. An early Bonus pt :),** Lets reuse the blasted resources and plugins files. !> 
    - **Create a folder** somewhere in your filesystem to hold the ''resources_d.cfg, plugins_d.cfg and Models folder'' and copy the above mentioned files and folders to the folder you create.    - **Create a folder** somewhere in your filesystem to hold the ''resources_d.cfg, plugins_d.cfg and Models folder'' and copy the above mentioned files and folders to the folder you create.
    - **Change the following lines in your code:** dont forget to make the backslashes forward slashes, and repeating them for the sake of c++ strings escape characters.<code cpp>     - **Change the following lines in your code:** dont forget to make the backslashes forward slashes, and repeating them for the sake of c++ strings escape characters.<code cpp> 
Line 39: Line 41:
 </code> </code>
    - **From the previous lab** You created a folder Models, and Materials if you did the bonus points. In the ''resources_d.cfg'' you must change the line ''FileSystem=Models'' and Materials respectively, to ''FileSystem=(your_absalutePath)/Models''    - **From the previous lab** You created a folder Models, and Materials if you did the bonus points. In the ''resources_d.cfg'' you must change the line ''FileSystem=Models'' and Materials respectively, to ''FileSystem=(your_absalutePath)/Models''
-   - Now whenever you modify the resources or add files or folders, do that in the folder you just created and all your lab assignments will reuse the configuration files.+   - **Now whenever you modify the resources or add files or folders**, do that in the folder you just created and all your lab assignments will reuse the configuration files.
 </box> </box>
   - **Plug in and Test Joypad** Plug a USB joypad into your computer and find the device in your system's control panel (usually under "Devices and Printers"). Examine the device properties and find a small test panel for the device. Make sure the device works. Intall necessary drivers if the system is not picking it up.    - **Plug in and Test Joypad** Plug a USB joypad into your computer and find the device in your system's control panel (usually under "Devices and Printers"). Examine the device properties and find a small test panel for the device. Make sure the device works. Intall necessary drivers if the system is not picking it up. 
Line 73: Line 75:
 </code> Don't forget to also **destroy** the joystick object in your destructor, just like you do with the mouse and keyboard. Make sure this code compiles and check to see if your joypad gets properly initialized. </code> Don't forget to also **destroy** the joystick object in your destructor, just like you do with the mouse and keyboard. Make sure this code compiles and check to see if your joypad gets properly initialized.
   - **Move Character with POV** Now you want to give players the option to move the character by pressing one of the directions on the POV (point of view) digital button on the left of the joypad. You should still retain the keyboard control of the movement. First explore the values you get when you press the POV button. <code cpp>   - **Move Character with POV** Now you want to give players the option to move the character by pressing one of the directions on the POV (point of view) digital button on the left of the joypad. You should still retain the keyboard control of the movement. First explore the values you get when you press the POV button. <code cpp>
 +// Create a member variable in the MyFrameListener class: int _povState
 +
 bool MyFrameListener::povMoved(const OIS::JoyStickEvent &arg, int pov) { bool MyFrameListener::povMoved(const OIS::JoyStickEvent &arg, int pov) {
- int direction = arg.state.mPOV[pov].direction; + _povState = arg.state.mPOV[pov].direction; 
- std::cout << direction << "\n";+ std::cout << _povState << "\n";
  return true;  return true;
 } }
-</code> Notice that you get special codes for each direction and the code 0 when you let go of the button (it goes back into center position). Unlike the keyboard, you don't get continuous events when you press and hold the directions! To use this for moving the character you need to store the last direction code received and reset it when you receive 0. In the same callback (below the two lines above), add the following code:<code> +</code> Notice that you get special codes for each direction and the code 0 when you let go of the button (it goes back into center position). Unlike the keyboard, you don't get continuous events when you press and hold the directions! To use this for moving the character you need to store the last direction code received and reset it when you receive 0. In the same callback (below the two lines above), add the following ''OR'' operation to your keyboard movement if statements:<code cpp> 
- _WalkingNorth = false; +if (_Keyboard->isKeyDown(OIS::KC_UP) || _povState == OIS::Pov::North) { 
- _WalkingSouth = false; + SinbadTranslate += Ogre::Vector3(0, 0, -1); 
- _WalkingEast = false; + walked = true;  
- _WalkingWest = false; + _rotation = 3.14f; 
- switch(direction) { +} 
- case OIS::Pov::North: +if (_Keyboard->isKeyDown(OIS::KC_DOWN) || _povState == OIS::Pov::South) { 
- _WalkingSouth = true; + SinbadTranslate += Ogre::Vector3(0, 0, 1); 
- break; + walked = true;  
- case OIS::Pov::South: + _rotation = 0.0f; 
- _WalkingNorth = true;  +} 
- break; +if (_Keyboard->isKeyDown(OIS::KC_LEFT) || _povState == OIS::Pov::West) { 
- case OIS::Pov::East: + SinbadTranslate += Ogre::Vector3(-1, 0, 0); 
- _WalkingWest = true; + walked = true;  
- break; + _rotation = -1.57f; 
- case OIS::Pov::West: +} 
- _WalkingEast = true; +if (_Keyboard->isKeyDown(OIS::KC_RIGHT) || _povState == OIS::Pov::East) { 
- break; + SinbadTranslate += Ogre::Vector3(1, 0, 0); 
- case OIS::Pov::Centered: + walked = true;  
- break; + _rotation = 1.57f; 
- } +} 
-</code> Make sure also to declare each of the ''bool'' variables as member variables in your class! This is a bit verbose here for clarity, but you can also pack these bits into a single byte to save space and use bit masking. Notice that the POV directions don't necessarily map correctly onto the directions in our world. You can now use these booleans just like the keyboard button presses for moving the character in your class's ''frameStarted'' method. In fact, you can use the OR operator to check to see if a keyboard direction was pressed OR the corresponding walking direction is true, for example: <code> +</code> Finally, you need to capture the joystick input in this ''frameStarted'' method: <code cpp> 
-                if(_Keyboard->isKeyDown(OIS::KC_UP) || _WalkingNorth) { ... } +if( _Joystick )  
-</code> Finally, you need to capture the joystick input in this ''frameStarted'' method: <code> + _Joystick->capture(); 
- if( _Joystick )  +
- _Joystick->capture(); +
 </code>    </code>   
-  - **Rotate Camera with Analog Stick** Now you should try to rotate (or swivel) the camera around the character with the right analog stick on the joypad. You first need to create a new member variable in your MyFrameListener class that stores the current camera angle (e.g. ''float _camangle''). In your constructor, initialize this angle to the value ''-1*Ogre::Math::HALF_PI'' so that this angle corresponds to the initial orientation of the character. As with the POV button, you should examine the values you get from the analog axes of your joypad. Add the following lines to your ''axisMoved'' callback:<code> +  - **Rotate Camera with Analog Stick** Now you should try to rotate (or swivel) the camera around the character with the right analog stick on the joypad. You first need to create a new member variable in your MyFrameListener class that stores the current camera angle (e.g. ''float _camangle''). In your constructor, initialize this angle to the value ''-1*Ogre::Math::HALF_PI'' so that this angle corresponds to the initial orientation of the character. As with the POV button, you should examine the values you get from the analog axes of your joypad. Add the following lines to your ''axisMoved'' callback:<code cpp> 
- int value = e.state.mAxes[axis].abs; +int value = e.state.mAxes[axis].abs; 
- switch(axis) { +switch(axis) { 
- case 0: + case 1: 
- std::cout << "0:" << value << "\n"; + std::cout << "1:" << value << "\n"; 
- break; + break; 
- } +} 
-</code> You can add more cases to this to observe values along the other axes. You will notice that they each run from a negative 32768 to a positive 32767, which corresponds to the range of a 16-bit signed integer. For one of these axes, we want this range to map onto a camera angle that runs from 0 to 360 degrees (calculated in radians). The camera angle can therefore be calculated as follows:<code> +</code> You can add more cases to this to observe values along the other axes. You will notice that they each run from a negative 32768 to a positive 32767, which corresponds to the range of a 16-bit signed integer. For one of these axes, we want this range to map onto a camera angle that runs from 0 to 360 degrees (calculated in radians). The camera angle can therefore be calculated as follows:<code cpp> 
-               _camangle = Ogre::Math::TWO_PI * ((float(-1*value) / float(_Joystick->MAX_AXIS) + 1.0f)/2.0f)+Ogre::Math::HALF_PI; +_camangle = Ogre::Math::TWO_PI * ((float(-1*value) / float(_Joystick->MAX_AXIS) + 1.0f)/2.0f)+Ogre::Math::HALF_PI; 
-</code> The ''-1'' in here is to reverse the axis value to let the direction of movement map better onto the perceived camera motion and the HALF_PI offset is just so that we start by facing the ogre model correctly. Finally, in the ''frameStarted'' callback you have to continue to update the camera position and orientation: <code> +</code> The ''-1'' in here is to reverse the axis value to let the direction of movement map better onto the perceived camera motion and the HALF_PI offset is just so that we start by facing the ogre model correctly. Finally, in the ''frameStarted'' callback you have to continue to update the camera position and orientation: <code cpp> 
- _Cam->setPosition(_myogrenode->getPosition()+Ogre::Vector3(20.0f*Ogre::Math::Cos(_camangle), 10.0f, 20.0f*Ogre::Math::Sin(_camangle))); +_Cam->setPosition(_myogrenode->getPosition()+Ogre::Vector3(20.0f*Ogre::Math::Cos(_camangle), 10.0f, 20.0f*Ogre::Math::Sin(_camangle))); 
- _Cam->lookAt(_myogrenode->getPosition());+_Cam->lookAt(_myogrenode->getPosition());
 </code> Test to see if this works.    </code> Test to see if this works.   
-  - **OPTIONAL: Map more axes and buttons** Add more controls to the camera or other things in the environment. For example, zoom the camera in and out with a different axis of movement or let a button start the effect from lab 2.         + 
 +====== Bonus points ====== 
 +<box green 100% | Bonus points> 
 +   - **Make the input a little bit more useful :)** Either make your own modifications to the input or follow the instructions given:  
 +     - **Remove the code** from frameStarted: <code cpp> 
 +Ogre::Vector3 SinbadTranslate(0, 0, 0); 
 +float _rotation = 0.0f; 
 + 
 +if (_Keyboard->isKeyDown(OIS::KC_UP) || _povState == OIS::Pov::North) { 
 + SinbadTranslate += Ogre::Vector3(0, 0, -1); 
 + walked = true;  
 + _rotation = 3.14f; 
 +} 
 +if (_Keyboard->isKeyDown(OIS::KC_DOWN) || _povState == OIS::Pov::South) { 
 + SinbadTranslate += Ogre::Vector3(0, 0, 1); 
 + walked = true;  
 + _rotation = 0.0f; 
 +} 
 +if (_Keyboard->isKeyDown(OIS::KC_LEFT) || _povState == OIS::Pov::West) { 
 + SinbadTranslate += Ogre::Vector3(-1, 0, 0); 
 + walked = true;  
 + _rotation = -1.57f; 
 +} 
 +if (_Keyboard->isKeyDown(OIS::KC_RIGHT) || _povState == OIS::Pov::East) { 
 + SinbadTranslate += Ogre::Vector3(1, 0, 0); 
 + walked = true;  
 + _rotation = 1.57f; 
 +} 
 + 
 +_node->translate(SinbadTranslate * evt.timeSinceLastFrame * _WalkingSpeed); 
 +_node->resetOrientation(); 
 +_node->yaw(Ogre::Radian(_rotation)); 
 +</code> 
 +    - **Now we will make the Sinbad move with the left analog stick** Add these two member variables to the ''MyFrameListener'' class, they will hold the values for the left analog axis. And make sure to initialize them all to 0. <code cpp> 
 +int _walkMagnitude;  
 +int _turnMagnitude; 
 +float _orientation; 
 +</code> 
 +    - **Capture the state of the left axis** in the function ''axisMoved'' by adding to the previously created switch statement. <code cpp> 
 +bool MyFrameListener::axisMoved(const OIS::JoyStickEvent &e, int axis) { 
 + int value = e.state.mAxes[axis].abs; 
 + switch (axis) { 
 + case 1: 
 + _camangle = Ogre::Math::TWO_PI * ((float(-1 * value) / float(_Joystick->MAX_AXIS) + 1.0f) / 2.0f) + Ogre::Math::HALF_PI; 
 + break; 
 +        // Add these lines, dont forget to break :) 
 + case 2: 
 + _walkMagnitude = (float)value / -float(_Joystick->MAX_AXIS); // Map the range to -1 to 1 
 + break; 
 + case 3: 
 + _turnMagnitude = (float)value / -float(_Joystick->MAX_AXIS); // Map the range to -1 to 1 
 + break; 
 + } 
 + return true; 
 +} 
 +</code> 
 +    - **Now add the new input method for Sinbad** add this code in place for the code removed from section //a// <code cpp> 
 +bool walked = false; 
 +Ogre::Vector3 SinbadTranslate(0, 0, 0); 
 + 
 +// If the joystick is not available, use the keyboard as input. 
 +if (!_Joystick) { 
 + if (_Keyboard->isKeyDown(OIS::KC_UP)) { 
 + _walkMagnitude = 1; 
 + } 
 + else if (_Keyboard->isKeyDown(OIS::KC_DOWN)) { 
 + _walkMagnitude = -1; 
 + } 
 + else { 
 + _walkMagnitude = 0; 
 + } 
 + 
 + if (_Keyboard->isKeyDown(OIS::KC_LEFT)) { 
 + _turnMagnitude = 1; 
 + } 
 + else if (_Keyboard->isKeyDown(OIS::KC_RIGHT)) { 
 + _turnMagnitude = -1; 
 + } 
 + else { 
 + _turnMagnitude = 0; 
 + } 
 +} 
 +// Create the translation vector. 
 +SinbadTranslate = _node->getOrientation().zAxis() * evt.timeSinceLastFrame * _WalkingSpeed * _walkMagnitude; 
 +walked = true; 
 + 
 +// Increment the roation angle. 
 +_orientation += evt.timeSinceLastFrame * _turnMagnitude*2; 
 + 
 +// Now finally apply the rotation and translation. 
 +_node->translate(SinbadTranslate); 
 +_node->setOrientation(Ogre::Quaternion(Ogre::Radian(_orientation), Ogre::Vector3::UNIT_Y)); 
 +</code> 
 +  - **As of now the camera follows Sinbad in a strange manner.** By adding buffered keyboard input, create a method of toggling the camera from following Sinbad behind his back, and a free roaming camera that you cam move with the mouse and "WASD" \\ **Hints:** \\ <code cpp>  
 +// This will make the camera a child of the Sinbad Scene node, and thus all transformation made to Sinbad will be applied to the Camera as well. 
 +_node->attachObject(_Cam);  
 +</code> Buffered keyboard input, Make the following changes to the MyFrameListener class to enable the buffered keyboard input <code cpp> 
 +// Add the inheritance of OIS::KeyListener, this will be required to make your FrameListener handle 
 +// the buffered input by providing you with the two virtual functions, keyPressed and keyReleased. 
 +class MyFrameListener : public Ogre::FrameListener, OIS::JoyStickListener, OIS::KeyListener { 
 +    //... 
 +    // Change the way the frameListener initializes the Keyboard object pointer in the constructor. 
 +    // And make "MyFrameListener" the event callback Handler for the keyboard. 
 +    MyFrameListener() : ... { 
 +        //... 
 +        // Notice the last parameter in the createInputObject() has changed from false to true!! 
 +        // That parameter indicates that we want to enable buffered keyboard input. 
 +        _Keyboard = static_cast<OIS::Keyboard*>(_InputManager->createInputObject(OIS::OISKeyboard, true)); 
 + _Keyboard->setEventCallback(this); 
 +        //... 
 +    } 
 +     
 +    // Now implement those two virtual functions. 
 +    virtual bool keyPressed(const OIS::KeyEvent &arg) { 
 + return true; 
 +    } 
 +    virtual bool keyReleased(const OIS::KeyEvent &arg) { 
 +        return true; 
 +     } 
 +     //... 
 +} 
 +</code>Now you have those two functions that trigger only once per key press, and are not continuous like before, did I mention buffered input :)? 
 + 
 +</box>      
  
  
Line 125: Line 250:
 ===== When You Are Finished ===== ===== When You Are Finished =====
  
-Upload your **commented source files** into Lab4 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 Lab5 in MySchool (zip them up if more than one). The lab projects will not be graded, but their completion counts towards your participation grade.
/var/www/cadia.ru.is/wiki/data/attic/public/t-gede-14-1/lab5.1392551805.txt.gz · Last modified: 2024/04/29 13:32 (external edit)
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki