Unity 3.4 has given me much problems and i don’t have the time to really figure out how to fix them, I need a way to download Unity 3.3 again. i’ve searched 4 pages on google and they’re all Unity key gen stuff. please help!
lorddament, sometimes is better try to solve the problem (if they are solvable of course), else than getting back to older release, is supposed that 3.4 must to be better and major of 3.3 problems were fixed… what problem do you have in 3.4?
Why not just learn to declare your variables? thats the only thing that really changed for most people using JS. I had to change nothing in my code at all. It all worked perfectly.
Instead of var thing = GameObject.Find(“x”); you need to do var thing:GameObject = …
Because you prefer to go back to 3.3 to fix it, without realising, your old code is really, really slow as js will be struggling to try and figure out why you couldn’t declare your variables. So by using 3.3 your code will run badly and slowly, and likely be riddled with bugs. It is your choice.
I agree with hippocoder. The new Unity improves performance at the expense of good typing habits which are of course expected of a programmer in the first place. 
But i think if Unity 3.4 still crashes often for me i might switch back to 3.3. Since i am coding in c# so not much difference except for new substance feature.
That’s not how it works, and that’s not what the issue is. “var thing = GameObject.Find(“x”);” and “var thing : GameObject = GameObject.Find(“x”);” are exactly the same thing. Type inference declares the variable type for you. GameObject.Find returns GameObject, so “thing” is typed as GameObject, whether you specify it or not. It’s the same thing in C#…“var thing = GameObject.Find(“x”);” is valid C# code and does exactly the same thing that it does in JS. This has nothing to do with dynamic typing, and it’s nothing to do with #pragma strict or Unity 3.4, and doesn’t affect the speed of code even a little bit. It’s purely a compile-time convenience.
–Eric
Hi.
I do not totally agree.
Of course, hereafter I will try to always apply these best practices, but at the time I assumed I could relax when the function is not used intensively, but it is only occasionally called when the user clicks a button or so, and really now I do not see that my program is especially slow, but rather the contrary.
I think that changes in Unity that forces to review old code should be optionals. Otherwise (as I believe is happening because of this latest version 3.4, and of course it happened to me), can create problems for people who have to meet deadlines.
Personally I had a problem that I find difficult to solve and I was forced to return temporarily to version 3.3.
People who have to meet deadlines wouldn’t be upgrading in the middle of a project, unless there are critical bugs (which there aren’t in 3.3, as far as I know).
–Eric
lorddament said that he has no time to fix the problem… that is a time problem, not a unsolvable bug… because that i was wondering if he tell us what are the problem he is having, so maybe they are easy to solve and he could stands in 3.4…
He’s a kid though. His profile says he’s at school for the next 5 years so he doesn’t want to have time.
omg, everytime gamedevs become younger …