![\"\"](\"https:\/\/lh5.googleusercontent.com\/PCj3ojWtkrp_s0mWvLAp_lqwZef4MDJpep-ztBY-8ducxHN3oBtj-0FptYRA1YFuxrKt4JvOnRRY6SPGKP3kxYDFEKkOfsO-fPDa2j2ZQmLMKTJ5se27spuHoe8um5ltvlFfcz8x\")
<\/figure><\/div>\n\n\n\nFor example, this slide is about Spot\u2019s constraints and the covid restriction we\u2019re facing. We have pictures of Spot and CMU and an icon here. Then we have the script like this: \u201cAt the same time, there are some constraints and challenges that we should consider. Spot has obstacle avoidance ability and it makes object collisions difficult, which means Spot can\u2019t pick up stuff, and it can\u2019t fetch like a dog. And it\u2019s a robot so it’s not safe for people to just physically interact with Spot like petting a dog. Spot can\u2019t detect obstacles in a dark environment, so we should avoid darkness in our design in most cases.\u00a0Also during this covid situation, we have limited access to the project room but at least one person needs to be there to safely operate Spot.\u00a0We won\u2019t have access to the ETC after Thanksgiving, due to CMU remote instruction policy so the experience we\u2019re making should be replicable or at least testable in our home if we bring Spots home. \u201c<\/p>\n\n\n\n
Also we responded to Carl\u2019s feedback, we made our slides more consistent and visually organized. <\/p>\n\n\n\n
On Tuesday, we finally had our formal presentation. Although we weren\u2019t able to see the audience’s reaction directly through Zoom, we believed that they liked our videos, concise slides, and honest playtesting results. We also answered the faculty\u2019s questions well. One of the questions was what\u2019s the overall story\/game here? We expected this question and prepared our answer ahead as we didn\u2019t show a background story in our presentation and we did mention that our client needs a whole experience rather than separate experiences. We answered: \u201cWe have talked to our client about this, and our client said it\u2019s okay to loosely tight those smaller experiences together. Based on current prototypes, we already have 2 ideas, but the final experience will depend on what smaller experiences are. 1st idea is that the game’s mission is to fix a spaceship in space. 2nd idea is that a training dog game.\u201d<\/p>\n\n\n\n
Although we spent lots of time preparing the presentation, we made progress on the project as well. We shared the \u201cSpace rescue\u201d story with our client and our client liked it. <\/p>\n\n\n\n We also playtested the Spot dance mechanism. We tried different key mapping <\/p>\n\n\n\n or <\/p>\n\n\n\n and the goal here is to let playtesters using the keyboard to control Spot to match the bits of a song. We were interested to know how they felt about this different key mapping and whether it\u2019s fun to hit the bits. <\/p>\n\n\n\n Playtesters indicated that no matter which keyboard mapping was, it\u2019s hard to tell when it\u2019s the end of a move and then got confused about whether they hit the bits or not We figured that this was because of lack of feedback. In most rhythm games, there were lots of visual feedback\/signals to indicate when are the bits, hitting or missing. However, this is quite challenging since we\u2019ve decided not to use computer interaction to cause distraction. Another thing that playtesters pointed out was that although it\u2019s good to watch Spot dancing with the music, it\u2019s not that fun to constantly pressing keyboards at the same speed. From this, we knew that we might need to change to a song in which rhythm varies if we go this direction.<\/p>\n\n\n\n We then need to discussed with our client whether to make Spot dance more like a gamy experience or a rewarding experience. After discussion, we agreed that it\u2019s more doable to make it a rewarding experience.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/lh3.googleusercontent.com\/cnAGdEfZHlQ7c2w_DfA3iHCALlOMeSK_xtWetOeGUeHJoFEFwFRr0SSlcmZRj92zxadQrXjNMBA7W3uVSTI0V4_laOuuxbw6IMKaF1FZwLbQvb_KHOq19fIs_QI5V6gdQnp4HLx5\")