Silent Hill-style scene transition on button click

Unity Engine
,
1

Been trying to figure out how to set up a Silent Hill-style scene transition that is:
a) only available when the player is within the trigger zone (eg. a doorway)
b) only activated on a the click of a button
I’ve so far been able to find info how to do both, just not together. Could it just be a matter of applying it correctly?

Here’s two of the scripts I tried:

using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using UnityEngine.SceneManagement;
public class SceneLoader : MonoBehaviour
{
    public void LoadScene(string sceneName)
    {
        SceneManager.LoadScene(sceneName);
    }
}

using UnityEngine;
using System.Collections;
using UnityEngine.SceneManagement;

public class SceneTransitionArea : MonoBehaviour
{
    bool _isPlayerWithinZone = false;

    void OnTriggerEnter(Collider other)
    {
        if (other.tag == "Player")
            _isPlayerWithinZone = true;
    }

    void OnTriggerExit(Collider other)
    {
        if (other.tag == "Player")
            _isPlayerWithinZone = true;
    }

    IEnumerator watchForKeyPress()
    {
        while (_isPlayerWithinZone)
        {
            if (Input.GetKey(KeyCode.Return))
            {
                SceneManager.LoadScene("SceneName");
            }
            yield return null;
        }
    }
}

Hope this makes some kind of sense.

2

Remove the IEnumerator. Your code should look something like the following:

void Update() {
if (sceneTransitionConditionMet() == true) SceneManager.LoadScene(“SceneName”);
}

private bool sceneTransitionConditionMet() {
if (_isPlayerWithinZone == false) return false;
if (Input.GetKey(KeyCode.Return)) return true;
return false;
}

The IEnumerator does nothing as it must be manually invoked with via StartCoroutine.

3

You just need to check for the input in Update, rather than your IEnumerator that’s not actually doing anything.

Also your SceneLoader component is kind of pointless.

You should put your code in code tags so your response is legible.

4

If this advice is followed you would need to replace the while loop with an if statement

5

Yes, hence ‘check for input in update’, which is not the same as ‘change your method to update’.

6

I know what you meant. My intention was to add additional information for the asker in the event they run into an issue and get confused.

7

Okay, so I tried this code first but ran into “error CS1513: } expected”. Not sure where the missing curly bracket is supposed to go, but seeing the code in code tags might be helpful.

8

You didn’t “ran into” any error. You made typing mistakes and caused those errors.

Now go fix them. Here’s how:

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.

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.

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! See the start of this post.