Skip to main content

Moodboards and Sound Compression

This week I worked on creating moodboards (~5hrs) for the Living Room environment because the current look left a lot to be desired. I find it helpful to follow a colour scheme when decorating a room in real life, so that is what I basically made before also showing how the colours could look like over top a render of the Living Room model.

For our game, we would like to have a bright living room that has some pops of colour for interest. A similar style will also be used for the furniture.

Below are some of the resulting ideas I had:






Out of the new coloured room options, the group preferred the 1st one and the 4th one the best. In the near future, after Maxime finalizes the Living Room environment model, I will be updating the materials.

I also created a moodboard for the Warehouse environment as well (~1hr, see image below). This required a bit of research on warehouses, which I did in a previous sprint. I noticed that common colours in warehouses were grey, orange/yellow, and blue.


This was an interesting article I read about painting warehouses:
https://specialtycoatingspainting.com/key-to-optimum-warehouse-performance.html

I also worked on reducing all the sound files (~2hrs) because when I tried to add them to the A-frame project, they took a while to load. They are now all OGG files of reduced quality and some files have been trimmed. However, the team is also considering adding a loading screen of sorts since we will have even more files to load once the furniture models and the Warehouse model are also imported. This would make it so that players will both wait on a nice screen rather than the blue A-frame default. 

I placed the Living Room OGG as a source for a sound emitter into a ceiling plane with a transparent material. The sound can be heard only once the file has completely loaded and is a consistent volume across the scene.

I am currently in the progress of separating the Warehouse environment and its related assets and functions into a different HTML file to keep the two environments separate. This should take about 2hrs or so, considering I would also need to move the camera to its starting position and place the sound sources for the Warehouse environment in appropriate locations. I will also be adding the lights to this scene.

Comments

Popular posts from this blog

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 = ...

[WEEK 6] Back from Reading Week

We got back from Reading Week and reviewed what each of us accomplished. Expected deliverables for this week include: moodboards for the Living Room and the Warehouse, basic recolouring for the Living Room, a completed final Warehouse environment, and a working spawning objects prototype.

JavaScript Libraries and Flow Charts

This sprint we focused on the laying the groundwork for the project and writing the design document.   For the design document, I outlined the Technical Requirements, Technical Features, Interaction Features, and created a user experience flow chart (~4-5 hours).   The rest of the sprint was spent testing the JavaScript packages we plan to, or are interested in, implementing in the project (~4-6 hours).    Creating the user experience flow chart took a few iterations as we weren’t certain of the final gameplay.   The current version is fairly linear, but the gameplay is straight forward to make it easy to pick up and play.    A part of the final user experience flow chart. The packages I tested for our project were aframe-extras , aframe-physics , and aframe-click-drag-component .   ‘Extras’, as the name suggests, adds some extra functionality to A-Frame, including controller support, ‘Physics’ adds a physics system, while ‘C...