Learning From Past Mistakes and Moving Forward

 Learning From Past Mistakes and Moving Forward

By: Pedro Colon

Hello all, Pedro here from Crystal Eyes! Now you may be wondering what this blog would be about but do not worry, the beta month has went well super well in comparison to last month. Communication was much better and tasks were done in quite a productive manner. A lot more tasks were done than before I feel and I feel the current build of the game is coming quite a bit. However, there are still some issues with the build to where next month, we are really going to pull over selves to full gear and really make it the best we can. So what went wrong and what went right?

What Went Right:

Honestly quite a bit. Our communication as a team is much better I feel. As a team, we knew what our tasks were and what we are supposed to do. And we got quite a bit of tasks done, so much so it felt like we were a cohesive unit. The only thing I lament is not being able to do more meetings but this will be fixed next month (will talk more about this in the What Went Wrong section). Another thing that went right was with the overall feeling of the game coming together. Now this is still beta so things are still jank, but in comparison to Alpha last month, I feel much more happier with the current state that would allow things to become the best it can be next month. These things I feel will help propel us into next month and be ready to get everything into pieces. 

What Went Wrong:

Honestly, I am not sure if I can say a whole lot went wrong. Though I suppose there was at least two things that came to mind that went a bit downward would be time management and description of tasks in Jira. For time management, I have started a few tasks late. This in turn may have effected the rate of which tasks could be done, possibly more tasks to be done and more time to do some fixes for some that failed the review. Another thing that I feel was a major issue was the description of the tasks in Jira. Quite a bit of points were lost due to that, haha. I will take this into account going into next month, since the scores for the milestone reviews will turn out to be better than for this month (and the previous month).

Overall Thoughts:

Overall, this is probably the most happiest I been with the project! Starting to understand what it means to be the point-man of the team along with getting quite a bit of tasks done as well. I really do see what this project could become and I can't wait to be apart of the end product this month. 

Comments

Post a Comment

Popular posts from this blog

The Pitfalls of Crafting a Position Placement and Lap Counter for Kart Racing Games

Kart racing games have always been a favorite among gamers, offering thrilling experiences of speed and strategy. Behind the scenes, however, game developers face numerous challenges in creating a seamless Position Placement and Lap Counter system. In this article, we'll explore the intricate web of issues encountered when striving to implement these essential features in kart racing games. 1. Real-time Position Tracking: Creating a Position Placement system that accurately reflects the real-time positions of players on the track is a daunting task. Traditional methods, such as grid-based placement, fail to capture the dynamic nature of kart racing, where players can change positions rapidly. Developers often resort to complex algorithms that require intensive computation to track player movements accurately. 2. Lap Counting Accuracy: Lap counting seems straightforward, but ensuring precise lap detection can be surprisingly intricate. Developers must consider factors like collisio...
Read more

Troubleshooting Unity GameManager Input Handling

Navigating Unity's complex ecosystem of scripts, input handling, and camera management can be challenging. This guide sheds light on the issues faced while implementing input actions in a Unity GameManager script and demonstrates a concise solution. Issue 1: Unresponsive Input Actions At first, the GameManager script wasn't responding to the LocalMultiplayerStart input action. The issue was traced to incorrect syntax usage. By replacing inputActions.Player.LocalMultiplayerStart.actionMap.enabled with inputActions.Player.LocalMultiplayerStart.triggered, the input action was correctly detected and acted upon. Issue 2: Inactive Update Calls Another roadblock was the GameManager's Update method not being called. This led to confusion and halted gameplay mechanics. The issue was mitigated by ensuring that the GameManager script was properly attached to an active GameObject within the scene. Furthermore, script execution order settings were adjusted to ensure proper function call...
Read more

Only one line of code

Image
 Only one line of code      For a while I was having trouble with a part of the drifting where the kart would completely stop at the drift zone. I made sure the trigger for the box collider was on so I was confused on why it would completely stop. I checked and messed with the drifting part of the code that maybe it was a way I made it but it still didn't work. I was working on it so much I reworked the drifting 3 times and even added a second boolean and I had no clue. Then after looking at how I'm calling the Drift method I thought about maybe moving it out of it's own if statement and it worked.     I didn't realize that it stopped moving rather than getting stuck. It was picking one over the other and after changing that it finally worked. I'm not sure if my previous code would have worked but now I'm making it so that the kart would drift after turning into a certain angle. I still can't believe that I overlooked the fixedupdate again.
Read more