scripting

warning: Creating default object from empty value in /home/buckman/public_html/neo/modules/taxonomy/taxonomy.pages.inc on line 33.
Matt Barton's picture

Dev Diary 009: Heavy Metal (with working example)

Well, I'm happy to say I'm back in the saddle again, excited about making some games with Unity. After watching the complete series on 3D Buzz about building a simple 2D game, I think I know enough to at least get started actually MAKING something again. I thought I'd start with something very simple: create a block that you can move around with the arrow keys, wrapping if you hit the borders, and for frills throw in a background and make the block rotate. I figured this was a complex enough project to take a noob like me the better part of a day, but--SHOCK--it only took a few minutes! Holy COW, those 3D Buzz videos made a difference.

Matt Barton's picture

Dev Diary 005: Stumbling around Unity Scripting

Well, I definitely think I've left all the easy stuff behind me...Way behind me. Coming to Unity Scripting from Gamemaker is like jumping from addition to differential calculus. I'm pretty much forced to copy and paste code from samples. What's frustrating is that I *feel* like I understand the concepts, but for some reason when I try to apply them I get lost in a sea of look-alike names and subtle but critical distinctions between objects, classes, components, etc.

Matt Barton's picture

Matt's Dev Diary 003: Fun with Blender and a bit o' scripting

Spent most of today working my way through the Blender book and hitting some of my Unity books. I'm really starting to enjoy working with Blender; the book has been fantastic, and although I still feel like I'm muddling my way through, I already feel less like a drunk driver and more like an eager 16-year working on his learner's permit. I'm constantly seeing things in the book and realizing I've been doing so much stuff the HARD way, but if you put the book down for a minute you've already forgotten the shortcuts and have to dig through it again. Still, once you realize there's an easy way to do something, at least you know it's there for the digging up.

One thing I didn't work with before was the modifiers you can apply to objects. Much like filters with Photoshop or GIMP, you can do a lot of nice art just by applying these tools (no actual artistic talent required).
Three Cubes: Applying some simple modifiers makes each one look different.Three Cubes: Applying some simple modifiers makes each one look different.
There's also techniques to quickly create four table legs and such. It's not quite as easy as just copying and pasting, but a helluva lot easier than trying to create four different ones and move them into place by hand. That's a nightmare.

As far as Unity goes, I spent most of my time there reading about the scripting system. There's three options: Javascript, C#, and Boo. From what I hear, nobody uses Boo, noobs use Javascript, and anybody worth his salt uses C#. However, I keep encountering conflicting advice. Javascript seems to be able to handle almost any scripting need you might have, some say, so C# isn't needed. I can't seem to get a definite answer on whether, for all intents and purposes, Javascript is fine, or if you really do get a huge performance increase of some sort by working with C#. One strong thing in favor of Javascript is that it's the language of all the books and tutorials I've seen so far, and I've heard it's the norm for anyone who isn't a programmer by trade.

Syndicate content