Skip to main content

Adding the Models and Socket.io

This week involved touching on a few different systems to fine tune existing modules as well as create new modules.  Two components that had the most focus were replacing the primitive models with the GLTF models Max created (~8-10 hours), and separating the living-room and warehouse into two separate HTML files as well implementing Socket.io to allow player game-mode selection (~4-5 hours). The rest of my time was spent on smaller functionality like player speed tweaks and consolidating a-mixins for the for their data to be move to the object JSON file (~2 hours)
https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiWbOzK0jaA6visJrl1eMlWexGo9_sXEfVXRq-MJq7oFLQAN2uS9SUfqsDVkjYKxb9AZtGsbt3jkSSuAYtvV9GV1sF8TDyjrK0Wb_9a0XUagH5gU5Z2EGpI2CUJHQW62cFXxqBD3_N5s6k/s1600/Alpha_Example.png
Alpha Table
Beta Table

Replacing the primitive chair pieces with their models proved to be far more difficult than anticipated, as usual.  The process should have just involved replacing the 'geometry' with the 'gltf-model' component and then adjusting the aframe-physics 'shape' components to create bounding boxes that fit the models, but there were some unexpected side effects.  First, since the shape component relies on 'half-extents' to create the bounding box, we needed to find the dimensions of each model in Maya and them to dimensions in Aframe.  The second issue I faced involved strange behaviours that the models exhibited when interacting with the physics system.  All the table legs behaved like they had very low centres of gravity and they could not be knocked over, but the table top was totally fine.  I eventually narrowed the issue down to the fact that the table leg model was not properly zeroed, so Max exported a new version for me.  Another issue with the models was that they were much more difficult to pick up and they oscillated when picked up and moved quickly.  This seems to have been mostly fixed by increasing the scale of the models, though it still occurs if the user quickly rotates the view while holding an object, so is something I am still working on.

Since we have two different environments that offer different gameplay I needed to separate the warehouse and living-room into two HTML files and then create a nexus room that allows players to select and navigate to either room. This meant I also had to recreate an normal HTML navigation link as an Aframe component.  As it turned out, this was quite simple:

AFRAME.registerComponent('navigate',
{
    schema: {
        url: { default: '' }
    },

    init: function ()
    {
        var data = this.data;
        var el = this.el;

        el.addEventListener('click', function ()
        {
            window.location.href = data.url;
        });
    }
});        

The next few days will be spent implementing the game system that will co-ordinate the two players as they construct the furniture. 

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

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