Problem instantiating a prefab, and storing a reference to it.

just tested this, works fine for me.. are you sure there's not more you're not telling us?

What exactly are you expecting the debug log to tell you?

maybe go.transform.name?

the as gameobject is pointless by the way. its implicit.

@sparkzbarca - Not so, have you tried this? with UnityScript (JavaScript based) yes, but not with C#!

also, fyi the above debug will return the name of the game object as written (and at any rate you can access the name directly via gameObject... i.e.: "go.name"... so go.transform.name is a bit redundant

Perhaps that particular index of the Balloons array he is calling is null?

you mean you have to use that for unityscript or for C#.

I use C# and i just instantiate, admittedly i've not yet bothered trying to store the object instantiated in a variable. But i've never used as

on a side note

you got like 4.5k karma answer this for me

http://answers.unity3d.com/questions/349071/splitting-a-script-up-into-multiple-scripts.html

...gladly, though karma does not mean I actually know what I'm doing ;)

But I think I got this one.. :D

Oh, for C# you have to do lots of things EXPLICITLY, where UnityScript handles them implicitly... such as typecasting instantiated objects from type "Object" to type "GameObject".. but only IF you attempt to store a reference to the GameObject, that is ;)

What type is the Balloons array? It should be GameObject. Even though "as GameObject" is the best try to cast ins$$anonymous$$d.

Instantiate returns an Object but the variable is GameObject. you do need to cast it.

There are two ways to do it:

 GameObject go = Instantiate(Balloons[x],transform.position,transform.rotation) as GameObject;

or

 GameObject go = (GameObject)Instantiate(Balloons[x],transform.position,transform.rotation);

They both returns null if not working but the second one throws an exception which gives information on where and why. The first one is faster.

When it comes to UnityScript it is all done for you by the compiler which makes it easier but also less safe.

I suspect @PaulUsul is right: afaik, if Ballons isn't GameObject[], the typecast returns null without any warning. The object is instantiated, but the go variable will cause null reference errors.

@PaulUsul is correct! Thank you Paul.

Paul, if you want to post this as an answer ins$$anonymous$$d of a comment, I will mark it as answered.

It was of type Transform. Correcting this to type GameObject fixed the issue!!

Thanks to everyone for your help!!!

-Larry