Skip to main content

Sprint 6 - Redesigning and Finalizing the Warehouse

Based on feedback from the alpha build and some considerations from the rest of the team, I spent the week redesigning (~9hrs) the design of the warehouse and retexturing (~5hrs) it to fit the aesthetic of the furniture more.

Some of the changes made to the warehouse include the following. First off, the game will only support three pieces of furniture to build, therefore it was unnecessary to have five rows of scaffolding. This is also supported by our attempts to reduce the poly count as well as create more space between shelves. From the way players moved into the environment, it was clear that there was too little space between shelves to removes boxes, so this was reduced. There was also too much unnecessary space in the front of the warehouse, so everything was pushed forward more while cropping the back end a little to reduce the poly count further. The doors of the warehouse were also redesigned to add more interest in that section of the environment. (~4hrs)

Next, I UV mapped everything from the ground up. This was challenging at first because I tried to fit everything into a single texture set, which was a terrible idea. In order to save real estate on the UV maps, I separated everything by categories (boxes, walls, containers etc.) into their own texture sets. Some categories were eve cut down further as well. I also stacked a lot of the shells to provide as much working space as possible. (~5hrs)

Finally, texturing. This process went quite well because I had already developed a style I liked from when I built the furniture. This was still challenging, however, because I didn't want everything to look too similar to one another. Adding variation creates more interest so I needed to change this up a bit.

Top-Down View
Front Doors
Scaffolds

Comments

Popular posts from this blog

[FINAL] - Where to find our game

Hello future builders, we're 3 programmer-artists that make up the Seismic Octopus team: Mitchell Koch - lead programmer, game tester, researcher  Priscilla Lo - project manager, sound design, lead 2D artist, programmer, documentation  Maxime Vincent - lead 3D artist, lighting designer, game tester We finished this course in May 2020 with a final release of Build-a-Furniture available on GitHub: https://github.com/Areizza/Build-a-Furniture Although this semester was full of hardships and unprecedented times near the end, we got through it together and are proud to present our simple web-VR game. Check it out and let us know what you think! :)

Catalogue, Sound Effects, JSON for Instructions

This week I updated the image for the catalogue and added it to the Living Room environment as an image plane (~2hrs). I am currently adding smaller clickable planes on top of it to represent the different furniture options to choose to build. A screenshot of this can be seen below. I also looked for some sound effects to use for user feedback (~2hrs) when pieces are combined together correctly, incorrectly, pieces are dropped, etc. These sound files have been added to the shared drive and will be implemented in the code in the next few days. Some example sounds can be listened to at the following links: https://freesound.org/people/NenadSimic/sounds/150879/ https://freesound.org/people/grunz/sounds/109662/ https://freesound.org/people/GabrielAraujo/sounds/242501/ https://freesound.org/people/kirbydx/sounds/175409/  I also worked on adding JSON for the builder.js and finder.js files to store the required information for the instructions (~1hr). An example o...

Building the Shelf and Chairs

With the final submission looming closer, most of my effort was directed at replacing some hard-coded game-play functionality with dynamic data from the Builder and Finder systems (~3 hours), assisting my team with issues they encountered (~2-3 hours), and getting the shelf and chair ready to be built by the players (~8 hours). The Builder and Finder systems still had a few hard-coded values from the Beta build of the project that were specific to constructing the table, so I worked on replacing those with the data that is contained in the instructions arrays that Priscilla and Maxime created this week.  I was initially have problems accessing this array before I discovered that JavaScript arrays can be accessed by string, which simplified it a lot.  Below is an example of the before and after of this process. // Before socket . on ( 'setFurn' , function ( data ) { this . current = data . id ; // Where data.id was always "table" this . step = ...