please help

Unity Engine
,
1

it doesn’t do anything when i click it

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.SceneManagement;
public class PauseMenu : MonoBehaviour
{
  public static  bool gameIsPaused = false;
  public GameObject PauseMenuUI;
    // Update is called once per frame
    void Update()
    {
        if (Input.GetKeyDown(KeyCode.Escape))
        {
            if (gameIsPaused)
            {
               Resume();
            } else
            {
               Pause();
            }
        }
    }
  
    public void Resume ()
    {
      PauseMenuUI.SetActive(false);
      Time.timeScale = 1f;
      gameIsPaused = false;
    }
    void Pause ()
    {
      PauseMenuUI.SetActive(true);
      Time.timeScale = 0f;
      gameIsPaused = true;
    }
    public void LoadMenu()
    {
         Debug.Log("Loading Menu...");
        SceneManager.LoadScene ("MainMenu");
    }
    public void QuitGame()
    {
      Debug.Log ("Quitting Game");
    }
}
2

What is it suppose to do?

3

Pause screen but when i click escape it does nothing

4

That’s because you didn’t create a pause menu with the UI.

Start with the basics. You’re getting ahead of yourself.

5

??? UI ?? i dont understand soz i am new

6

Exactly……go to YouTube and search for tutorials for brand spanking new beginners.

7

I’m going to guess that you don’t see anything happening and conclude that “it does nothing”. You have Debug.Log statements in LoadMenu and QuitGame. Get in the habit of adding these statements anywhere you need to check whether a method was called.

8

Then start with tutorials, LOTS of tutorials. Spamming the forum multiple times won’t change you being new.

Tutorials and example code are great, but keep this in mind to maximize your success and minimize your frustration:

How to do tutorials properly, two (2) simple steps to success:

Step 1. Follow the tutorial and do every single step of the tutorial 100% precisely the way it is shown. Even the slightest deviation (even a single character!) generally ends in disaster. That’s how software engineering works. Every step must be taken, every single letter must be spelled, capitalized, punctuated and spaced (or not spaced) properly, literally NOTHING can be omitted or skipped.
Fortunately this is the easiest part to get right: Be a robot. Don’t make any mistakes.
BE PERFECT IN EVERYTHING YOU DO HERE!!

If you get any errors, learn how to read the error code and fix your error. Google is your friend here. Do NOT continue until you fix your error. Your error will probably be somewhere near the parenthesis numbers (line and character position) in the file. It is almost CERTAINLY your typo causing the error, so look again and fix it.

Step 2. Go back and work through every part of the tutorial again, and this time explain it to your doggie. See how I am doing that in my avatar picture? If you have no dog, explain it to your house plant. If you are unable to explain any part of it, STOP. DO NOT PROCEED. Now go learn how that part works. Read the documentation on the functions involved. Go back to the tutorial and try to figure out WHY they did that. This is the part that takes a LOT of time when you are new. It might take days or weeks to work through a single 5-minute tutorial. Stick with it. You will learn.

Step 2 is the part everybody seems to miss. Without Step 2 you are simply a code-typing monkey and outside of the specific tutorial you did, you will be completely lost. If you want to learn, you MUST do Step 2.

Of course, all this presupposes no errors in the tutorial. For certain tutorial makers (like Unity, Brackeys, Imphenzia, Sebastian Lague) this is usually the case. For some other less-well-known content creators, this is less true. Read the comments on the video: did anyone have issues like you did? If there’s an error, you will NEVER be the first guy to find it.

Beyond that, Step 3, 4, 5 and 6 become easy because you already understand!

Finally, when you have errors, don’t post here… just go fix your errors! Here’s how:

Remember: NOBODY here memorizes error codes. That’s not a thing. The error code is absolutely the least useful part of the error. It serves no purpose at all. Forget the error code. Put it out of your mind.

The complete error message contains everything you need to know to fix the error yourself.

The important parts of the error message are:

  • the description of the error itself (google this; you are NEVER the first one!)
  • the file it occurred in (critical!)
  • the line number and character position (the two numbers in parentheses)
  • also possibly useful is the stack trace (all the lines of text in the lower console window)

Always start with the FIRST error in the console window, as sometimes that error causes or compounds some or all of the subsequent errors. Often the error will be immediately prior to the indicated line, so make sure to check there as well.

Look in the documentation. Every API you attempt to use is probably documented somewhere. Are you using it correctly? Are you spelling it correctly?

All of that information is in the actual error message and you must pay attention to it. Learn how to identify it instantly so you don’t have to stop your progress and fiddle around with the forum.

9

There is no error in the console to start off with

10

We can guess there is no error or you would have mentioned it shows an error. I am pointing out that “it does nothing” might be what it looks like but it is doing something. It is not doing what you expect perhaps. By adding Debug lines you can insure what is and isn’t being called and what the value of things are.

We can key in the code and solve it for you or you can do what developers do and determine exactly why it isn’t working like you expect.

There are going to be 1000’s of these “it doesn’t work” situations you need to figure out how to determine why and there is a methodology for doing that.

11

Then welcome to debugging! Here’s how you get started:

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 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.

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

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://discussions.unity.com/t/839300/3

When in doubt, print it out!™

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

12

so i added these and none of them show in the console even when i click the key

 void Update()
    {
        Debug.Log("Before Input ");
        if (Input.GetKeyDown(KeyCode.Escape))
        {
            if (gameIsPaused) 
            {
               Resume();
            } else
            {
               Pause();
            }
        }
       Debug.Log("KeyInput");  
    }
13

Awesome! Now you’re getting somewhere.

Sounds like your code isn’t even running.

There are EXTREMELY well documented conditions that must be achieved for your code to run.

Go back to basic Unity documentation and understand WHY Unity runs your code.

Fix that.

14

It is a pause screen so i think it might not be on the right one it is on a canvas ATM does that sound right

15

Have you attached the script to an object in the scene? If not you need to create one in the scene and drag the script onto it to attach it.

16

Not that i can see

17

i couldn’t find anything

18

it is in the scene