Skip to main content

Control Scheme Research

For the first sprint, I looked into possible control schemes that could be used with A-Frame, then at existing libraries for implementing these controls, and physics systems that could be implemented in A-Frame.  As the initial idea is to have the finder use desktop, we want to support keyboard and mouse, as well as controller (the standard PS/Xbox configuration) based interaction.  Since we were not sure whether A-Frame supports controllers by default I set out to find out what level of support was integrated, and what libraries could be used for controller support.

The first step was checking the A-Frame documentation on Interactions and Controllers.  Here I learned that A-Frame fully supports all common VR controllers, but it only supports conventional controllers through custom controllers, however, the library aframe-extras includes code for working with game-pads.  Since implementing our own code for controllers will be time consuming and the A-Frame documentation recommends the add-on we will likely use it for our experience.

Furthermore, since the experience will involve working with parts in a realistic environment we will need some kind of physics system, which A-Frame does not implement by default.  The most popular physics system in A-Frame is the aframe-physics add-on, which adds simple 'static-body' and 'dynamic-body' tags that can be added to most primitive elements as seen in the code below.


An example of aframe-extras and aframe-physics used in conjunction to simulate throwing a ball.

Ideally, these two systems will create a strong foundation for us to build off of as we begin to hammer out the details of our VR experience.


Comments

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

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

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