So basically I’m making a tank game and i’ve made the camera follow the tank and got the camera to move left and right when the mouse is near the corresponding side. Im having trouble getting the camera to pivot around the tanks target point instead of the movement. Can anyone help?
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
public class CameraControl : MonoBehaviour
{
public float rotateSpeed = 10f;
public Transform target;
public float smoothSpeed = 0.125f;
public Vector3 cameraOffset;
private void Start()
{
cameraOffset = transform.position - target.position;
}
private void Update()
{
}
void LateUpdate()
{
Vector3 NewPos = target.position + cameraOffset;
transform.position = NewPos;
float edgeSize = 15f;
if (Input.mousePosition.x > Screen.width - edgeSize)
{
transform.Rotate(0,rotateSpeed * Time.deltaTime, 0);
}
if (Input.mousePosition.x < edgeSize)
{
transform.Rotate(0, -rotateSpeed * Time.deltaTime, 0);
}
}
}
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.
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 Debug.Log("Problem!",this);
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.
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: