'SceneManager' does not exist in the namespace 'UnityEngine'

I’m getting “error CS0234: The type or namespace name ‘SceneManager’ does not exist in the namespace ‘UnityEngine’ (are you missing an assembly reference?)”. I’m wondering if it’s because I’m currently using VS Code rather than the Visual Studio 2019.

Here’s my code:

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

public class Next : MonoBehaviour
{
void Start()
{
SceneManager.LoadScene("Game");
}
}```

The error occurs when I build and run.

Go check out the documentation for the proper spelling of the namespace you seek.

Thanks.

It’s UnityEngine.SceneManagement what you’re looking for.

Hi, i have the same issue and looked back on all the posts i can find on this matter
adding UnityEngine.SceneManangement does not work, it still says the same error, CS0234

PLEASE do not necro post.

You do NOT have the same issue.

Your issue is you cannot seem to spell “Management” correctly.

Go look it up.

Hint: it is NOT spelled “Manangement”

dude, chill out, i only mistyped on that post
this is one of 3 scripts that had the same error CS0234

using UnityEngine;
using UnityEngine.SceneManagement;
using UnityEditor.SceneManagement;
public class Titlescene : MonoBehaviour
{
public string Scene0;
// Start is called before the first frame update
void Start()
{
}
// Update is called once per frame
void Update()
{
}
public void GameStart()
{
EditorSceneManager.LoadScene(Scene0);

}
}
p.s. it works and the whole game runs fine, no error
the CS0234s only appears after I try to build the whole thing

This is only for editor use:

I don’t believe you need it in this case, but if you do, conditional compilation is the approach you need.

I am very grateful for the speedy reply despite being a dead thread, however
I am merely a student and had very little experience in coding, can you be a little bit more specific
I am here to ask for solutions, not being kicked to more documents that I will most likely not understand
and I looked up conditional compilation, I simply don’t understand what it does or how to do it.
the error happened at first when i don’t have the “using UnityEditor.SceneManagement;” line
I read up saying this should fix my issue, yet here I am

It is Editor code, as in it only works while in the Unity Editor. If you try to build the game, Unity neglects to include the packages for all the Editor stuff, so naturally it will throw an error on the code which isn’t there anymore.

By using Conditional Compilation, you can tell Unity “don’t write this code when you build the game”. It will treat it as if it doesn’t exist, and will get around the errors you’re getting. Read the documentation, or at least the examples at the bottom to see how it’s used.

Next time you have an issue, instead of necroing an old thread, it is much better for everyone involved if you just create your own thread. The top two stickies of the forum tell you how to format code in your thread, and what the rules are for the forum, which should stop you from drawing people’s ire.

Neither do we unfortunately. Nowhere in any of your posts have you said what you are even TRYING to do here.

I infer it’s something to do with scene changing, but I don’t know if it is editor time or game time. You are mixing and matching both above for some reason.

Changing scenes is so incredibly simple and trivial that there are over THREE MILLION tutorials on how to do it.

8662164--1166418--Screen Shot 2022-12-14 at 10.58.39 AM.jpg

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.

just an update, turns out all the suggested fix isn’t what i need
I simply had to remove “Editor” from 2 of the scrips that contains “Editor.SceneManager”
and then I can remove UnityEditor.SceneManager from the beginning, and that lets me build the game

but anywho, the suggestions did gave me the idea, so thank you with all my heart.