{"id":392336,"date":"2024-06-29T10:21:32","date_gmt":"2024-06-29T10:21:32","guid":{"rendered":"http:\/\/savepearlharbor.com\/?p=392336"},"modified":"-0001-11-30T00:00:00","modified_gmt":"-0001-11-29T21:00:00","slug":"","status":"publish","type":"post","link":"https:\/\/savepearlharbor.com\/?p=392336","title":{"rendered":"A bit about our currently nameless game company, and what we\u2019re working on at the moment<\/span>"},"content":{"rendered":"
<\/div>\n
\n
\n
\n
\n

Hey everyone! I represent a game studio without a name, and the project we\u2019re working on goes by the technical name of «CGDrone». I started writing this article earlier today, having tortured myself for ages with sketches, colours, algorithms and correcting bugs in rotations based on quaternions (the last one just about finished me off). You can probably understand I needed a break.<\/p>\n

I\u2019ve often come across stories people have posted online about how they made their game, the difficulties they faced, and the result they achieved at the end. Likewise, our team has its own story, and I\u2019d like to share a bit about it.<\/p>\n

The beginning<\/h2>\n

It all started at uni, towards the end of my master\u2019s. Me and a coursemate from another group decided to make our own super cool 3D first-person puzzle game. Why did we decide to make a game? Well, I had some experience of drawing, specialised in art at school, and my teammate had experience of 3D modelling. And after all, we\u2019re both programmers, and we\u2019ve made games before whilst working in companies. Why a puzzle game? Because we like puzzles.\u00a0<\/p>\n

We divided all the various tasks roughly 50-50 between the two of us, or each one of us basically took on the tasks we could do. On the one hand, having two people on your team means each person gets half the workload! Quite nice really \ud83d\ude42 And overseeing your teammates\u2019 work doesn\u2019t take up as much time than if there were, say, 30 other people.<\/p>\n

So, basically, everything fell into place: I was to be responsible for all the code and the graphics (shaders, lighting, post processing effects), and my teammate for the levels, and legal issues. At the start his modelling was better than mine, but after a while I realised that constantly asking him to re-do some model or other was just hassling him and taking his focus away from the key tasks. Also, the requirements for a given model could change quite frequently and I didn\u2019t want to drive him mad by making him do 1000 corrections each day. So, I took on responsibility for modelling too.\u00a0<\/p>\n

At the very start we decided on an idea for the game, its laws and mechanics, tested everything out in our heads, on paper and on Unity, and planned out a networking mode.<\/p>\n

You won\u2019t believe it, but I\u2019ve now got two folders worth of sketches for the project, and sometimes I still have to sketch out pictures, go through different ideas and compare different objects. Here are some examples from the sketches I\u2019ve done:<\/p>\n

<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n

As it stands we\u2019ve already published most of our sketches on Twitter and Instagram\u2026\u00a0<\/p>\n

We also tried to get some of our acquaintances involved in the project. At one point we had two girls (designers\/artists), a game designer and another programmer on the team as well as us. After 2-3 weeks the programmer went to work in a big company, after attempting to create a structure for the project and build one game object — some random object with an \u201ceye\u201d which follows the player. Then the designers abandoned us. The game designer turned out to be made of stronger stuff though. He stayed with us till the last, although he didn\u2019t actually produce any concrete results \ud83d\ude42<\/p>\n

Btw, at that time the game looked like this:<\/p>\n

<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n

The models shown on the pictures are some of the first versions we did. I\u2019ve not posted these pictures to show the graphics or mechanics, but in order to show how everything looked at the stage when we were working on the mechanics and testing everything out.<\/p>\n

And a few more sketches:<\/p>\n

<\/figcaption><\/figure>\n
<\/figcaption><\/figure>\n

A little about a lot: Networking<\/h2>\n

Initially we wanted to build in a multiplayer mode, but as it turned out, it really wasn\u2019t worth it. I tried my best to make it work and clung onto it like a cat with a fish. We had built rooms, levels, and networking functions on the main objects. But all this was moving along so slowly, and our time was basically disappearing into a black hole with all the testing and debugging. Here\u2019s how our interface looked:<\/p>\n

<\/figcaption><\/figure>\n

We did a lot of work on the networking mode, even installed a web chat (the envelope icon) and a voice chat system (the microphone icon).<\/p>\n

Later on I realised one important thing: the multiplayer function was cool, but if you\u2019ve got two people on your team and neither have any experience with it (not counting the networking labs we did in uni), it\u2019s better to put the networking to one side and focus on the main aspects of the game:<\/p>\n

\n

A bird in the hand is worth two in the bush<\/p>\n<\/blockquote>\n

Attempting to expand our team<\/h2>\n

At some point I started trying to attract high-level artists to work on our project with us — but that didn\u2019t go anywhere. The reasons for that turned out to be quite obvious: <\/p>\n