The Beta Dash of Team Witness Paradox(2nd)

Which course does this assignment belong to	EE308
Where are the requirements for this assignment?	Requirement of this project
Team Name	Witness Paradox
Reference documents	CSDN, 《构建之法》

This is the 2nd blog of Beta Dash of Team witness Paradox.

①.Teamwork description

Team leader：Teng Junyi（832101329）

Progress from yesterday to now: Completed editing the first blog post and started working on the second blog post.

Problems/difficulties encountered: Not yet,everything is under control

Schedule from now until tomorrow: Wait more information to finish other blogs, and participate in the discussion of software.

Experience and feelings: Comparing with further improvement of our soft ware, designing a blog is a much easier work for me to do to. With my involvement in software refinement work, I am able to expand my development perspectives. And as the number of blog writings increases, I become more proficient in written work.

Screenshot of completed results:

Team Member: Wei Mingjiang（832101330）

Progress from yesterday to now: write some essays

Problems/difficulties encountered: time consuming.

Schedule from now until tomorrow: write all essays

Experience and feelings: I need to gather all information about our group

Screenshot of completed results:

Team member Yao Shutong（832101322）

Progress: Launched the game, monitored player feedback, addressed any post-launch issues.

Problems: Handling unexpected bugs or technical issues that may arise after launch.

Schedule: Continue monitoring and responding to player feedback, gather data for future improvements.

Feelings: Satisfaction in the game’s release, excitement for the game’s reception and potential future updates.

Screenshot: [Attach updated screenshot]

Team Member Deng Hongyu (832101302)

Progress from yesterday to now: Assist in refining the final report

Problems/difficulties encountered: Unfamiliar with the report structure, you need to check the data online repeatedly

Schedule from now until tomorrow: Prepare to make the final ppt

Experience and feelings: Through learning, I can make the final report more smoothly in the future

Team Member: Zhu Rundong（832101304）

Reflective Essay 2:

Progress from yesterday to now: Over the past few days, I focused on debugging and optimizing the game. I fixed various issues, including enemy behavior and collision detection. I also optimized the game’s performance by implementing object pooling and reducing unnecessary calculations.

Problems/difficulties encountered: I encountered difficulties in optimizing the game’s performance without compromising its visual quality. It required finding the right balance between performance and aesthetics.

Schedule from now until tomorrow: Tomorrow, I plan to implement additional gameplay features, such as power-ups and level progression. I will also continue optimizing the game for a smooth and enjoyable experience.

Experience and feelings: The process of debugging and optimizing the game has been challenging but rewarding. It has deepened my understanding of Unity and game development principles. I feel proud of the progress I have made and excited to see the game come together.

Team member: Lei Wutong（832101327）

Progress from yesterday to now: Completed editing the first blog post and started working on the second blog post.

Problems/difficulties encountered: Not yet,everything is under control

Schedule from now until tomorrow: Wait more information to finish other blogs, and participate in the discussion of software.

Experience and feelings: Comparing with further improvement of our soft ware, designing a blog is a much easier work for me to do to. With my involvement in software refinement work, I am able to expand my development perspectives. And as the number of blog writings increases, I become more proficient in written work.

Screenshot of completed results:

Team Member: Yang Xiao（832101309）

Progress from yesterday to now: fix the bug, and optimize the management of game page.

Problems/difficulties: Puzzle design needs to pay more effort

Arrange from now until tomorrow: improve the final game page management

What you’ll learn: UI is very important to the game completion degree

Screenshot of completed results:

Team member Wang Xuebin（832101301）

Progress from yesterday to now: Completed the collection and research of the questionnaire survey and other scattered parts of the guard.

Problem/difficulty encountered: No problem.

Lesson: The teammates are still working very hard and playing well

Team Member: Lai Binyu（832101326）

Progress from yesterday to now: Conduct the overall play experience of the game and test whether the process is smooth.

Problems/difficulties encountered: As on the previous day, it was not possible to explore the cause of the game error due to the ability problem. At the same time, due to the lack of time to play the game, it is impossible to design more deeply about the fun of the game content.

Schedule from now until tomorrow: Complete the preparation of the defense PPT.

Experience and feelings: Designing a game well and doing it sustainably is relatively difficult. It is inseparable from the cooperation of team members. In the daily also need to carry out more understanding of the relevant aspects, in order to design a game that someone loves to play, someone can play all the time.

Screenshot of completed results:

Team Member: Lu Weitao（832101303）

Progress since yesterday: Release of questionnaire and game test version, survey

Problems/difficulties encountered: None

Planning from now to tomorrow: Sort out the contents of the questionnaire and form a report

Experience: The results of the questionnaire need to wait, the waiting process is the most nervous, I hope you can enjoy the game we do

Team Member: Sun Jiahong（832101306）

Progress from yesterday to now: Supervise the development team members to complete the game beautification work and character operation optimization, and make ppt content summary to facilitate the completion of the overall task
Existing problems: no problem

Arrangements from now to tomorrow: Continue to summarize and understand the progress of each member’s tasks.

Experience: In order to report the results, I need to do a lot of preparation, which is what I should do.

Screenshot of completed results:

Team Member: Li Xingda（832101308）

In my recent sprint tackling the issue of clipping in our game, I delved into the intricate world of collision detection. I spent yesterday examining our current physics engine, identifying the gaps where models intersected unnaturally. Today, I adjusted the collision boundaries, ensuring a more realistic interaction between characters and the environment. The challenge was to optimize these adjustments without compromising game performance. This process highlighted the importance of precision in game physics and the fine line between realism and resource efficiency in game development.

Team member Chen Xuqi（832101314）

Progress since yesterday: Help fix the code

Existing problems/difficulties encountered: the programming is not enough, the source code is more complex, difficult to repair

The arrangement from now until tomorrow: The design of the scene

Experience: The code is difficult, I hope the scene design can be smooth

Screenshot of completed results:

②.Current project progress

We have basically completed the plan of this sprint, the game content is basically realized, and it is now in the stage of testing and feedback：
After the testing of testers and the improvement plan of debugging personnel, we solved some problem of item threading in the current stage, but sometimes the character model can reach the other side through the wall, We found the reason why the mold is worn, because we are giving the camera position to the character’s eye position, but when walking or the character moves the Angle of view, it is inevitable that the camera will penetrate the model or the wall but the character itself has not reached the wall, we tried to find a solution, but still failed.

③.Project burn out diagram

④.Photo of the SCRUM meeting：