:notebook_with_decorative_cover: Furniture Catalogue

3 options are currently available to be built: a white table, a brown chair, and a blue shelf. The catalogue displays the completed items with a difficulty rating and a short description. This catalogue is located on the Living Room wall by the TV, where the Builder can click one of the furniture options to start a new build.

:video_game: Platform

• Desktop, keyboard and mouse - Our game is built for the web using Javascript, HTML, and CSS

This game was originally created for a school project requiring an asynchronous cooperative experience. Our initial plan was to have the Finder player use a standard game controller and PC setup while the Builder player has a VR set up. An example of the physical setup is shown in the diagram below. However, due to some technical difficulties with acquiring hardware, we had to change our target platform from using the VR headset and controller to using desktop with mouse and keyboard.

:sweat_drops: Process and Challenges

Above is an overview of our intiial project timeline. As planned by our project manager, we set up weekly goals and meetings to discuss our current development progress. These can be reviewed in more detail on our project board.

The application required many small pieces that could each have multiple snap-points, and each snap-point has an image, but these objects had to be spawned dynamically on demand for both the Builder and the Finder while remaining consistent. The best solution we could find was to create a template JSON file that held the important data for all the furniture pieces, and a specialised serialiser takes this data and converts it to Aframe entities. In addition to this, the bounding shapes and snap-points all had to be manually placed and created for each individual piece, which was incredibly tedious.

The biggest challenge was the snapping functionality, which continually caused issues or required more functionality throughout the development process. As the Aframe Physics system cannot handle reparenting physics objects, every time an snap occurred, the child piece would have to be duplicated in its entirety (including other snap-points on the child), and then attached to the parent piece, using the relative positions and rotations of the two snap-points to place the new body. As one object cannot consist of multiple dynamic physics bodies, the bounding shape of the child piece would also have to be added the the parent object.

Curious about how we got here? Want to learn more about our process? Check us out on our development blog for our weekly updates: https://seismicoctopus.blogspot.com/

:scream: Known Issues

The markings on the pieces helped visualise how and where pieces are snapped. Previously, as seen on the right, we used emissive maps to show this so it was visible anywhere despite light levels, however, the problem was that they needed to be small enough to be covered up post snap so that they don’t remain visible. As a result, in certain cases, they turned out to be too small to make out the symbols. Our solution to fix this was by connecting larger images of the symbols to the snap points themselves. They appear large an obvious when spawned but will disappear once the snap is complete.

A minor challenge we found branches off from adding images to snap points. We use sphere colliders to detect the collision or intersection of two snap points, which are essential in making the whole mechanic function. Any attempt to hide them only creates this effect of a transparent surface on hover.

Another challenge we faced had to do with the orientation of the pieces being snapped. This issues arise in certain cases where an object snaps to two different points at once like on the chair’s backrest, or when an object is mirrored on both ends of the furniture, such as with the shelf’s sideboards. As seen here, because there are two snapping options and only one is ideal, there’s a chance that the object will snap to the wrong component and create a mess. There’s no way to detach pieces so the only option is to restart.

:zzz: Conclusion

Were we given more time and personnel, there are several things we would add to improve the experience of our game.

• This includes a detachment element that allows users to remove pieces off of furniture in case they make mistakes.
• Another is a trash can to delete components entirely if the player wishes for any reason. This would also help avoid clutter and not being able to do anything to pieces being spawned continuously in the warehouse.
• We would also improve the movement of how smaller pieces are controlled. While large blocks are easy to drag and move around, smaller pieces such as legs and skirts are not.
• We also want to fully implement VR. We were unable to do this as a result of time and resource constraints but a lot of our movements and controls are designed for VR in mind.
• As an aside, we would also add a crouch mechanic for desktop users to lower their camera and view objects from closer when they’re on the floor or on a lower level of the scaffolds.
• Finally, we would want to add more furniture of varying complexities and additional extraneous pieces.

:smiley: We hope you enjoy our game! :smiley: