Symptoms:
- I am getting the error below appearing in my console:
error ArgumentException: The thing that you want to instantiate is null. Unity Engine.Object.CheckNullArgument (System.Object arg, System.String.Message)
Cause:
The error, 'ArgumentException: The thing that you want to instantiate is null,' is caused when you use a script to instantiate a GameObject that doesn't reference a prefab.
Some possible common scenarios that could lead to this error are:
- You tried to load a prefab that is not present on a Resource folder using Resources.Load() resulting in a null reference.
- You manually assigned the GameObject a value of null on your script.
Resolution:
You need to assign a reference to the -GameObject that you wish to instantiate via the inspector- or a -script.
Via the inspector:
Create reference via a script:
More Information:
Comments
4 comments
This is not true, and though not deeply, then for the newbee it is in contrast to this info:
https://docs.unity3d.com/ScriptReference/Resources.Load.html
However, it does often happen in cases where people for example are using new on a Monobehaviour, or maybe have a Dont Destroy On Load persistant Game manager type of setup that both holds scripts that should load prefabs while at the same time do things such as load scenes with for example
this isnt work for me. i even copied the actual path in the "Load" part but it isnt still working and My Object in inspector is still None
What if I only get the error when my clients, not the host, call the instantiation?
Host can instantiate objects just fine, and the clients will see them.
Bolt no longer works not even in a new blank project
what is wrong?
Please sign in to leave a comment.