Got him to retest the two codes....
Not as simple as it would appear....
In both cases the cube displayed about 50% of the time.
In other words 50% of the time the GVar was = 0 on load and a flight reset.
The rest of the time, I don't know!
Anyway I sent him modified code instead of
(G:Var4) 0 == if{ code }
(G:Var4) 1 == if{ code }
(G:Var4) 2 == if{ code }
I used
(G:Var) 3 == if{ code } els{ (G:Var) 2 == if{ code } els{ code} } }
That way the final els is any value that is not 1 or 2, so will cover whatever value it is initialising at.
Prelim tests encouraging!
Not as simple as it would appear....
In both cases the cube displayed about 50% of the time.
In other words 50% of the time the GVar was = 0 on load and a flight reset.
The rest of the time, I don't know!
Anyway I sent him modified code instead of
(G:Var4) 0 == if{ code }
(G:Var4) 1 == if{ code }
(G:Var4) 2 == if{ code }
I used
(G:Var) 3 == if{ code } els{ (G:Var) 2 == if{ code } els{ code} } }
That way the final els is any value that is not 1 or 2, so will cover whatever value it is initialising at.
Prelim tests encouraging!