Skip to main content

Spring 9 - Finishing Furniture and VR startup

This week, I completed stripping the shelf apart to create separate components, as I did with the other two furniture pieces. I also rendered each component from each piece of furniture so that they can be used in the instruction manual. Finally, I added onto the blueprint of shape match from last week to incorporate the shelf, as well as the repetition of each step. This can be seen in the image below. Finally, each component has the coloured symbols placed in the right places and have been exported as GLTF to import into AFrame (~7hrs)

This week, I also went to procure a VR headset. With the state of things in the world, I had to be quick to contact Carleton's BIT department but was able to successfully obtain an Oculus Rift to do testing within VR. It took time to set everything up but I got it running in the end, however, I had many difficulties operating the WebVR space. Using the rift is extremely draining and I had several headaches afterwards. As of now, I'm unable to open the AFrame project in full VR, and not in a small popup window. This also spawned concerns with how building the project for Oculus Rift may affect how it works with other Oculus systems or the Vive. (~4hrs)

To end off the week, I re-rendered the completed furniture pieces without backgrounds or shadows for the manual. I also went into the code and resized the entire living room and furniture components to be smaller so that everything is consistent between Warehouse and Living Room in terms of their sizes; this was successful (~3hrs). Last I tested with VR, there were some concerns with size because opening the scene in VR made everything around the user look huge. Seems like the VR set creates a new camera and gyroscope system according to its own parameters and ignores the one we created and intended to use. This will be tackled in the next week.
Labels:

Comments

Post a Comment

Popular posts from this blog

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

Controllers and Game-state Management

The two issues I worked on this past week were getting game-pad controllers working with our project (~6 hours), and general work on the game-state systems to iron out some of the kinks and add some more functionality (~3-4 hours).  Unfortunately neither of these tasks proved 100% successful due to some set backs. The game-pad controllers are so close to working, movement and look controls are fully functional, but I cannot get the Super Hands components to pick up the button events from aframe-extras.  The easiest way to see this is by looking at some code: <!-- Camera --> <a -entity id= "rig" movement-controls position= "0 0 0" > <a -entity id= "camera" camera wasd-controls= "acceleration: 125" look-controls= "pointerLockEnabled:true" position= "0 1.6 0" capture-mouse st...
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