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

Sprint 5 - Finishing the Furniture

This week, I completed modelling (4hrs) and texturing (7hrs) the furniture that will be used in the scene. It took longer than I expected because I had difficulty nailing down an art style while also working with new techniques in Substance Painter that I wasn't familiar with. A big challenge was finding a style that I really liked and understanding how to achieve that. My experience is more in realistic modelling and texturing where it's easy to see where things don't look right. However, with stylized pieces, it's up to my own interpretation. I'm also working with a very base, low-resolution mesh because I want to avoid creating too much detail through normal or height maps. The simpler, the better, but, the simpler, the less there is to work with. The grand solution in nailing down a flexible art style was through the use of ambient occlusion. By baking the same model over itself, I get an AO map, which already improves the look dramatically as it removes ...

[WEEK 3] Illustrations and Alpha Prototype

This week, we need to complete the user interaction specification document, which contains many graphical components that need to be created. This includes the storyboard/wireframes, design compositions, and the architectural flow of our game. Additionally, the Alpha prototype is due next Friday! This is a huge priority and at this point, we will be relying on Mitchell to work on coding majority of the functional elements. Primitive environments have been prepared by Maxime, but they need to be tested in a VR environment (i.e. for scale). Priscilla will be putting together all the parts of the proposal document and supporting both Mitchell and Maxime with their tasks.