Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Question Camera Limit On Map Edge

Discussion in 'Scripting' started by Midwitch, Mar 27, 2023.

  1. Midwitch


    Mar 22, 2023
    I Tried Camera with 2d box collision and a border with 2d box collision, didnt work.
    Made this script for wasd free camera movement. Why is collision with map boundaries not registering?
    Not a coder just using tutorials.

    Code (CSharp):
    1. using System.Collections;
    2. using System.Collections.Generic;
    3. using UnityEngine;
    4. using static UnityEngine.RuleTile.TilingRuleOutput;
    6. public class WASDCameraMovement : MonoBehaviour
    7. {
    8.     private Vector3 CameraPosition;
    10.     [Header("Camera Settings")]
    11.     public float CameraSpeed;
    13.     void Start()
    14.     {
    15.         CameraPosition = this.transform.position;
    16.     }
    17.     void Update()
    18.     {
    19.         float translation = Time.deltaTime * 10;
    20.         transform.Translate(0, 0, translation);
    21.         float MinimumXValue = -96
    22.         + CameraPosition.x;
    23.         float MaximumXValue = 56
    24.             + CameraPosition.x;
    26.         if (Input.GetKey(KeyCode.W))
    27.         {
    28.             CameraPosition.y += CameraSpeed / 50;
    29.         }
    30.         if (Input.GetKey(KeyCode.A))
    31.         {
    32.             CameraPosition.x -= CameraSpeed / 50;
    33.         }
    34.         if (Input.GetKey(KeyCode.S))
    35.         {
    36.             CameraPosition.y -= CameraSpeed / 50;
    38.         }
    39.         if (Input.GetKey(KeyCode.D))
    40.         {
    41.             CameraPosition.x += CameraSpeed / 50;
    43.         }
    44.         this.transform.position = CameraPosition;
    45.         if (Input.GetKey(KeyCode.D))
    46.         {
    47.             //if our current X is > than the minimum range AND less than maximum range
    48.             if (transform.position.x > MinimumXValue && transform.position.x < MaximumXValue)
    49.             {
    50.                 transform.Translate(Vector3.right * CameraSpeed * Time.deltaTime, Space.World);
    51.             }
    53.         }
    54.     }
    55. }  
  2. Kurt-Dekker


    Mar 16, 2013
    Camera stuff is pretty tricky... you may wish to consider using Cinemachine from the Unity Package Manager.

    There's even a dedicated forum:

    Otherwise, time to start debugging! Here is how you can begin your exciting new debugging adventures:

    You must find a way to get the information you need in order to reason about what the problem is.

    Once you understand what the problem is, you may begin to reason about a solution to the problem.

    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
    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 names of the GameObjects or Components involved?
    - 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.

    You can also supply a second argument to Debug.Log() and when you click the message, it will highlight the object in scene, such as

    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: or this answer for Android:

    If you are working in VR, it might be useful to make your on onscreen log output, or integrate one from the asset store, so you can see what is happening as you operate your software.

    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:

    When in doubt, print it out!(tm)

    Note: the
    function is an alias for Debug.Log() provided by the MonoBehaviour class.