Question Scene management - loading next level

Hello

I am new to Unity. My current Unity version is 2021.3.5f1

I am making a 2d platformer for my unity essential checkpoint project. I have main camera, a player, ground and a gameObject (named End) which i intend to use it for entering my next level. If my player collides with End next scene should be loaded.
I can not find what i am doing wrong. While playing in game tab if my player collides with the End object, tab changes to scene tab and next scene is not loaded. The code of the script is given below.

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. using UnityEngine.SceneManagement;
5.  
6. public class FinishLine : MonoBehaviour
7. {
8.    
9.     private void OnCollisionEnter2D(Collision2D other)
10.     {
11.         if (other.gameObject.CompareTag("Player"))
12.         {
13.             SceneManager.LoadScene("scene2");
14.         }
15.     }
16. }

The error on the console is:
"Scene 'scene2' couldn't be loaded because it has not been added to the build settings or the AssetBundle has not been loaded.
To add a scene to the build settings use the menu File->Build Settings...
UnityEngine.SceneManagement.SceneManager:LoadScene (string)
FinishLine:OnCollisionEnter2D (UnityEngine.Collision2D) (at Assets/FinishLine.cs:12)"

But i've already added my two scenes in Build Settings.

 

Omg i was using "scene2" as the second level. But my second level is level2. I changed the code as below and now it works just fine.

Code (CSharp):

1.    
2. private void OnCollisionEnter2D(Collision2D collision)
3.     {
4.         if (collision.gameObject.CompareTag("Player"))
5.         {
6.             SceneManager.LoadScene("level2");
7.         }
8.     }
9. }

 

Yeah, that's a thing!! I've been there, done that. Here's the fastest way to hone right in on these problems: print EVERYTHING out and question each result.

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: https://forum.unity.com/threads/how-to-capturing-device-logs-on-ios.529920/ or this answer for Android: https://forum.unity.com/threads/how-to-capturing-device-logs-on-android.528680/

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:

https://forum.unity.com/threads/coroutine-missing-hint-and-error.1103197/#post-7100494

"When in doubt, print it out!(tm)" - Kurt Dekker (and many others)

Note: the

print()

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

 

It is surprising getting an advice this helpful due to a silly mistake. I just finished unity essentials pathway today and started junior programmer pathway. I believe your valuable input will help me through the course. Thank you.