{"id":75,"date":"2019-02-06T15:44:58","date_gmt":"2019-02-06T15:44:58","guid":{"rendered":"https:\/\/projects-old.etc.cmu.edu\/artales\/?page_id=75"},"modified":"2019-02-14T21:48:54","modified_gmt":"2019-02-14T21:48:54","slug":"week-3","status":"publish","type":"page","link":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/week-3\/","title":{"rendered":"Week 3, Getting Somewhere…"},"content":{"rendered":"\n

Since we had effectively\neliminated Meta 2 and HoloLens from our consideration the previous week, we\nneeded to make sure that we as a team could actually develop for the Magic Leap\nand AR Kit. We wanted to experiment with some of the AR Kit possibilities with environment\nmapping and gestures, however it so happened that the Developer Portal was down\nthis week, so we were unable to get accounts. This put mobile AR on a temporary\nhold as a viable platform and testing.<\/p>\n\n\n\n

This meant that we had to figure\nout the Magic Leap. This is the first time the platform was made available to\nETC projects, so none of our fellow colleagues have ever developed for it.\nBeing a very new platform, this meant that this held true for the outside world\nas well. There was very limited documentation outside of Magic Leap regarding\ncommon practices, pitfalls, tips and tricks, and suggestions. In addition, due\nto the rapid development of the firmware, many of the questions that were found\non forums were either already outdated, not yet answered, or were the focus of\na follow-up firmware release. This was most definitely worrying, as we were\neffectively a very small 4 person team on our own. Needless to say, our\nprogrammers braved on and attempted to create a series of \u201cGold Spike\u201d builds\nto prove to the team that developing for the platform was something feasible.\nAnd so, after hours of tinkering, we come to this picture of the first\nsuccessful build compiling and running on the Magic Leap hardware. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

It might not have been much, just\na floating cube that rotates based on hand position and gestures, but it gave\nus a huge boost of confidence. Our instructors urged us to make a decision\nabout platform as soon as possible, so since we couldn\u2019t afford to wait for the\niOS developer portal to be online, we ultimately decided upon the Magic Leap to\nbe our final platform.<\/p>\n\n\n\n

In addition this week was also key\nin constructing our team design language. ETC requires each project team to\nhave a logo and a team poster. We liked the vector art style, so we came up\nwith a stylized book pages logo, and an accompanying poster in a similar vein.  <\/p>\n\n\n\n

Finally, we really needed to get rolling on the story front. We are working with a CMU School of Drama student, Kate Busatto who is helping us formulate a story and write the script. Since we no longer were in a loop of choosing platform first then story, or choosing story first then platform, we finally were able to discuss story and purpose ideas with Kate in the context of headset AR. Following the thoughts of our instructors, we ended up with the following main guiding principle:<\/p>\n\n\n\n

AR exists as the intersection between the virtual, created world, and\nthe familiar space and items of the guest\u2019s real world. The interaction between\nthe two is what makes the experience magical and compelling.<\/em><\/p>\n\n\n\n

This is what we believe to be what\nseparates VR from AR, and what we will need to capitalize as we work forward in\nstyle and story. Due to a number of snow days that cancelled class and made\ntravel hazardous, we had a fruitful Skype conversation discussing these ideas\nwith our team and our writer to come up with some general higher level story\nideas. <\/p>\n\n\n\n

A question and concern that\nfrequently came up was where the threshold of \u201cgame\u201d was. We wanted meaningful interactions\nwithin our story ideas, however the threat of those interactions turning our\nexperience into a game was always on our mind.<\/p>\n\n\n\n

This was a question that we wanted\nto have some clarity on from our instructors moving onto week 4.<\/p>\n","protected":false},"excerpt":{"rendered":"

Since we had effectively eliminated Meta 2 and HoloLens from our consideration the previous week, we needed to make sure…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-75","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/pages\/75"}],"collection":[{"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/comments?post=75"}],"version-history":[{"count":5,"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/pages\/75\/revisions"}],"predecessor-version":[{"id":164,"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/pages\/75\/revisions\/164"}],"wp:attachment":[{"href":"https:\/\/projects-old.etc.cmu.edu\/artales\/index.php\/wp-json\/wp\/v2\/media?parent=75"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}