Category: Songting’s Status Reports

This week, I focused heavily on integrating our hardware, CV module, and software components. I added new gameplay elements and, throughout the integration process, identified and resolved several bugs, connection issues, and other inconsistencies. I also worked on improving the overall player experience. For example, smoothing camera motion, refining the camera-follow behavior, and removing unnecessary obstacles from the map.

Overall, our team is on track for Monday’s demo, and we feel confident that the experience will be both engaging and meaningful for the audience. After the demo, I plan to work on the final report and begin collecting accuracy metrics and user experience feedback.

This week, I have been working on adding a start-game scene to our game. Now the player will hover their mouse to the start game button and press it to start the game. I have also worked with my teammate to tranmit data from another machine that runs the CV component to my local machine that runs the game through bluetooth. I am also working on the final presentation.

I am on track to nearly finish the game and start testing our system to be ready for the showcase. Next week, we will collect feedback to our game and start testing and debugging.

This week, I focused on adding more exciting features to the game. After exploring multiple options, I implemented a feature where a random target is generated within a certain range on the map. Players need to hit this target to earn points. The game won’t end simply when the disk falls to the ground; instead, a new target will be generated, allowing players to continue trying to hit it. The game’s ending logic requires players to reach a certain point threshold to win.

I believe I’m on the right track! Next week, I plan to enhance the scoring system further and make the game even more enjoyable.

This week, I have been focusing on adding more input parameters to the Unity game. Specifically, Unity now supports an initial launch angle, tilt, and other rotational information from the sensor. To facilitate this, I have enhanced the DPU to calculate the launch angle and to directly receive the rotational properties from the Arduino. Additionally, the launching direction has been adjusted to align with the rotational angle.

I believe I am making good progress in development. Next week, I will work on integrating and fine-tuning the system with the real sensors, as well as improving the in-game physics model to account for the aerodynamics associated with different tilts.

This week, I made significant progress on the Unity Engine and the DPU. For the Unity Engine, I finalized the physics model based on an MIT paper on the physics of Frisbees. I incorporated their drag and lift force equations into the game. Additionally, I created a game scene featuring a central island with trees, woods, and bushes, all surrounded by water and mountains.

Furthermore, I implemented an initial version of the DPU that receives data from the Arduino sensor and calculates the initial velocity, tilt, and launch angle from the input values. This information is then sent to the Unity game. With the current system, players can throw the board with the sensors, and the trajectory will be automatically simulated in the game.

I believe we are on track and ready for the demo next week. However, there are still many details to address. The DPU currently needs to support a Bluetooth connection instead of a cable connection. Additionally, I need to enhance the integration of the sensors to obtain accurate measurements of throw direction, height, initial tilt, and launch angle.

This week, I continued my work on the physics code for the Unity Engine. I read additional papers on frisbee and disk physics. However, I am still encountering difficulties in perfecting the physics behavior of the more complex mesh of the frisbee.

I am slightly behind schedule due to my travels this week, but I plan to start working on the DPU next week. Hopefully, I will be able to process the data into a format that Unity can use.

This week, I have been focused on improving the Unity game physics model. I successfully made changes to achieve partially correct behavior in the physics system for the more complex frisbee physics mesh. Although there are still some flaws, I believe they will be relatively easy to fix.

During our meeting with the instructors and TAs on Thursday, we discussed the possibility of using a simple cylinder mesh for the disk instead of a more complex model. We also talked about benchmarking steps we could implement to verify our system, rather than relying solely on user ratings of their experience. I think a valid approach would be to actually throw a Frisbee and gather data from the sensors, then compare those sensor readings with the simulation data.

Next week, I will be traveling, but I plan to continue working on the Unity aspects and think through how we can write the Python data processing unit. Overall, I feel that I am on track with the entire process.

This week, I continued my work on the Unity Engine. I successfully implemented a prototype of our physics model using Unity C#. In the prototype, I created a simple disk based on my modeling. The disk accepts various parameters, such as launching velocity and angles, which will be calculated in our Data Processing Unit. I also contributed to the design report and finalized several technical components.

I believe I am on track to achieve my goal. I am making significant progress on the Unity game. Next week, I will continue to work on improving the physics model. Additionally, I plan to create a better frisbee model, as the current one is just a flat cylinder, and I will work on integrating the physics model with it.

 

 

This week, I have been focused on preparing the design presentation, gathering feedback from other teams, and reflecting on our design plan. The questions raised during the presentation were very helpful, particularly regarding how we will integrate all the sensors into the Frisbee. Additionally, I continued working on the Unity game, where I am concentrating on integrating the physics model to simulate the Frisbee’s trajectory.

I believe we are on track with our work schedule. Next week, we will finalize the parts list and place our order. I also plan to explore the OpenPose project. My goal is to get it up and running and examine the data it will output.

This week, I focused on exploring a viable physics model for Frisbee and disc games. I reviewed several academic papers on these models and attempted to implement one particular model (https://web.mit.edu/womens-ult/www/smite/frisbee_physics.pdf) using C# in the Unity Engine. There is still much that needs to be fine-tuned, as the mathematical model must align with the Unity Engine’s physics model and the shape of the Frisbee. However, I believe this is definitely a good start.

Additionally, I have been working on the design presentation and preparing for it. I put a lot of thought into the block diagram and our detailed implementation methods, which have been very helpful for planning the entire project.

Overall, I feel that I am on track this week. My goal is to complete the presentation by next week, receive feedback, and develop a concrete and comprehensive implementation plan. After the design presentation, I believe we will have enough information to order the necessary parts.