Wednesday, 24 February 2016

Craig Lang: Scripting Update



I worked on trying to create my own player controller for our character. The reason behind this decision was due to being unable to edit the default Third-Person controller provided by Unity. We originally wanted to add a double jump feature to help create the platforming aspects we were looking for in our gameplay. Unfortunately there were several problems.








The main problem we faced was identifying the player is grounded. Despite the grounded code working the player could still run and jump off the walls within the game. We tried tackling this problem by using physics. The problem still occurred. We therefore tried to create our own physics to allow us more control. This broke the game entirely. The player not only failed to move properly, but the double jump was clunky as well.

The cameras were also an issue as its default rotation and position kept changing every time you entered zoom mode. This happened due to the default rotation and position updated the transformations when the player entered zoom mode. Adjusting the camera orientation so it always was facing forward caused the player to travel in any direction the camera was pointing as they moved forward. This enabled the player to fly.

Due to the list of errors and the deadline fast approaching we decided as a group to return to using the default Third-Person controller provided by Unity. This meant abandoning the double jump feature we originally wanted to implement into the game. 

The result of trying to fix the errors in the Player Controller caused me to full behind in other vital scripts needed for the project. I will need to edit the camera zoom script if I don't want the default transformations to change.

No comments:

Post a Comment