Find Week 8's report here.
For the week 10 meeting on 6/1. We have reached the final week of the course, and our project is nearing completion. Shooting and multi-colored footsteps have been added to network play. As a result of playtesting, details such as player speed, wall color, and server period duration have been updated. Improvements have also been made outside of gameplay. The network code was made more efficient and bugs such as the game crashing when one client exits have been removed. There are some goals we are hoping to accomplish within the next few days. We are aiming to add sound to bring more depth to the game, add a visual indicator for when a player has been hit, and possibly add a ceiling boundary texture for the sake of appearance. We are preparing for our presentation and excited for the demo! Morale is high. The gif below shows foosteps in multiplayer network play.
My concrete goals for the week were to help out with integration and make sure that the animations can be seen by all players.
I was able to accomplish both of these goals.
I was unable to load in the crouching and running animations which was a reach goal for last week.
My specific goals for this upcoming week are to implement an effect which allows players to know they have been shot (red tint, particle effect, etc.) I would also like to work out any bugs with the game before demoing on Friday.
This week I learned that OpenGL does not work for all our machines. Mitchell and I were running the exact same code and his OpenGL variables were not being initialized whereas mine are. Luckily, we haven’t had any issues on the demo machines.
My individual morale is good as we have basically implemented all core aspects of our game and now we are just refining and implemented extra features.
Setup footsteps on network.
All.
N/A.
Audio fully setup before demo.
Our network code design.
Good, looking forward to demo!
Finish shooting.
Shooting registers and works with multiple clients.
Animations do not work on my machine (crashes immediately). Seems to be an OpenGL specific issue (does not appear on others) with my computer.
Finish the game.
Nothing new learned this week.
High - Game looks good.
My goal for this week was to modify the animations to be correctly holding the guns.
I was not able to finish my goal for this week.
We ended up not needing to modify the animations.
My goal for the next week is to finish any miscellaneous things needed for the game to be completed.
I did not learn anything new this week.
My morale is very high and I’m excited to see the completed game.
My goal for this week was to implement some minor quality of life changes to the network code, like not sending messages to a client that has disconnected.
I did implement that and will push shortly. I actually encountered another bug on my machine with the latest gameplay code, where I can build the game fine, but I get 5 frames and attempting to move using WASD crashes the game.
I accomplished what I set out to do.
I don’t know what to do specifically, but I’ll do whatever the team needs as we head into the final demo.
I learned a bit more about Visual Studio.
My morale is good.
My goal this week was to prepare introduction slides for our demo and write a script for the features we are hoping to show off during the gameplay portion of the demo.
I have created the slides and written a script.
I accomplished my goal.
Next week, I’ll prepare to present and write the final report.
I did not learn anything new this week.
My morale is high. I'm excited for the demo!