Skip to main content

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 ‘Click-and-Drag’ is supposed to add mouse click and drag support for objects, but I was never able to get it working while testing, so we will likely have to find another option.  I also investigated a few more libraries that could come in use as we continue development:

  • Three.js: the 3D infrastructure for JavaScript that A-Frame is built on.  Using this package will allow for some powerful manipulation of 3D objects in our scenes.
  • Socket.io: supports the implementation of multiplayer servers.
  • Networked A-Frame: A more powerful, A-Frame specific version of Socket.io that has some added features such as voice chat and cross-play support.

Unfortunately, not having a working click and drag system made it difficult to test any modular components, so I was not able to get far with that this past week.


Labels:

Comments

Post a Comment

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 ...
Post a Comment
Read more

[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.
Post a Comment
Read more

Storyboard and Physical Layout

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 ...
Post a Comment
Read more