So which one do you recommend for an artist (or which one is in the league of LiteC?)?

Now the reason I want to learn UnityScript is that:
a) According to everyone in their forum, it's the easiest to get started with (plus, I am not a programmer).

b) According to EVERYONE, even Unity devs, the tutorials are written in Unity Script (or are US friendly only) so I will end up struggling to learn something other than Unityscript if that's the case (and it seems, it is).


Any recommendations on where to start? I'll be honest with you all, the only reason I am interested in Unity is the Mac compatibility. The editor really isn't a big deal for me so if I can get the scripting thing sorted out, I'll just go for Unity (unless Conitec ports the A7 engine for Mac as well :P).


EDIT: I already emailed them the day the trial expired, no response. Not even a "f**k-off", thought I don't when them to say that. :P

Also, can you tell me what exactly do you mean by "get used to Unity API"? What's wrong with the API? (unless it can become a roadblock when creating a working game) Yeah, I am a noob, enlighten me someone.

UnityScript

a) yes
b) yes

UnityScript

a) no
b) no

Finally. With all my questions answered, I can now go design the bestest best of the best MMO's out there, probably destroy Blizzard in the process.



:P

On the other hand, I should probably post this on Unity forum.

it's like getting used to Unity API itself.

i mean in lite-c there is ENTITies and their pan tilt roll skills this kind of stuff, in unity all this things are diffrent and in unity way, knowing the api is gettin used to this. But i dont think this would be a problem when you start and learn it

hello

Is this " component " based programming system really suitable to code complex gameplay ?
I mean, for people who are more interested in programming rather than graphic ( AI algo's etc)

I have been playing with Unity for some days, a too short period really

Ok I dont mean that Lite_C is the best in the life but I start having a
" nostalgia " for those simple old fashion engines supplying just a bunch of functions and then... it is up to you

Just guessing, what's your opinion ?

I see the potential of the engine already convinced all of you serious about game development

one tipp from my side, I switched 12 month ago from A7/C-Script, I am mainly lead developer/programmer:

DO NOT EVEN bother programming with UnityScript (which is a JavaScript derivate; same syntax, etc.), instead use C# and Visual Studio C# (get the free express edition), you can easily add the DLLs that make up the unity framework (tutorial on the unity wiki) to a Visual Studio project and simply access the managed functions and classes. c# is nice and easy and using Visual Studio brings you all the very nice features of this IDE: auto completion, intelliSense, debugging, etc.

Docking Visual Studio to Unity is one of the most powerful combinations you can get. You will never regret switching from A7 - I promise you.

Oh - by the way - I might have mentioned this already - you can access the whole .Net Framework from any Unity-C#-Project.. this brings you all features of the .Net Library: SErialization, XML files, IO functions, encryption and everything else.

EDIT:
@ AlbertoT:
basically you can do anything you want with the engine. You are not restricted to some lame ass C-Script-style thingy anymore, using c# you can code anything you like. Our lead programmer currently is working on Pathfinding and Object Management for an RTS-style game and is making great progress...
a "component" is just a class attached to a game object acting as a property for the object:
e.g. you have a character that should act as your player... this character is an imported fbx model: you add a renderer, a texture, a basic collider, a physics component, and then you add a class controlling all that, moving the player by input keys...etc.. its really easy.

Hiya.

...I thought you could add anything you want to A7 by using C++, Delphi, etc.? Kinda like using C# to code stuff "into" Unity. Or am I just remembering something wrong again (wouldn't be the first time!).

About C# .... What are the limitations (if any) using the indie version as opposed to the Pro version ?

I mean, can I use the Unity3D engine with Visual Studio 2008 Express ?
Could I write a DLL etc ?

I tried this with Visual Studio + A7 and I found it tricky and there wasn't much official help.

Thanks

It is interesting to read from the experienced users like maybenew, David Lancaster, Kiyaku or Alphastrike that they like Unity. Since all these people made a few games I appreciate their reports very much. I did not test Unity so deeply and this information helps a lot.

Regards