Differences

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

--- public:t-vien-14-1:lab_4_materials [2014/02/05 10:53] – [Procedure] hannes
+++ public:t-vien-14-1:lab_4_materials [2024/04/29 13:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Lab 3: Indoor Environment ======
+====== Lab 4: Indoor Environment ======
 {{:public:t-vien-14-1:lab4-indoor.png?400|}}
@@ Line 5: / Line 5: @@
 ===== Goal =====
-The goal of this lab is to create an interactive indoor environment, with some puzzle logic implemented in C#.
+The goal of this lab is to create an interactive indoor environment, with simple puzzle logic implemented in C#. The puzzle works in the following way: The player/user has to configure a set of switches into a secret pattern to unlock and open a door to get out.
 ===== Preparation =====
-  * You should retrieve the scripts that were demoed in class. They are all available here: [[http://ru.is/~hannes/classes/ve2014/VIEN-ScriptsDemo4.zip|VIEN-ScriptsDemo4.zip]]. Note that they won't run in your project (unless the rest of the project happens to be exactly the same), but you should be able to adapt the code to your purposes in this lab.
+  * You should retrieve the scripts that were demoed in class. They are all available here: [[http://ru.is/~hannes/classes/ve2014/VIEN-ScriptsDemo4.zip|VIEN-ScriptsDemo4.zip]]. Note that they won't run in your project (unless the rest of the project happens to be exactly the same), but you should be able to adapt the code to your purposes in this lab. If you want to retrieve the full project where these scripts were taken from, you are also welcome to download it from here (but this is not required for the lab): [[https://dl.dropboxusercontent.com/u/73101/VIEN-Demos.zip|VIEN-Demos-.zip]] (700 MB!).
   * You should import "Robot Lab" from the asset store if you haven't already. It contains some nice prefabs and materials (e.g. for walls and floors) that you may want to use.
@@ Line 21: / Line 21: @@
     - You can use **Plane**s for floors and ceilings, and **Quad**s for your walls (2-3 meters is a good height for walls).
     - Both planes and quads are single-sided (there is no thickness to them and the polygons that they are made from have one front facing side)
-    - Use the ''Transform'' component of your building blocks directly to type in exact values for ''Position'', ''Rotation'' and ''Scale'. That way you ensure things line up.
+    - Use the ''Transform'' component of your building blocks directly to type in exact values for ''Position'', ''Rotation'' and ''Scale''. That way you ensure things line up.
     - Use **Ctrl-D** to duplicate a **GameObject** (e.g. a wall segment).
     - Hold down **Ctrl** to manipulate objects in a **snap-to-grid** mode.
@@ Line 28: / Line 28: @@
   - **Door(s)** Identify one or more wall panels as doors. Give them a different visual appearance and name them uniquely (e.g. ''Door1'').
   - **Scene Hierarchy** You may notice that your **Hierarchy** panel will quickly fill up with rather static game objects, such as walls. It is a good idea to gather such static scenery objects under new parents in the hierarchy. This allows us to quickly reposition them together as a single object, and also reduces the clutter. Create a new parent object through **GameObject->Create Empty** and then drag and drop all your walls, floor and ceilings (you can multi-select by holding CTRL or SHIFT) onto that new parent. Rename the parent as something that describes the group, e.g. ''Room''.
-  - **Puzzle Objects** Add
+  - **Puzzle Object and Puzzle Pieces** In this environment the player will **not** be collecting objects and therefore will not need an inventory. Instead, you should implement a new **Puzzle** game object (it can sit at the top of the hierarchy, created as an **Empty** object) that contains a puzzle behavior (script). Then, in the same way you created pickable objects in the past, create three **Puzzle Piece** objects around the environment that have the following behavior: (1) They are either in an On or Off state - this should be visible somehow (e.g. color, rotation, effect); (2) When the player collides with the object, the state toggles;
-  - **Door Opening Mechanism**
+  - **Door Opening Mechanism** Attach a movement behavior to the door(s). You can use the **Slide** script (from the source files distributed above). Remember that you have to assign a couple of transforms to the ''Start Marker'' and ''End Marker'' public variables for this script to work. You can do that by creating a couple of empty game objects, marking those locations, and then dragging those objects into the coresponding variable slots in the sliding script component. You can make some of your doors simply open when the player collides with them, but pick at least one door that is locked (and can only be opened by solving the puzzle, see below).
-  - **Puzzle Logic**
+  - **Puzzle Logic** As you toggle different puzzle pieces around the environment, the puzzle object should update its own ''solved'' state. Initially this state should be ''false'', but when a certain combination of On/Off states in the puzzle pieces occurs (you pick the pattern), the puzzle object should switch ''solved'' to ''true'' **AND open one or all of the doors**. You have complete freedom in how you implement this, but keep the following in mind:
+    - If your script needs to access other game objects, you can find any game object by name and assign it to a variable like this: ''go = GameObject.Find ("Door");'' - but only do this once in your script (in the ''Startup'' method), since this is costly.
+    - If your script needs to access a specific component (e.g. another script or property) in another game object, you can request a compoenent by type like this: ''inventory = GameObject.Find ("Player").GetComponent<Inventory> ();''
+    - It would be best to have the entire puzzle logic inside the puzzle object itself (the puzzle pieces don't even have to know they are part of a puzzle). For example, the puzzle object could posess references to each of the toggling objects and check for their state in each update, comparing them to the solution.
+  - **OPTIONAL: Provide hints** To be fair to the person trying to get out of your environment, you can leave visual cues to what the correct solution is. Use youre imagination.
+  - **OPTIONAL: Flashlight** Attach a spot light source to your camera for an additional "spooky" effect.
+  - **OPTIONAL: Outdoor Environment** What's on the other side of the final door?