| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| public:t-vien-08-1:lab_5_materials [2008/02/07 00:23] – hannes | public:t-vien-08-1:lab_5_materials [2024/04/29 13:33] (current) – external edit 127.0.0.1 |
|---|
| |
| * Download and unzip the [[http://www.ru.is/kennarar/hannes/classes/ve2008/Lab5Assets.zip|Lab 5 Asset File]] into your working directory | * Download and unzip the [[http://www.ru.is/kennarar/hannes/classes/ve2008/Lab5Assets.zip|Lab 5 Asset File]] into your working directory |
| | |
| | |
| |
| |
| </code> | </code> |
| |
| - **Setting Up:**\\ Create a **World** class derived from **DirectObject** like before and set up a camera at **(0,-70,2)** with FOV of **50** and a near clipping plane of **0.01**. Load and display the environment model called **environment** (it comes standard with Panda 3D, so you don't need any path information) and scale it down to **30%**. Add your camera movement code from [[Lab 2 Materials|Lab 2]]. Verify that you can now move around the landscape. | - **Setting Up:**\\ Create a **World** class derived from **DirectObject** like before and set up a camera at **(0,-70,2)** with FOV of **50** and a near clipping plane of **0.01**. Load and display the environment model called **Models/environment** and scale it down to **30%**. Add your camera movement code from [[Lab 2 Materials|Lab 2]]. Verify that you can now move around the landscape. |
| - **Adding a Moving Character:**\\ Create a **Character** class derived from **FSM.FSM** (Finite State Machine). In the constructor, you first need to call the constructor of the parent like this:<code python> | - **Adding a Moving Character:**\\ Create a **Character** class derived from **FSM.FSM** (Finite State Machine). In the constructor, you first need to call the constructor of the parent like this:<code python> |
| FSM.FSM.__init__(self,"Character") | FSM.FSM.__init__(self,"Character") |
| <mouse_picker>.make_pickable(<youractornodepath>) | <mouse_picker>.make_pickable(<youractornodepath>) |
| </code> Now, whenever you click on your actor, an event with the name **'clicked_render/Eve'** occurs, which you can of course **accept** in your **Character** class. See if you can make your character respond to your clicking. | </code> Now, whenever you click on your actor, an event with the name **'clicked_render/Eve'** occurs, which you can of course **accept** in your **Character** class. See if you can make your character respond to your clicking. |
| - **Starting a Conversation:**\\ Create a new state called **Conversing** and enter that state when you click on your character in the **Noticing** state. Make sure the click is only received if the character is actually in the **Noticing** state (hint: you'll need to use the **ignore** method as well as the **accept** method). Similarly, only in the **Conversing** state should you receive the **'clicked_None'** event (when user clicks on nothing) and that should send the character back to **Pacing**. As for what happens in the **Conversing** state, you can use [[http://www.panda3d.org/wiki/index.php/OnscreenText|**OnscreenText**]] to display a greeting while you are in this state (and remove it when you exit the state). Verify that the behavior of your character is following the original state diagram. | - **Starting a Conversation:**\\ Create a new state called **Conversing** and enter that state when you click on your character in the **Noticing** state. Make sure the click is only received if the character is actually in the **Noticing** state (hint: you'll need to use the **ignore** method as well as the **accept** method). Similarly, only in the **Conversing** state should you receive the **'clicked_None'** event (when user clicks on nothing) and that should send the character back to **Pacing**. As for what happens in the **Conversing** state, you can use [[http://www.panda3d.org/wiki/index.php/OnscreenText|OnscreenText]] to display a greeting while you are in this state (and remove it when you exit the state). Verify that the behavior of your character is following the original state diagram. |
| - **Conversation Machine:**\\ Instead of just showing a greeting when you enter the **Conversing** state, let's start an actual dialog! Use the [[http://www.panda3d.org/wiki/index.php/FSM_with_input|"FSM with input"]] method (and a single ''defaultFilter'') to create a new **Conversation** class that handles the branching dialog shown in this diagram: {{public:t-vien-08-1:conversation_states.png|}}\\ The diagram shows the state names in the blue boxes and the text that should shown on the screen when entering each state. The user picks response '1' by pressing the '1' key on the keyboard, which then takes the conversation to the state connected by the arrow labeled '1'. Same for '2'. The simplest way to do this, is to have the new class (that inherits from FSM.FSM) accept '1' and '2' as keyboard events, which are handled by the same handler method that directly calls the ''self.request(<input>)'' method for advancing to the next state. | - **Simple Conversation Machine:**\\ Instead of just showing a greeting when you enter the **Conversing** state, let's start an actual dialog! Use the [[http://www.panda3d.org/wiki/index.php/FSM_with_input|"FSM with input"]] method (and a single ''defaultFilter'') to create a new **Conversation** class that handles the branching dialog shown in this diagram: {{public:t-vien-08-1:conversation_states.png|}}\\ The diagram shows the state names in the blue boxes and the text that should shown on the screen when entering each state. The user picks response '1' by pressing the '1' key on the keyboard, which then takes the conversation to the state connected by the arrow labeled '1'. Same for '2'. The simplest way to do this, is to have the new class (that inherits from FSM.FSM) accept '1' and '2' as keyboard events, which are handled by the same handler method that directly calls the ''self.request(<input>)'' method for advancing to the next state. |
| |
| |
