How to fix it UI Problem?

Unity Engine
,
1 
using UnityEngine;
using System.Collections;
using UnityEngine.UI;
using UnityEngine.UIElements;

public class ButtonOK : MonoBehaviour {
   
    public string loadSceneName;    //Next load scene name
   
    public Texture2D buttonOkNormal;  //Texture button normal
    public Texture2D buttonOkDown;   //Texture button down
    public Entername enterNameScript;  //script entername
    public SelectCharacter selectCharacterScript; //script select character
    public AudioClip sfxButton;  //sound effect when click this button
   
    void OnMouseUp()
    {
        //change texture to "normal"
        this.gameObject.guiTexture.texture = buttonOkNormal;
       
        //Save select character and name
        PlayerPrefs.SetString("pName",enterNameScript.defaultName);
        PlayerPrefs.SetInt("pSelect",selectCharacterScript.indexHero);
       
        SpawnPointHero.enableLoadData = true;
       
        //Load next scene
        Invoke("LoadScene",0.1f);
    }
   
    void OnMouseDown()
    {
        //change texture to "down"
        this.gameObject.guiTexture.texture = buttonOkDown;
       
        //Play sfx
        if(sfxButton != null)
        AudioSource.PlayClipAtPoint(sfxButton,transform.position);
       
    }
   
    void LoadScene()
    {
        Application.LoadLevel(loadSceneName);;   
    }
}

ButtonOK.cs(24,19): error CS1061: ‘GameObject’ does not contain a definition for ‘guiTexture’ and no accessible extension method ‘guiTexture’ accepting a first argument of type ‘GameObject’ could be found (are you missing a using directive or an assembly reference?)

ButtonOK.cs(39,19): error CS1061: ‘GameObject’ does not contain a definition for ‘guiTexture’ and no accessible extension method ‘guiTexture’ accepting a first argument of type ‘GameObject’ could be found (are you missing a using directive or an assembly reference?)

2

Check the autocomplete when you write
this.gameObject.
That’ll let you know what valid properties/methods it supports. I think you’re looking for a Renderer, which would then allow you to set a Material.

3

Alternatively check the documentation to see what properties and methods exist for any given class: Unity - Scripting API: GameObject

There’s no such property as guiTexture. in game object, so you might want to explain what you’re trying to do rather than make a post with no effort.

Though why not just use a UI button for this?

4

Just throw out this code and everything associated with where you found it.

Seriously, just abandon it in place and walk away.

Go find a more-modern tutorial or example (see below).

How I know: I can see that the above code is at least eight or nine years old because it uses Application.LoadLevel() plus that .guiTexture obsolete removed shortcut.

Unity simply does not do this stuff this way anymore, end of story.

Start how this guy did: ask yourself “Can I …?”

Imphenzia: How Did I Learn To Make Games:

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.