3Ddesign&animation: REPORT P1

REPORT PROJECT 1

INTRODUCTION

For the last two weeks we have been working on a huge assignment. This was related to a robot and it’s environment. We teamed up two and two, where one person took care of the environment and the other the robot. This is yet the biggest and most difficult task so far.

INTERPRETATION OF THE TASK

Before we could start on this assignment, we had to team up with another student, or you could do the assignment by your own, without doing the environment. I teamed up with John Erlend Yttervik, which is a fantastic person to work with, in any cases. We had to give our team a name, and came up with ‘’team Bonecrusher’’. We started to read the assignment notes for this two-week assignment, and how we wanted it to be.

CONCEPT

For this assignment, there is basically two concepts to explain, but since I was focusing on the robot, I’m also going to focus on my task in the report. When we started with the design tryouts, I was pretty clear on what I wanted. Something massive, iron, rusty and huge. I came up with the main design and concept art for the model, and started to work on it in Maya. The design and story around the robot, is based on the well known fight between David and Goliath, were Goilath lost. The whole point with this concept, is to show the people out there that he’s back, and want revenge. The important thing with this assignment, is to picture yourself this scene in a world were robots is blending with humans every single day. The work, driving cars, and does things a normal human would do. Goliath is special, and have been stored in a old hangar for decades, because of his powers and strength. When this Goliath series was produced in the late 60’s, they were produced in only 90 examples, before something unknown shut the production down. This is, as far as we know, the only remaining Goliath example that is still alive on planet earth. After an inspection, it’s clear that this is the famous G.O.L.I.A.T.H B-23, which is the only robot who survived the attack on the production line in the 60’s. Goliath is about 15 metres tall and have extremely powers when it comes to his arms. His muscles is driven by small nuclear reactors, but is not affecting humans as we think of Tsjernobyl. After a long life in the hangar, he want’s to get out. He will find, and destroy what destroyed the rest of his family, and with no exeptions.

ACHIEVED ACTION

With my final project, I will convey that humans have to take care of what’s out there, no matter what it is. If they’re angry, then find out why. Robots are underestimated products that is a huge resource for our planet. If we build them right.

SCHEDULE

WEEK 1

MONDAY; Started on the assignment. Desgin and concept art.

TUESDAY; Desgin and concept art.

WEDNESDAY; Desgin and concept art.

THURSDAY; Modeling in Maya. Taking important notes in the process.

FRIDAY; Modeling in Maya. Taking important notes in the process.

WEEK 2

MONDAY; Modeling in Maya – Last touch. Starting with Checkers/Unwrapping

TUESDAY; Checkers/Unwrapping. Collecting textures and tryouts.

WEDNESDAY; Checkers/Unwrapping. Collecting textures and tryouts.

THURSDAY; Texturing. Making own textures for the finished robot. Doing the FP files.

FRIDAY; Compositing. Report.

RESEARCH AND WORK PROCESS

CREATIVE METHODS

When I started on this assignment, I had to work after my design drawings. I choosed to not use the drawings in maya as imageplanes, because it was a little bit difficult with all the panels that this product is made of. I used my favourite method on the chest of the robot, which is to start with one poly plane, and extrude the edges in the shape you want the object to have. This is a hard surface modeling assignment, so I used as few edgeloops as possible, because of all the tiny pieces that comes out of using it too much.

INSPIRATION METHODS

When I found inspiration for this assignment, I choosed to look for something in the Transformers category. To make a transformers robot is way too complicated. I choosed to take the idea using panels, to give the impression of a huge and strong machine.

ANALYSIS

The issues I had to work with this two weeks, was to make a low-poly robot, which had the right design and shapes compared to the main design. Overall we had a lot of problems with both the robot and the environment, such as crashes every minute, render engines failed to read the file, colors and textures suddenly disappeared. The task itself is ok, but when it comes to the texturing and rendering, it might trigger a lot of problems, which also takes a lot of effort to fix.

DESIGN

TOPOLOGY/EDGE-FLOW/POLY-COUNT

The topology and edge flow in this assignment is rather important compared to previously assignments. To save the computer for a lot of memory use, and a lot of time in the modeling part, it is a good solution to use polyplane extrude.

COLOURS

For this assignment, I used a rusty texture all over the whole robot, except the arms and leg itself. All the panels should have a rusty look, so they have the all over rusty texture.

COMPOSITION, LAYOUT

For this assignment, we had to do the same thing as in C1, to make the finished product.

We rendered out the passes we needed for this task, and then put it into nuke to tweake on the lights and other things that had to be adjusted.

SELF- EVALUATION

REFLECTION ON FINAL PRODUCT

My opinion with the final product is that this was a assignment with many different issues and problemsolving. I think we arranged the weeks as best as we could, to get the right use of time on each part. In the end of this assignment, there was a lot of problems, which forced us to stay up all night from Thursday to Friday, to get the project finished. I think both the environment and the robot matches the designs we agreed in the beginning of the first week, so overall I think this was a huge experience to take with me further into the 3D business.

CONCLUSION

By doing this weekly assignment, I have learned a lot about modeling, especially hard surface modeling. I have learned a lot when it comes to working in teams, which I thought was a great thing to do with this task.