Camera Systems

The camera system for our project evolved significantly over time, reflecting the changing needs of the game as it developed. Initially, the plan was to use static cameras to frame the action, giving the game a more cinematic feel. However, as the game world expanded into a more open and dynamic environment, it became clear that static cameras were no longer suitable. They restricted the player's view and didn't adapt well to the fluid nature of the gameplay.

In response to this, I explored and implemented a dynamic camera system using splines, which allowed the camera to move along predefined paths. While this approach offered more flexibility, it introduced new challenges, particularly with player movement. The spline-based camera system sometimes struggled to keep up with the player's actions, leading to disorienting shifts in perspective and making it harder for players to navigate the game world effectively.

After extensive testing and iteration, I ultimately designed and implemented a simpler, more effective camera system that followed the player using a spring arm mechanism. This approach provided a more consistent and reliable experience, ensuring that the camera was always positioned to give players a clear view of their surroundings. However, this solution came with its own set of challenges. The spring arm camera required careful level design to avoid obstacles and ensure that the camera movement remained smooth and unobtrusive.

Throughout this process, I gained a deep understanding of the complexities involved in camera design for games. I learned that different approaches to camera systems each have their own strengths and limitations. The key is to balance the technical capabilities of the camera with the needs of the gameplay, ensuring that the camera enhances the player's experience rather than detracting from it. This experience has given me valuable insights into how to create camera systems that are both functional and immersive, tailored to the specific needs of the game and its players.

First iteration

My initial camera system had a single camera that constantly rotated to face the player but only moved when the player entered a trigger box. Each trigger box specified a new location for the camera to move to. This approach caused several issues: the camera movement was frequent and abrupt, which led to erratic gameplay. Additionally, because the player movement logic relied on the camera’s orientation to determine directions (left, right, forward, and backward), this inconsistency affected the player's control and navigation.

Here is the blueprints for this system.

Second iteration

To enhance the camera system, we implemented a dynamic setup where the camera followed the player along splines and always rotated toward them. Although this improved the experience, it introduced new issues. Each time the camera changed angle or spline, it affected the player's movement because the movement controls relied on the camera's rotation.

Initially, we tried to mitigate this by only updating the camera reference when the player stopped giving input, which reduced the impact on movement controls. However, this solution was problematic if the player didn't stop moving and ended up behind the camera, causing the controls to invert.

Ultimately, we decided to base player movement on the world's rotation rather than the camera's, which provided more consistent controls but limited the camera's positioning relative to the player.