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

[FINAL] - Where to find our game

Hello future builders, we're 3 programmer-artists that make up the Seismic Octopus team: Mitchell Koch - lead programmer, game tester, researcher  Priscilla Lo - project manager, sound design, lead 2D artist, programmer, documentation  Maxime Vincent - lead 3D artist, lighting designer, game tester We finished this course in May 2020 with a final release of Build-a-Furniture available on GitHub: https://github.com/Areizza/Build-a-Furniture Although this semester was full of hardships and unprecedented times near the end, we got through it together and are proud to present our simple web-VR game. Check it out and let us know what you think! :)

Catalogue, Sound Effects, JSON for Instructions

This week I updated the image for the catalogue and added it to the Living Room environment as an image plane (~2hrs). I am currently adding smaller clickable planes on top of it to represent the different furniture options to choose to build. A screenshot of this can be seen below. I also looked for some sound effects to use for user feedback (~2hrs) when pieces are combined together correctly, incorrectly, pieces are dropped, etc. These sound files have been added to the shared drive and will be implemented in the code in the next few days. Some example sounds can be listened to at the following links: https://freesound.org/people/NenadSimic/sounds/150879/ https://freesound.org/people/grunz/sounds/109662/ https://freesound.org/people/GabrielAraujo/sounds/242501/ https://freesound.org/people/kirbydx/sounds/175409/  I also worked on adding JSON for the builder.js and finder.js files to store the required information for the instructions (~1hr). An example o...

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