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

Controllers and Game-state Management

The two issues I worked on this past week were getting game-pad controllers working with our project (~6 hours), and general work on the game-state systems to iron out some of the kinks and add some more functionality (~3-4 hours).  Unfortunately neither of these tasks proved 100% successful due to some set backs. The game-pad controllers are so close to working, movement and look controls are fully functional, but I cannot get the Super Hands components to pick up the button events from aframe-extras.  The easiest way to see this is by looking at some code: <!-- Camera --> <a -entity id= "rig" movement-controls position= "0 0 0" > <a -entity id= "camera" camera wasd-controls= "acceleration: 125" look-controls= "pointerLockEnabled:true" position= "0 1.6 0" capture-mouse st...

Storyboard and Physical Layout

I finished up on some graphical elements for the user interaction specification component of the proposal due this coming Friday. This includes the storyboard panels and the physical layout diagram. As I was researching Oculus Rift physical setups, I had to determine how many sensors we would need for our game. I believe that 2 sensors will be sufficient, since we do not need a true 360 degrees experience as the Builder player will primarily be focused on the 180 degree space in front of them (i.e. the fireplace, the TV, and building the furniture). Our game is not an action packed game with any running or shooting. Of course, the player will still be able to fully look around but they shouldn't have a great need to move in the other 180 degrees of space. This would also take into consideration accessibility to our game, because it costs extra to buy a third sensor (the Rift only comes with 2) as well as requiring adapters and wire extensions. I spent about 4 hours researching ...