Posted on

Arthur’s Status Report for 02/27/21

This week, after Logan gave the presentation on wednesday, I started making some research on what parts we are going to need for our glove controller. We will meet early next week to finalize this list and start ordering our parts.

We are still on schedule

Deliverables for next week: The design presentation as well as we should at least order all of the parts so that we can start assembling the glove.

Posted on

Team Status Report 02/27/21

Significant Risks:

  • Creating an AR environment for our game. It is crucial for us to decide if we intend on using a regular background or the user’s living room as a background
  • Tracking the LED glove using OpenCV + Unity. As of now our best option is to spend $95 and use the Unity module to track the input, we need to make a decision if we intend on going forward with this or writing our own library to enable Unity – OpenCV communication

Changes made:

  • Based on feedback from our project proposal presentation we are quantifying our requirements and testing strategy
  • Using Blender and sketchup.com for our 3D assets, using readymade assets  will reduce time spent building our own assets

Schedule – No Changes

Posted on

Logan’s Status Report for Feb 27

I prepared for and presented our project proposal. Feedback was overall both constructive and positive. We need to consider quantifying our requirements and testing strategy going forward. As per our schedule I have installed and been working in blender to develop the 3D models for the game. This has taken a good amount of learning, as expected.

We are on schedule, however we need to order our parts as soon as possible.

For the next week I intend to continue to make progress on the 3D models I am responsible for as well as integration within Unity. I will likely be working with Ishaan to do this next week.

Posted on

Ishaan’s Status Report 02/27/21

I worked on the following:

  • Finding 3D assets for orange, apple, watermelon. Image below is a sample of one of the 3D assets

 

 

 

 

 

 

  • Setting up the Unity development environment on my local machine
  • Installing and getting started on using the following Unity libraries – UnityPhysics, UNet, UnityUI, Unity 2D, Unity Scripting
  • Explored different methods of tracking the user’s LED. The most promising method was using Unity + OpenCV. Based on my research it seems like it might be challenging to write code to make Unity + OpenCV work together, however, an easy alternative might be to pay $95 to use an existing Unity plugin.

 

Progress status – on schedule 

 

Deliverable for next week: 

  • Make existing 3D fruit objects appear in Unity game
  • Basic fruit ninja logic functions. Like spawn fruit
  • Researching methods to track the user LED through Unity
Posted on

Ishaan’s Status Report 02/21/21

 

I worked on designing our solution and how each component in our project would interact. The figure below demonstrates how the different game components will interact.  

For the glove component I researched different micro controllers would best suit our use case and what sensors, motors we need for haptic feedback[1] [2].

 

Understanding Technical risks: 

I researched different attempts of building fruit ninja in VR and found that translating the 2D visuals to 3D while maintaining a responsive user interface was the most demanding aspect of the project. [3]

Progress Status – On Schedule

Deliverables for next week: 

  1. Setting up the Unity Game environment
  2. Understanding the requirements for 3D modeling and building our fruits
  3.  Designing object/input tracking framework

References: 

  1. https://www.instructables.com/Haptic-Glove-for-the-Blind/
  2. https://hackaday.io/project/160405-diy-haptic-glove-for-vr
  3. https://www.jamesquickportfolio.com/fruit-ninja-vr
Posted on

Arthur’s Status Report for 02/21/21

This week, our team focused on our Proposal Presentation and making sure that all required elements are present. I was tasked with the Requirements section as well as making the Gantt chart for our initial schedule. We did however finalize the tasks, starting dates, and end dates together. This chart can be seen in our team status report as well as in our Proposal Presentation.

We are on schedule for this project and next week we will order all of the parts that we need for our glove controller. As soon as those parts arrive, we can start assembling the glove. Since the glove is one of our main risks, we want to make sure that the glove works or doesn’t as soon as possible.

If the glove is assembled by next week, then we will be able to post a picture. Once the glove has been built, I will turn all of my attention towards testing this glove to make sure that all the parts work correctly. This will be helpful once we code the game environment in order to identify where the errors come from.

Posted on

Logan’s Status Report for Feb 20

This week I accomplished my main deliverable of creating my assigned slides for the Proposal Presentation. Our team met multiple times throughout the week during and outside of class to respond to instructor feedback and refine our proposal and project idea. We met on Saturday to set up this WordPress site and finish our slides, and I volunteered to present on Monday.

We are on schedule.

In the coming week I plan to present for our team’s Proposal Presentation. As planned, I intend to help procure the parts we need for the physical glove this coming week, as well as begin designs on the 3D elements of our game. I expect next week to include significant time spent becoming acquainted with Unity as well.

Posted on

Team Status Report 02/21/21

Significant risks: 

Calibrating the glove to work with the Fruit Ninja environment and using Unity to wirelessly communicate with the glove are current technical challenges to our project. Additionally, ensuring the glove input is accurate and there is minimum delay are crucial to a smooth user experience.

If we are unable to set up the glove input our project will be a 3D Augmented Reality fruit ninja user’s can play using a computer mouse.

Changes made to the design: 

We pivoted from our original idea of building a Virtual Reality application using an FPGA. Since our original project did not have a specific use case we changed our project to a popular game that has not been recreated in Augmented Reality. This change significantly reduces our budget and increases our interest.

Updated Schedule: 

Posted on

Introduction and Project Summary

Fruit Ninja AR

For our project, we would like to implement the game Fruit Ninja in Augmented Reality with a glove controller. The traditional game is played on a tablet where the user needs to cut the fruits by swiping on a screen and avoid the bombs as they appear. Fruits that are cut earn the player points, while missed fruits make the player lose 1 life and cutting a bomb is an instant game-over. Multiple fruits go in an arc motion across the screen, and several fruits can be cut at the same time for combos.

What are our design goals?

The glove that we are going to build for this project needs to be wireless for optimized mobility. This glove represents the sword, which is the user input for this game: this is how the player can cut fruits. Translating the 2D Fruit Ninja environment to a 3D Augmented Reality game is our primary software focus.

Why this project is unique?

The game is traditionally in a 2D environment, even the VR versions of the game that have risen. The 3D designs of the fruits, bombs, and the sword combined with our unique glove controller will make this project distinctive.