Cayne Zacharias - Audio System Design/QA

What I learned.

Communication. 

No amount of pre-planning can compensate for poor communication. This project emphasized that effective communication is the cornerstone of teamwork, especially in a large group. One key lesson I learned is the importance of asking questions when you think someone might need help. Even if they don’t, you gain clarity—but in some cases, you’ll witness the evident relief as they realize support is available.

Working together in person adds another layer of connection, fostering camaraderie as everyone works toward a shared goal. The ability to bounce ideas off teammates—whether it’s refining system designs with input from programmers, integrating unspoken details from art or narrative, or adapting based on unexpected insights—proved invaluable. Clear communication allowed us to bridge gaps and approach challenges from different perspectives, ultimately strengthening the outcome.

Collaboration.

Working with a team requires patience and adaptability. Even small teams of two or three can present challenges, but coordinating with 26 individuals introduces a whole new level of complexity. Without proper coordination, it can quickly spiral into chaos.

This project offered valuable insights into effective collaboration and the importance of structure, even when loosely applied. While each of us had a specific role, we still relied on guidance to stay aligned and focused. Most of our progress was driven by group deliberations, supported by input from our professor, which helped us navigate challenges and maintain direction.

Despite the hurdles, we managed to come together, combining our efforts to create a final product worthy of inclusion in a portfolio—a testament to our teamwork and perseverance.

What was the most surprising part of the project?

It’s remarkable that it all came together. Given the limited time frame we had to conceptualize, design, and implement the project, the fact that we succeeded as a class is a testament to our adaptability and teamwork. Unlike projects that benefit from months or even years of meticulous pre-planning, we had to think on our feet, make quick decisions, and adapt to evolving challenges in real time.

Despite the constraints, we collaborated effectively, combining our individual skills and ideas to create a cohesive product. This experience demonstrated how teamwork, open communication, and a shared commitment to the goal can overcome even the tightest deadlines and the absence of extensive preparation. It’s an accomplishment that showcases the value of flexibility and determination in any creative endeavor.

Set Up.

For this project, I needed to learn to use MetaSounds and found an amazing tutorial for gunfire sounds that can be implemented in many ways using the patches that were taught. These patches allowed for customizing audio cues without having to recreate entire Meta Sound Sources.

The main objective of the game is to eliminate the enemy robots. We were shooting at the enemy, so we needed gunfire. Nearly every sound you hear within this devlog was acquired or produced by Vincent Lee.

Quick Summary:

QA and Assistance.

In addition to ensuring that the sounds were functioning as intended, I took on the role of identifying and reporting issues that didn’t seem to work as expected. I promptly communicated these observations to the relevant team members, helping to address potential problems early. I also assisted in brainstorming solutions when certain features or implementations didn’t go as planned, offering support to programmers as they worked through challenges. This collaborative effort improved the overall quality and fostered a stronger sense of teamwork within the group.