How to Clamp a Camera FOV value?

Unity Engine
,
1

Hello all,

im just playing around trying to make a small game with my Girlfriend.

I wanted to Clamp my FOV between 100 and 20, so that my camera doesn’t zoom out so far.

I could use Cinemachine I know, I want to learn though and I don’t think that’s the best way.

I’ve gotten quite far IMO.
I just have a small problem I can’t figure out.
My two if’s are going against each other. I can’t say “if FOV > 20 && FOV <100” because that makes it not stop scrolling.

I know it’s not that difficult for most of yall but I’m struggling a bit so thanks for all the help!

Code:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;

public class ZoomHandler : MonoBehaviour
{
    [SerializeField]
    private float ScrollSpeed = 10f;

    private Camera ZoomCamera;

    float CamFOV = 0f;


    // Start is called before the first frame update
    private void Start()
    {
        ZoomCamera = Camera.main;
     
    }

    // Update is called once per frame
    void Update()
    {
     
        CamFOV = Camera.main.fieldOfView;

            if (CamFOV <= 100f) {
                float FOV = Input.GetAxis("Mouse ScrollWheel") * ScrollSpeed;

                ZoomCamera.fieldOfView -= FOV;

            } else { }


            if (CamFOV >= 20f) {
                float FOV = Input.GetAxis("Mouse ScrollWheel") * ScrollSpeed;

                ZoomCamera.fieldOfView -= FOV;

            } else { }




        //Debug.Log(CamFOV);

    }
}
2

Feels good, huh? :slight_smile:

If you want to debug the above, then you must find a way to get the information you need in order to reason about what the problem is.

What is often happening in these cases is one of the following:

  • the code you think is executing is not actually executing at all
  • the code is executing far EARLIER or LATER than you think
  • the code is executing far LESS OFTEN than you think
  • the code is executing far MORE OFTEN than you think
  • the code is executing on another GameObject than you think it is
  • you’re getting an error or warning and you haven’t noticed it in the console window

To help gain more insight into your problem, I recommend liberally sprinkling Debug.Log() statements through your code to display information in realtime.

Doing this should help you answer these types of questions:

  • is this code even running? which parts are running? how often does it run? what order does it run in?
  • what are the values of the variables involved? Are they initialized? Are the values reasonable?
  • are you meeting ALL the requirements to receive callbacks such as triggers / colliders (review the documentation)

Knowing this information will help you reason about the behavior you are seeing.

If your problem would benefit from in-scene or in-game visualization, Debug.DrawRay() or Debug.DrawLine() can help you visualize things like rays (used in raycasting) or distances.

You can also call Debug.Break() to pause the Editor when certain interesting pieces of code run, and then study the scene manually, looking for all the parts, where they are, what scripts are on them, etc.

You can also call GameObject.CreatePrimitive() to emplace debug-marker-ish objects in the scene at runtime.

You could also just display various important quantities in UI Text elements to watch them change as you play the game.

If you are running a mobile device you can also view the console output. Google for how on your particular mobile target, such as this answer or iOS: https://discussions.unity.com/t/700551 or this answer for Android: https://discussions.unity.com/t/699654

Another useful approach is to temporarily strip out everything besides what is necessary to prove your issue. This can simplify and isolate compounding effects of other items in your scene or prefab.

Here’s an example of putting in a laser-focused Debug.Log() and how that can save you a TON of time wallowing around speculating what might be going wrong:

https://discussions.unity.com/t/839300/3

Still though, camera stuff is pretty tricky… you may wish to (re)consider using Cinemachine from the Unity Package Manager.