Calling variables in external script - inconsistent results

Question

Ive got a game-state script where I initialize and update variables that are "global".

Game_State.js:

var globalVariable_1 = "hello";  // string 
var globalVariable_2 = 20;  // number 
var globalVariable_3 = false;  // bool

Other_Script.js:

private var Game_State : scr_Game_State; function Start () { Game_State = FindObjectOfType(scr_Game_State);

Debug.Log("globalVariable_1 = " + Game_State.globalVariable_1); Debug.Log("globalVariable_2 = " + Game_State.globalVariable_2); Debug.Log("globalVariable_3 = " + Game_State.globalVariable_3); }

Output:

globalVariable_1 = hello 
globalVariable_2 = 1 
globalVariable_3 = true

As you can see, the output is correct only for the string-type, but when initializing numbers or booleans the value retured is incorrect.

Can anybody make sense of this, and hopefully propose a solution?

Answer 1

Answer by Tetrad · Jul 19, 2010 at 05:09 PM

Well first of all you can declare your variables static and then you don't have to do the FindObjectOfType nonsense. Just call your variables exactly the same way you have them in your example code.

Second, try declaring the types of your variables. So, like this:

var globalVariable_2 : int = 20;

Add comment · Show 2 · Share

Mike 3 · Jul 19, 2010 at 05:25 PM 0

Share

No need to set the type for int, bool or string - they're all deter$$anonymous$$ed implicitly by the compiler

Daniel 10 · Jul 19, 2010 at 05:29 PM 0

Share

That works great!

However, the variables now disappear from the inspector-pane. Not such a big deal - can always set them in the script - but it would be cool to just be able to adjust them as you do with other variables.

Answer 2

Answer by Mike 3 · Jul 19, 2010 at 05:27 PM

My guess is that you changed the values of your public variables at some point in the script, without realising (or forgetting - heck it happens all the time to me :P) how unity serializes public variables

What happens is that unity will keep on persisting the values which were set in the inspector (which will have been 1 for var2, true for var 3) after the first time they're set, and disregarding script changes for the values after that

If you want to change them, you should change them in the inspector for the script

Note - I still think you should use Tetrad's answer of making them static.

Add comment · Share

Answer 3

Answer by Daniel 10 · Jul 19, 2010 at 09:06 PM

Thanks for your answers :)

Im definitely going with the static variables - works great!

Add comment · Show 1 · Share

Mike 3 · Jul 19, 2010 at 09:13 PM 0

Share

mark Tetrad's answer as solved then :D (the tick under the vote up/down thing)

Calling variables in external script - inconsistent results

3 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions