The following blog post, unless otherwise noted, was written by a member of Gamasutras community.
The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.
We've started up with a new Unity #game for mobile devices recently. Working on #tech demo/#prototype and sharing more first impressions.
What I like most is good documentation. The video lessons from their official site were enough for the beginning. Now I’m also watching the lessons here http://www.unity3dstudent.com/category/modules/
. The examples on this site are only on Js. It would seem to be uncomfortable if you want to write on C#, but you can easily write a code of equal value on both languages and the best part is that scripts on unity can be also written on both of them and they will work together without any problems)) I’m not sure yet which language to choose. JS is kind of closer to flash, but C# is easier to read when it comes to large amounts of code. I hope I’ll decide soon.
The most complicated thing so far is to understand the unity application structure itself. At some points it crosses path’s with flash and is complicated by 3d frills. It’s hard at the very beginning, because after working with 2d graphics it was a little unusual that you need to at least set the lights for the scene, or else it will be dark like in… )) After 2d, it’s also hard to allocate objects in 3d space. A simple drag-and-drop with the cursor doesn’t always work. Sometimes you’ll have to switch between different projections and drag the object in each one of them.
It’s important to understand what prefab is. It’s a MovieClip analogue, only with a more complex structure. I didn’t puzzle out all of the details yet, but they can be easily created on the scene with a simple drag-and-drop as well as with a dynamic code.
What also made my day is that if class contains public parameters, they are shown in fields of object inspector and can be edited manually from there.
I really liked the simplicity of adding physics to the object. It’s quite simple to add a Rigidbody component to the object and it will begin responding to the physics. You can set such parameters as weight, gravity etc. The manipulation with physical factors also doesn’t seem to be quite complicated. For example, gm.rigidbody.AddForce( Vector3(0,20,0)); - is a sort of a way to kick the object up (it will gain a one-time speed-up depending on the indicated vector). There are a couple of more useful things like that, which can come in handy and will save plenty of time for quickly written trash-games.
I also haven’t got the time yet to figure out how you can simulate the accelometer and gyro sensor on your pc. Once again, I’ve spent enormous amount of time on testing one code line, which responds to the accelometer.
In the morning, I heard that a new version of unity with 2d native support was released. I’m curious about what they came up with :)
We've got a demo and sketches goes first I guess.
Also I'm still planning to expand Unity on Windows Phone impressions in previous article R&D for Moblile Game Development
That’s all for now, see You soon :)