Skip to main content

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

    // "tableTop" is the id for the first piece of the table.
    sceneEl.emit("setInstruct", { furn: this.current, piece: "tableTop" }); 
});

// After
socket.on('setFurn', function (data)
{
    // Get the instruction object for the specified id
    this.current = instructions[data.id]; 
    this.step = 0

    // Send the parts required out to the app.
    sceneEl.emit("setInstruct", instructions[this.step]) 
});

 In addition to this, I helped Priscilla and Max with some of the code they worked on.  The most notable was helping Max to add images to the snap-points by adding the image source to the templates array and reading it in through the 'spawner' component, which is something he discusses further in his blog.

Unfortunately a large chunk of my time was spent preparing the chair and shelf models for their placement into the game; far more than I anticipated.  Preparing the models for the Aframe environment involved manually creating the Aframe Physics bounding boxes and then manually placing each snap-point for every individual piece of the chair and shelf models.  Creating the bounding box for a piece involves finding the dimensions of the piece from the Maya file, and then translating these values into XYZ 'half-extends' that the physics system uses to create the bounding box.  Placing the snap-points then requires spawning all the pieces for a build, constructing the furniture in the Aframe Scene Inspector, then dragging a placeholder snap-point to the approximate positions that are required, and recording the position data in the template file. 
Although this was not challenging work, it was time-consuming and repetitive and it was slowed down occasionally when problems with the exported models or textures were discovered.

As we approach the final deadline the stress is mounting, but the worst is behind us, so all that is really left to do is hooking up the remaining systems, and implementing a player 'ready' system. 




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