Build-a-Furniture

This week, a large majority of both environments have been modelled (~2hrs)  to their fundamentals. The main focus for me was producing the design comps, which I did by setting up a camera in one angle of the environment that captures a scene from the wireframe. All objects in that shot are UV mapped (~4hrs) then brought to Substance Painter for texturing and rendering (~7hrs). The final results are seen below. The warehouse will contain a wide space for the user to work with. The green platform as seen on the right-hand side of the design comp is a dropbox for them to deliver the correct components, which are found in the scaffolded aisles. These aisles are labelled by the icon by its front, which determines what parts for which piece of furniture is found. The living room has a more simple design that will probably be tweaked and improved over time. Boxes containing the building components sent from the warehouse and are delivered through the chimney. Both of these desi...

I finished up on some graphical elements for the user interaction specification component of the proposal due this coming Friday. This includes the storyboard panels and the physical layout diagram. As I was researching Oculus Rift physical setups, I had to determine how many sensors we would need for our game. I believe that 2 sensors will be sufficient, since we do not need a true 360 degrees experience as the Builder player will primarily be focused on the 180 degree space in front of them (i.e. the fireplace, the TV, and building the furniture). Our game is not an action packed game with any running or shooting. Of course, the player will still be able to fully look around but they shouldn't have a great need to move in the other 180 degrees of space. This would also take into consideration accessibility to our game, because it costs extra to buy a third sensor (the Rift only comes with 2) as well as requiring adapters and wire extensions. I spent about 4 hours researching ...

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

This week's focus has mainly been on writing the design document and preparing for the alpha prototype (~2hrs). A great majority of the written sections in our proposal is complete while a large chunk of graphics remains to be developed in the coming week. The sooner the design document is complete, the better of an idea we have in how the project will turn out in the end.  On my end, I am responsible for 3D modelling the environments that will be used in the alpha demo. These are also necessary for producing design comps. The environments will be very low poly environments using primitive shapes and basic forms to form the rooms, nothing too extravagant. Below are a few screenshots of the environments in their current state: Living Room (~3hrs) that will be played in VR and the Warehouse (~4hrs) on desktop; all modelled in Maya. Warehouse Back Side Warehouse Front Gate Warehouse Top-Down View Living Room Back View Living Room Front View Living Roo...

This week, we decided to focus on finishing the Design Document as a main deliverable for the end of this sprint. Having this complete would help us to better understand our project requirements and develop an adaptable plan. On Friday, we had a group meeting (~0.5hrs) to discuss our specific roles, project scope, milestones, and to create a more defined objective in terms of styling, target audience, and primary educational takeaway. I spent the rest of class time (~3.5hrs) working on writing these details for the Design Document. I also made a visual to illustrate a simplified version of our proposed development schedule, which can be seen in the WEEK 2 introduction blog post . I spent a few hours (~3hrs) researching web sockets, socket.io, and networked-a-frame because we will need to have connectivity and communication between our two platforms (desktop browser and VR headset).  I also wanted to explore how other people created multi-user experiences with A-Frame.  Be...