Level Layout Design

By Space Toothpaste

Ben (Technical Lead)
Chandra (Creative Lead)
Cynthia (Artist)
Douglas (Layout Designer)
Mateo (Systems Designer)

Following Tuesday's meeting, we have discussed further details that will entail in Falling Apart. This meeting was mainly to communicate our ways of adding to the design brief of the game and starting on our first steps. 

We decided on the floor plan and its placement of physical components with consideration for possible VR locomotions we could use for the game. 


Level Layout Design

The level layout design will include one main pentagonal chamber and four sub-chambers connected by three protruding tunnels. There will be placements of various windows and machines/systems laid upon the cells. The main chamber will accommodate the main computer system. The three sub-chambers will contain respectively the systems for life support, lights control and power generations. 

Systems Key Descriptions

Main Computer collates all errors into one place and regulates all systems.

Life Support has the components:

  • Oxygen Generator (creates oxygen and pumps it into the atmosphere).
  • CO2 scrubber (uses a filter to scrub CO2 out of the atmosphere).
  • Pressurizer (uses nitrogen pumped into the atmosphere to keep the base at or near an acceptable pressure).

Power Generators has the components:
  • Solar Panels (stores energy powered by the sun in large batteries).
  • Battery Charger (used to charge batteries such as those in the life support systems).
Lights Control has the components:

- Main Lights (bright)
  • Power Connector
  • Fuse
  • Screen
  • Warning Light/Buzzer
- Backup Lights (dim)
  • Power Connector
  • Battery
  • Screen
  • Warning Light/Buzzer

Dimensions

The dimensions for the space will consist of 2.5 to 3 metres at its widest for the chambers and for the tunnel 1.2 at the thinnest width.

We will continue to develop our design brief in the following days to fit the standards of prototyping expected for this project.





Level Layout Design Mapped By Douglas Wang (Team Layout Designer).
Game/Systems Design and Descriptions By Ben Elwood (Technical Lead).
Blog By Chandra Hu.


Comments

Post a Comment

Popular posts from this blog

Forming Group 'Space Toothpaste'

Image
  Falling Apart By Space Toothpaste Ben ( Technical Lead ) Chandra ( Creative Lead ) Cynthia ( Artist ) Douglas ( Layout Designer ) Mateo ( Systems Designer ) During the workshop on Friday, 19th March 2021, everyone from our class presented their concept pitch for software development ideas (one person - one pitch). After that, we formed groups in terms of what projects we were interested in. We're doing Ben's software development idea, which is called 'Falling Apart'. We agreed on having the group name 'Space Toothpaste' (created by Douglas).  Due to our other paper's assignment, we didn't get to have a thorough meeting discussing exactly what our first steps are. On Friday, 26th March, we decided to hold a meeting on the following Tuesday to discuss the design brief and our roles in the project.  Ben has created a Blogger, Gmail, Jira and Confluence account for this project.  Above is a screenshot of part of the Gannt-Chart Ben had created on Jira. 
Read more

Mission Control Manual

Image
  By Space Toothpaste Ben ( Technical Lead ) Chandra ( Creative Lead ) Cynthia ( Artist ) Douglas ( Layout Designer ) Mateo ( Systems Designer ) This week, we improved on our Mission Control Manual. The Mission Control Manual helps the player know how the components look and where they are in the systems.  Below are some photos of how our Mission Control Manual looks like currently.  Cover Page Level Layout Design & Life Support System Light System & Power Generator System Appendix
Read more

Programming

By Space Toothpaste Ben ( Technical Lead ) Chandra ( Creative Lead ) Cynthia ( Artist ) Douglas ( Layout Designer ) Mateo ( Systems Designer ) From starting this project I (Ben Elwood) wanted to make the components and systems easy to expand. This meant using polymorphism to assist with the coding of new systems or components. I started with the components. A general component has: A Type (What is it?) A Repair Cost (How long does it take to repair) A boolean to store if it is broken or not A function to damage the component (Some components may not just break if damaged) The first component that differed from that was the battery component. The battery component has, in addition to the general component things, a charge (The amount of charge remaining in the battery) and also functions to allow you to consume or recharge that charge. I did the same with systems. A general system has: A list of components that it needs to work A list that stores all the components currently connected A
Read more