Box Colliders are not working...

Unity Engine
, ,
1

Hello everyone, excuse me for submitting this very simple problem but I’m a bit rusty with scripting and I’m not a professional programmer, I’m simply trying to make a sliding door, but it seems that the two box colliders (of the door and the player) don’t collide with each other, it doesn’t even start the debug I wrote under “On trigger enter” so they’re not really colliding, where am I going wrong?
I ensure that I have set the player object with the “Player” tag, and that both the door and player collider boxes are on and are set to “Is trigger”

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

public class SlidingDoor : MonoBehaviour
{
public float slidingSpeed = 2f; // Velocità di scorrimento della porta
public float openPosition = -1.5f; // Posizione della porta quando aperta
public bool isOpen = false; // Flag per indicare se la porta è aperta o chiusa
public string playerTag = “Player”; // Tag dell’oggetto giocatore

private Vector3 closedPosition; // Posizione della porta quando chiusa
private Vector3 targetPosition; // Posizione target della porta

// Start is called before the first frame update
void Start()
{
closedPosition = transform.position; // Salva la posizione iniziale della porta
targetPosition = closedPosition; // Inizializza la posizione target alla posizione iniziale della porta
}

private void OnCollisionEnter(Collision collision)
{
Debug.Log(“OnCollisionEnter called”);
if (collision.gameObject.CompareTag(playerTag))
{
Debug.Log(“Player collided with the door”);
isOpen = true; // La porta è aperta
targetPosition = new Vector3(openPosition, transform.position.y, transform.position.z); // Imposta la posizione target della porta
}
}

private void OnTriggerExit(Collider other)
{
if (other.gameObject.CompareTag(playerTag))
{
isOpen = false; // La porta è chiusa
targetPosition = closedPosition; // Imposta la posizione target della porta
}
}

private void FixedUpdate()
{
// Muove la porta verso la posizione target con una traslazione morbida
transform.position = Vector3.Lerp(transform.position, targetPosition, slidingSpeed * Time.fixedDeltaTime);
}

// Update is called once per frame
void Update()
{

}
}

8951460--1228935--Player.png
8951460--1228935--Player.png587×765 48.2 KB
8951460--1228938--Door.png
8951460--1228938--Door.png583×796 51.6 KB

2

I don’t see a whole lot of Rigidbodies on there… go back and check the docs for the requirements to receive collision messages.

For future reference, if you post a code snippet, ALWAYS USE CODE TAGS:

How to use code tags: Using code tags properly

And if the lack of RB isn’t the solution then it is 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 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 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 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.

Visit Google for how to see console output from builds. 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: How To - Capturing Device Logs on iOS or this answer for Android: How To - Capturing Device Logs on 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!™” - Kurt Dekker (and many others)

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

3

Thank you very much, the problem was the lack of rigid body…