{"id":310,"date":"2019-02-26T02:12:38","date_gmt":"2019-02-26T02:12:38","guid":{"rendered":"https:\/\/projects-old.etc.cmu.edu\/hot-metal\/?p=310"},"modified":"2019-03-26T00:05:28","modified_gmt":"2019-03-26T00:05:28","slug":"week-6-dev-blog","status":"publish","type":"post","link":"https:\/\/projects-old.etc.cmu.edu\/hot-metal\/index.php\/2019\/02\/26\/week-6-dev-blog\/","title":{"rendered":"Week 6 Dev Blog"},"content":{"rendered":"\n

On Week 6, we continuously work on the linear VR experience. Here are some screenshots for our latest progress:<\/p>\n\n\n\n

\"\"
Step Controller for level management
<\/figcaption><\/figure><\/div>\n\n\n\n

The above picture shows the steep controller we used for level management. We use a stepManager system as the bottom structure to manage the linear level system. We gave every step several parameters, and every step has events to be triggered when the step starts and ends. When a step is created, we also gave them step events for ending and start, and also store each step and their following steps in two dictionaries. Then we leave the AddStep Interface for .json file to store and add levels. For every step, we need a structured method calling the step ID of every single step. Then, we search in .json file for glowing objects and outline objects and use specific functions to provide visual feedback. In the .json file, we store objects with names and split with the comma. Therefore, In Set step function we formalized strings and find objects in the scene through their name and call relative methods. Then we leave interface for both moving to the next step and also calling specific step. In most occasions, when the system receives the event that the guest has finished the current step, we call the function of moving to the next step. In some other occasions, we need the player to recall back to specific steps and looping in several steps until they finish the last requirement. In the loop, we need to call a specific step instead of moving to the next step. When calling the function, we pass the step index as the parameter.
We use a stepManager system as the bottom structure to manage the linear level system. We gave every step several parameters, and every step has events to be triggered when the step starts and ends. When a step is created, we also gave them step events for ending and start, and also store each step and their following steps in two dictionaries. Then we leave the AddStep Interface for .json file to store and add levels.<\/p>\n\n\n\n

\"\"
Interface of Setting the current step<\/figcaption><\/figure><\/div>\n\n\n\n

For every step, we need a structured method calling the step ID of every single step. Then, we search in .json file for glowing objects and outline objects and use specific functions to provide visual feedback. In the .json file, we store objects with names and split with the comma. Therefore, In Set step function we formalized strings and find objects in the scene through their name and call relative methods.<\/p>\n\n\n\n

\"\"
Set step function implementation<\/figcaption><\/figure><\/div>\n\n\n\n

Then we leave interface for both moving to the next step and also calling specific step. In most occasions, when the system receives the event that the guest has finished the current step, we call the function of moving to the next step. In some other occasions, we need the player to recall back to specific steps and looping in several steps until they finish the last requirement. In the loop, we need to call a specific step instead of moving to the next step. When calling the function, we pass the step index as the parameter.<\/p>\n\n\n\n