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. Because Mitchell will likely be very occupied with developing the Alpha prototype's in-game functionality, I will be helping with the server side stuff.
Some useful links I found include the following:
I also started looking at making a diagram to illustrate the project's physical setup. This should be fairly straight forward as there are no real environmental restrictions for the set up. Since we are developing for Oculus Rift first, the physical set up will also take into consideration the placement of the sensors. The user with VR headset would also need to have enough space to play (like in the image below), and the user playing on the browser may or may not even be in the same room (depending on whether voice chat has been implemented).
Unfortunately, since all 3 of us participated in Global Game Jam this weekend (Friday to Sunday), we were not able to dedicate as much time towards this project. Next week, the goal for me is to work on finishing the diagrams and wireframes for the User Interaction Specification document, and to help with programming for the Alpha prototype.
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. Because Mitchell will likely be very occupied with developing the Alpha prototype's in-game functionality, I will be helping with the server side stuff.
Some useful links I found include the following:
- https://www.reddit.com/r/WebVR/comments/cww751/question_multiplayer_integration_with_aframe/
- https://hacks.mozilla.org/2017/10/multi-user-experiences-with-a-frame/
- https://glitch.com/~networked-aframe
I also started looking at making a diagram to illustrate the project's physical setup. This should be fairly straight forward as there are no real environmental restrictions for the set up. Since we are developing for Oculus Rift first, the physical set up will also take into consideration the placement of the sensors. The user with VR headset would also need to have enough space to play (like in the image below), and the user playing on the browser may or may not even be in the same room (depending on whether voice chat has been implemented).
Comments
Post a Comment