This project lasted around 3 months and started out very bumpy. There were a lot of disagreements between students and tutors, and misinformation surrounding this project and how groups were initially chosen, and not open to adjustments. The result of this made it very difficult for students to start this project with optimism. It personally made me very wary of this project and I considered requesting to work on my own for this project. Unfortunately it also made it very difficult to go to tutors for advice related to this project. I feel like my group was disadvantaged greatly with the lack of tutor feedback meetings as we definitely needed support throughout this 3 month project.
My team mates, as lovely as they are weren't at all balanced in areas of expertise. We had three 3D environment artists and three character artists, with secondary skills in prop creation, 3D modelling and texturing. But we had no one who was dedicated to concept art, UI or engine work three massive parts of the project. I believe none of us had worked together beforehand as well, so the settling period for our group was long. To be honest we never really settled into roles, everyone just ended up doing a bit of everything to compensate for the gaps in our team composition. As individuals we all have a willingness to learn new skills and we're competent regardless, but it would have been nice to just be able to focus on what we specified that we wanted to improve for this project. I feel like we ended up missing out on the opportunity to specialise, to keep the balance in our team.
Project Contribution:
Project Contribution:
Concepts:
- Underground level
- Garden level
Characters:
• Bluebells- Full Process
• Foxgloves- Full Process
• Victorian Clock- Full Process
• “Eat me” Cake- Full process
• Pillar- Texturing (Albedo)
• Big Leaf- Unwrapping, Texturing (Albedo, Normal, Roughness)
• Books- Unwrapping, Texturing (Albedo, Normal, Roughness)
- The White Rabbit
• Bluebells- Full Process
• Foxgloves- Full Process
• Victorian Clock- Full Process
• “Eat me” Cake- Full process
• Pillar- Texturing (Albedo)
• Big Leaf- Unwrapping, Texturing (Albedo, Normal, Roughness)
• Books- Unwrapping, Texturing (Albedo, Normal, Roughness)
This is a quick summary of how my weeks looked throughout this project (recorded in more detail in previous blog posts.)
At the end of the project I came out with a hand full of assets, but my main contribution to the project was my White Rabbit Character
Post Mortem Q&A
This is a tricky question as I didn't have a clear idea of what I wanted for this project after my initial ideas. In the beginning I envisioned this project to be a simple platformer, with painted, stylised backgrounds and assets; with a focus on 2D skills (think Rayman legends with a little 3D thrown in there) with minimal mechanics. However none of this happened; the type of game I wanted was shot down fairly early in the process and I never replaced that with anything else as the direction we ended up going in was the complete opposite of what I had in mind.
Q. What stressed me out the most during this project?
At the end of the project I came out with a hand full of assets, but my main contribution to the project was my White Rabbit Character
 |
| Underground Assets |
 |
| Garden Assets |
 |
| White Rabbit Render |
 |
| Assets in game |
 |
| Assets in game |
 |
| White Rabbit in game |
Post Mortem Q&A
Q: Did my end result represent what I wanted for this project?
Q: Strengths I found during this project
As a group: Though we didn't get the level of polish we could
have for the project. I got to hand it to us, we produced a lot of work. 3
different populated levels that include 3 completely rigged characters with all
the concepts to back them is nothing to scoff at. We really powered through
this project despite the imbalances in the team composition and we helped each
other out when we could. Most of the team went about the project with a
constant level of optimism (which I found disconcerting at times, but encouraging none the less.)
Individually: I've found that I'm very quick and texturing individual assets,
having been able to complete several in an afternoon when previously I'd need a
least a day for each one. I've also become fast at rigging biped characters and
can test them in engine quickly.
Q:
Weaknesses I found during this project
As a group: Attendance was an issue through this project. Half
of the team were in every day at consistent times, whereas the other half came
in at more sporadic times, or not at all, without much of an explanation for
that. Because of this it was difficult to keep track of how everyone was doing,
if they were on track, needed help etc. I assumed that everyone was
working on what was discussed but that was not the case, on several
occasions a team-mate would add extra details, or work to their current jobs,
that weren't discussed, and looking back, really weren't needed to improve the
game, people got carried away with new features rather than finishing what they
already had. These problems tie in with the large issue of a lack of
communication. Though there were several means of communicating with each
other, the just were not used much by the majority of the team. I've learnt
that making communication easy doesn't guarantee that communication will
happen.
Individually: I did not assert myself enough throughout this
project. I found that having to work with completely new people stopped me
being able to be as critical as I normally would with those that I know. I
would voice concerns, but I stopped myself repeating them afterwards and as a
result my concerns were often forgotten in the end. The fear of being seem as
overly negative or annoying prevented me from following up on the problems. Now
I know to just go with it regardless, because the problems I mention won't just
go away.
Q. What stressed me out the most during this project?
Asset creation was a slow process all around, everyone was left to do their
own thing but there wasn’t enough overlap in peoples work. Assets were
concepted, modelled and textured by the same person, and if they didn't show
you their work, you wouldn't know what to expect. I personally shared
screenshots of my work throughout my process as did many member of the team, but there are few assets and bits
of work that I did not see until they were completed and put in the game. This
combined with a slow output in asset creation meant that some assets never had
the opportunity to be improved. There was no clear leadership or structure to
this project which caused problems and stress for me since I could never be
sure that everyone was on track with what they were doing. There was also a
sense of passiveness in the team everything just seemed "ok" but
there weren't many points in the project that got people fired up and really
enthusiastic about the project. Having a group of people was such varying
tastes and work practises contributed to that.
The want of individual ownership over parts of the project hindered how
well the group worked together. Though everyone in the group worked towards
finishing the project there was little to no collaboration between smaller
areas of work, instead work was produced in self-contained projects. This
practice I believe has come about from the urgency for portfolio pieces this
year; team mates (including myself) wanted to showcase their individual skills
to help them get hired after graduation. Which isn't a problem normally, but
can be terrible in group work. This links with my main issue during this
project; texturing. Not being allowed to texture many assets in this project
really stressed me out. Despite offering, and putting myself down for texturing
as a main skill, no one passed their assets to me for texturing until the very
end of the project. This was frustrating because for one it made me feel like I
wasn't trusted to do good work, and two, made me annoyed when texturing
was left to the last possible second. I saw several
assets that I could have textured early that didn't get
time put into them because people were busy with other aspects of the project,
but still wanted these assets for portfolios, so were unwilling to give them
up.
The scope of this project was just too much, the team does not lack
ambition, but needs to know when to stop. Despite being told several times
through this project to cut down the level I'd come back to look at how things
were going and see that though areas were cut, extra aspects were still
being added, without finishing other problem areas and really polishing the
level.
Conclusion:
This has been an exhausting project, and it's not even 100% finished yet, but I learnt a lot about myself and how I work. My biggest take away from this project is that I need to have more confidence in myself when it comes to pitching my skills and voicing my concerns in group projects. Finishing a project that I'm proud of takes priority of being seen as a negative team mate, if things aren't going the way which I think is beneficial, next time I'll just have to take charge of that situation, if I overstep hopefully someone will call me out and I can work on it. But I won't know until I try.
This has been an exhausting project, and it's not even 100% finished yet, but I learnt a lot about myself and how I work. My biggest take away from this project is that I need to have more confidence in myself when it comes to pitching my skills and voicing my concerns in group projects. Finishing a project that I'm proud of takes priority of being seen as a negative team mate, if things aren't going the way which I think is beneficial, next time I'll just have to take charge of that situation, if I overstep hopefully someone will call me out and I can work on it. But I won't know until I try.
