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

[WEEK 1] Introducing our project...

Our goal is to make a cool VR game for Design Studio 3. The main idea involves a collaborative asymmetrical experience to build furniture virtually. There will be two roles in this game: a finder (to look for furniture pieces in the warehouse), and a builder (putting the parts together). We started this project on January 22, 2020 and are currently on our first 1 week sprint of development.

Sprint 10 - Adding more boxes and lots of scripting

As the final submission draws near, lots of work has yet to be done. Due to time constraints and the lack of resources in light of recent events, we made the decision to cut down our scope by removing VR functionality entirely and focus on desktop-to-desktop connection fully. With new goals in mind, I spent the beginning of the week by adding all the boxes for spawning furniture components. To do so, I started by replacing the blue boxes we used previously with stylised boxes that match the environment better. To tell the player what each box contains, an image of the rendered component is placed on each side. The challenge here was that I wanted to avoid creating a GLTF for every single box because it would have slowed down the page drastically. The solution was to instead use a single, universal GLTF for every box and placed images on each side of the box as explained previously (~6hrs). New Warehouse Area - Added new boxes Close up of updated box - Bright colours and side

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