Skip to main content

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 image


By the end of the week, I worked on two scripting events. The first was reworking the symbols on the components. Previously, the GLTF object has an emissive map with the symbols on them. The problem with this system is that the symbols come out very small. This is due to the face they're on are thin surfaces with little room to work with, or because the component that would snap over the symbol doesn't have much surface area and I wanted to avoid overlap. This was reworked to have the symbols attached to the snapping points themselves. This way, the symbols would be more obvious to the user and would disappear once snapped.


I also started the set up for scripting the order of operations of how instructions are updated in the warehouse. According to the script, only certain pieces can be sent from the furniture at once, and only a limited quantity of them so to avoid spamming. The instruction image will change once all the components are snapped correctly on the builder's side.

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

[WEEK 6] Back from Reading Week

We got back from Reading Week and reviewed what each of us accomplished. Expected deliverables for this week include: moodboards for the Living Room and the Warehouse, basic recolouring for the Living Room, a completed final Warehouse environment, and a working spawning objects prototype.

JavaScript Libraries and Flow Charts

This sprint we focused on the laying the groundwork for the project and writing the design document.   For the design document, I outlined the Technical Requirements, Technical Features, Interaction Features, and created a user experience flow chart (~4-5 hours).   The rest of the sprint was spent testing the JavaScript packages we plan to, or are interested in, implementing in the project (~4-6 hours).    Creating the user experience flow chart took a few iterations as we weren’t certain of the final gameplay.   The current version is fairly linear, but the gameplay is straight forward to make it easy to pick up and play.    A part of the final user experience flow chart. The packages I tested for our project were aframe-extras , aframe-physics , and aframe-click-drag-component .   ‘Extras’, as the name suggests, adds some extra functionality to A-Frame, including controller support, ‘Physics’ adds a physics system, while ‘C...