Question Help Please lol

Hi I'm trying to make a 2D game where i can switch between scenes through colliders which i got to work perfectly but i tried to add a cross fade transition between scenes and thats where the problem lies. I'm getting an error "CS1503. cannot convert from void to string" and i was wondering if anyone has a solution to this. Here is my code. the error is on line 16:

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. using UnityEngine.SceneManagement;
5.  
6. public class ScenesManager2 : MonoBehaviour
7. {
8.     public int sceneBuildIndex;
9.     public Animator transition;
10.     public float transitionTime = 1f;
11.  
12.     private void OnTriggerEnter2D(Collider2D other)
13.     {
14.         if(other.tag == "Player")
15.         {
16.             StartCoroutine(LoadScene(sceneBuildIndex, LoadSceneMode.Single));
17.         }
18.     }
19.  
20.     IEnumerator LoadScene(int levelIndex)
21.     {
22.         transition.SetTrigger("Start");
23.  
24.         yield return new WaitForSeconds(transitionTime);
25.  
26.         SceneManager.LoadScene(levelIndex);
27.  
28.         //levelIndex
29.     }
30. }
31.  

 

I lol at this. Please use code tags, or we have no other choice but to lol, because it's very lolable.

When you get an error, it makes sense to pay attention to the message of the error. If it says "cannot convert from void to string" it couldn't be any clearer. StartCoroutine expects an argument, and in one of its overloads, it expects a string, while LoadScene doesn't return anything, and so this void cannot convert to string. I'm also of the opinion that if void was convertible to string, it would be called string, not void, so I tend to agree with the compiler.

 

ah, this is my first time posting a thread lol, i didnt know abt the code tag. I just started coding so im not exactly sure what a void is but i understand that string is a form of text? Is there a way i can change my code to fix this issue?

 

Yes, you're just making typing mistakes. For one, stop doing that.

For two, here is how to fix your typing mistakes when you do make them.

NOTE: it does not involve posting to the forum.

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.

-------

How to fix a NullReferenceException error

https://forum.unity.com/threads/how-to-fix-a-nullreferenceexception-error.1230297/

Three steps to success:
- Identify what is null <-- any other action taken before this step is WASTED TIME
- Identify why it is null
- Fix that

-------

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 above!

 

Yes, by learning the aforementioned concepts.
Should I just start building a wall if I don't know what bricks are?

 

You're calling your LoadScene corountine with 2 arguments: LoadScene(sceneBuildIndex, LoadSceneMode.Single) while it only accepts one: LoadScene(int levelIndex). This is making the compiler confused and thinks you're trying to call the StartCouroutine(string methodName, object value = null) variant (in C# world it's called "overload").

So either remove LoadSceneMode.Single or add a parameter to your LoadScene coroutine.

Lol.