The team made great progress with mapping out and narrowing down the specifics of scripted case scenarios in the battle portion of the game. Programming included real time drop shadows and basic animations for the player\u2019s bot, which went a long way towards visually grounding the bot to the floor through the eyes of the user, and was well received. <\/span><\/p>\n As we add new features and refine\/balance the movement, control, and physics systems, playtesters spend more and more time with the iPad before they decide they\u2019re done with it. More than ever, I am seeing the real potential for us to make something great. <\/span><\/p>\n The most limiting constraint that we face is time\u2026 14 total weeks of development, six of which have past already. Moving forward and for next week, we will be challenged by scoping back our idea in a manner that retains its core identity and purpose. <\/span><\/p>\n <\/p>\n Programming:<\/b><\/p>\n This week we are still working on prototyping. For Wednesday, we made out a demo that uses the new version of control. We reduced the controller from 2 to 1 which allows us to put enough space to place attack UI. In the new control, we move and rotate bot in a more intuitive way. We let the bot to always move in the direction that player is facing. The reason why we made this is we found when player use the previous control they usually get lost if the camera’s facing direction is changed. This time we change the moving coordinate system from global to local so that your bot is always move in front of you. We let the EA visitors to try the two version and everyone who tried it out prefer the later one which means we are in the right track.<\/span> <\/p>\n Design:<\/b><\/p>\n As a team, we decided to focus on the \u201cRe-Design\u201d (Phase 2) part of our game to be playtested in week 6. <\/span><\/p>\n <\/p>\n The goal of this playtest was to figure out:<\/span><\/p>\n <\/p>\n As a part of our playtest, we presented players with 3 scenarios:<\/span><\/p>\n 2) How would you redesign the silver and red robot to deal damage more effectively?<\/span><\/p>\n 3) How would you change the two-wheeled robot so that you could recover after being flipped?<\/span><\/p>\n For each of these scenarios, we further asked them the following questions:<\/span><\/p>\n <\/p>\n This playtest was conducted in two separate ways, <\/span><\/p>\n <\/p>\n Our findings:<\/span><\/p>\n <\/p>\n Our next playtest will be based on scenario 3 (being immobilized). We will be presenting players with options that they can choose from to fix this problem. Each option will have a weight and a cost associated with it. <\/span><\/p>\n This playtest will help us in the following way:<\/span><\/p>\n <\/p>\n Art:<\/b><\/p>\n In this week, we finished the 3D models concept for our final project. We made two battlebots based on the shapes of two real famous battlebots in the show. <\/span><\/p>\n After the Art and Design meeting, we figured out our basic <\/span>restraint relationship among different weapons. For the art, we will start to build weapon components for the game such as hammer and flipper. So in the next week, we will start to make the models of several weapons. In addition, we will begin texturing some models by Substance. <\/span><\/p>\n \u00a0<\/span><\/p>\n UI\/UX Design:<\/b><\/p>\n In this week, we had our first formal playtest on \u2018Redesign\u2019 part which could help designers in the team to ideate more options of redesigning bots and also playtest the prototypes we made in last few weeks. We got lots of valuable input from people inside and outside ETC building. I collected the feedback of prototype playtest and delivered them to our programmer. For now, we were trying to solve the problems of control system.<\/span><\/p>\n <\/p>\n As a part a design work, we try to review the game design we had from last week and modify a little bit to fit with our time and resource constraints and client feedback. We also generate a idea about bot gallery at the end of the whole experience to satisfy our client requirements from last client meeting that we probably need to make manufacture get more involved into the whole process.<\/span><\/p>\n <\/p>\n I and Trisha has a clearer work division about design after faculty meeting in the middle. After the team deciding our basic flow, we will take responsibility for different parts work. I will take care of the design to user end and Trisha will take care of game level design.<\/span><\/p>\n <\/p>\n To help the team have a better understanding of our game flow, I made the wireframes of battle phase. I believe visual elements could help our team on the same page and also help to move forward. I\u2019m still in the process of experiments and comparison different layouts of battle phase with people\u2019s critique around me.<\/span><\/p>\n <\/p>\n \f<\/span><\/p>\n","protected":false},"excerpt":{"rendered":" Production: The team made great progress with mapping out and narrowing down the specifics of scripted case scenarios in the battle portion of the game. Programming included real time drop shadows and basic animations for the player\u2019s bot, which went a long way towards visually grounding the bot to the floor through the eyes … <\/p>\n
\n<\/span>On Friday, we have another updated version which includes the wheel animation and realtime shadow. The wheel animation is based on the real physics, if you turn right, the right wheel will rotate backward while the left one rotate forward. And the shadow enhance the feeling that the bot is in the real world.<\/span><\/p>\n\n
\n
![](\"https:\/\/media.giphy.com\/media\/xFoOLpyEN6QchyZEih\/giphy-downsized-large.gif\")
<\/p>\n![](\"https:\/\/media.giphy.com\/media\/g0vZVG9ZOFmcsuQpZ9\/giphy.gif\")
<\/p>\n![](\"https:\/\/media.giphy.com\/media\/ypbPwodZYM1RUIqVsW\/giphy-downsized-large.gif\")
<\/p>\n\n
\n
\n
\n
\n
\n
![\"\"](\"https:\/\/projects-old.etc.cmu.edu\/botlab\/wp-content\/uploads\/2018\/11\/unnamed-1-300x196.png\")
<\/p>\n![\"\"](\"https:\/\/projects-old.etc.cmu.edu\/botlab\/wp-content\/uploads\/2018\/11\/unnamed-300x171.png\")
<\/p>\n