Team Status Report 2/8

We’ve set up a Github for the Unity project and begun work on basic game mechanics. We have also done some preliminary research into electronics selection for modules and put in some parts orders.

Significant Risks

The most significant risk we see to our progress at this time is the complexity of the connections between the modules and the game panel. For our game to be enjoyable, it’s critical that switching the modules is fast, seamless, and reliable. This risk is being managed by handling this aspect of the project early on. As a team, we are discussing various ways to make solid electrical connections between the modules and the game panel. We are also looking at different ways to communicate between the modules and the panel. We are leaning toward mostly passive designs to keep the modules simple and minimize latency. A contingency plan we have is to focus on the simpler modules first and make sure that the MVP of our game works with them before moving on to more complex modules.

Significant Changes

We have not made any noteworthy changes to our overall system design but have made some changes to our module electronics. For example, we’ve decided to use an encoder instead of a potentiometer for one of our modules because it allows the users to freely spin the dial/wheel. This was necessary because it more closely aligns with our game design and how we’d like to control the submarine. It also allows the users to switch the module without it maintaining its state, since encoders do not output absolute position but rather direction and velocity. This will be slightly more expensive but still well within our budget so cost is not a significant concern. This is not a significant enough change to update our schedule.

Leave a Reply

Your email address will not be published. Required fields are marked *