Skip to main content

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 and creating the diagram for the physical set up. The set up for the desktop browser Finder player is fairly straightforward with only an addition of a game controller.

Below is a diagram of a possible physical layout if both players are playing in the same room.


Some resources for the VR physical set up include:
https://forums.oculusvr.com/community/discussion/66062/how-many-sensors-should-i-use
https://riftinfo.com/best-oculus-rift-360-setup-for-amazing-tracking
https://www.roadtovr.com/oculus-rift-room-scale-tracking-setup-guide-easiest-no-drilling-holes-cheapest/
https://www.reddit.com/r/oculus/comments/a6t1sq/best_2_sensor_setup_for_360/

I created all the storyboard panels ("wireframes") for the user interaction specification document using Adobe Photoshop. It took approximately 3 hours to design, create, and write descriptions for each of the 11 screens.

The images below illustrate the general interaction goes from both players pressing "ready" at the start screen to the completion of the furniture piece in the Living Room and the ability to play again by selecting a new furniture to build from the catalogue.











(Repeat steps of communicating instructions and combining pieces until furniture is complete)


Other things I did this week include putting the design document and user interaction specification document together, formatting them, updating tasks and adding new weekly tasks to the GitHub project (~2.5hrs).


Labels:

Comments

Post a Comment

Popular posts from this blog

Sprint 2 - 3D Modelling the Environments

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

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