Resource.Load not working on startup of Unity

[nightowl79a]

I’m trying to load a map with resource.load. my code works 99% of the time… but after I close unity and reload it… I get a null reference error loding the resource. … as soon as I make any change to any script, even adding only a commit… it works again. Im pulling my hair out trying to google this, but I can’t figure out the magic keywords to describe this.

void SpawnDungeon()
        {
            GameObject temp = Resources.Load<GameObject>("Dungeon/Dungeons/" + dungeon.dName);
            //print(dungeon.dName);
            GameObject go = Instantiate(temp, transform);
            Transform tilesParent = go.transform.Find("TilesMap");
            tilesMap = new List<Tile>();
            foreach (Transform t in tilesParent)
            {
                tilesMap.Add(t.GetComponent<Tile>());
            }
        }

ArgumentException: The Object you want to instantiate is null.

UnityEngine.Object.CheckNullArgument (System.Object arg, System.String)

[Brathnann]

idk how you can use lightmode.
Anyways…Use code tags and post your code in the forum and not as screenshots.

Your text got split up, so it was a little hard to follow at first.

Copy and paste your error message, it contains a stack trace and can help direct people to where to look in your code.

[nightowl79a]

@Brathnann

idk how you can use lightmode.
Anyways…Use code tags and post your code in the forum and not as screenshots.

Your text got split up, so it was a little hard to follow at first.

Copy and paste your error message, it contains a stack trace and can help direct people to where to look in your code.

Should be fixed. I had to post from my phone, thats why screenshots seemed easier than typing it in, can’t just copy paste.

[Brathnann]

I was hopeful for some stack trace in the error with line numbers. But, if that is your only instantiate call in all your code, then I guess that would be the error source. My first thought was just an order of operation error.

However, I’m thinking it’s just an issue with the Resource folder. Honestly, if it’s a GameObject, I would just tie it to a variable and drag and drop in the inspector, but if you have a ton of stuff, I can see why you wouldn’t go that route. Addressables is a better solution honestly, if that is the case. Unity is trying to move away from the Resource folder anyways.

[nightowl79a]

@Brathnann

I was hopeful for some stack trace in the error with line numbers. But, if that is your only instantiate call in all your code, then I guess that would be the error source. My first thought was just an order of operation error.

However, I’m thinking it’s just an issue with the Resource folder. Honestly, if it’s a GameObject, I would just tie it to a variable and drag and drop in the inspector, but if you have a ton of stuff, I can see why you wouldn’t go that route. Addressables is a better solution honestly, if that is the case. Unity is trying to move away from the Resource folder anyways.

Let me clarify. This code works every time, except when I load unity for the first time. I load unity, press play and I get this error. To fix it, I just have to let the code recompile(change anything in any script and save)… After recompile… it then works flawlessly until I close unity and open unity again. The dungeon.dName is dynamic, but ig i could use a list of publics…but id like to understand why this is happening instead. I know the reference isn’t broken, the path is definitely correct, because it works every time except that first time.

[Joe-Censored]

Looks like this thread:

Resources.Load not working unless any asset is reimported

After upgrading a project from 2019.4 to 2020.2 I am experiencing an issue with the Resources class. When the editor is launched a call to Resources.Load that happens in Awake fails, unless I reimport any asset in the project. I don't really need to reimport the asset I am trying to load (a prefab) but any asset in the project, even a texture. To be even more clear: the path of the prefab is correct and the code did not change at all, only the editor version changed. Builds are not affected by…

[nightowl79a]

@Joe-Censored

Looks like this thread:
https://discussions.unity.com/t/822427

I think your right, the thread doesn’t really help fix it, but maybe its a unity issue. Although I’m using 2020, not 2019 and I haven’t updated in at leat 5 months, and my laptop stays mostly offline. Thanks for the link though.